Gary,
This might be an opportunity to use some programmatic tricks with settings: grab them now, install via Installer or whatever we decide to do, and then #ensure: the settings back to their original state???
Thanks for all the great work!!
Bill
Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254
Email: bschwab@anest.ufl.edu Tel: (352) 846-1285 FAX: (352) 392-7029
gazzaguru2@btinternet.com 03/25/08 8:09 AM >>>
With the Widgets stuff it is best to have as few Morphs onscreen while loading. In particular, keep the central screen area clear (where the progress appears) and disable any dockingbars/taskbars. Otherwise you may run into problems since the Widgets affects display code and MC is not atomic.
Regards, Gary.
-----Original Message----- From: ui-bounces@lists.squeakfoundation.org [mailto:ui-bounces@lists.squeakfoundation.org]On Behalf Of Adrian Lienhard Sent: 25 March 2008 1:02 PM To: Squeak's User Interface Subject: Re: [UI] Scrolling issue
Wow, that was fast. It works perfectly, thanks!
Note, I cannot load version Pinesoft-Widgets-gvc.302.mcz. It breakes the image during loading. I loaded Pinesoft-Widgets-gvc.301.mcz and then merged the change you did in Pinesoft-Widgets-gvc.303.mcz
Cheers, Adrian
On Mar 25, 2008, at 13:54 , Gary Chambers wrote:
That is down to having changed to generating MouseWheelEvents (rather than keyboard). The Hand procesing seems to lock mouse events to the UI. I have modified the behaviour to be more in line with the old handling. Pinesoft-Widgets-gvc.303.mcz on SqueakSource if you want to try and see if it helps.
Gary.
-----Original Message----- From: ui-bounces@lists.squeakfoundation.org [mailto:ui-bounces@lists.squeakfoundation.org]On Behalf Of Adrian Lienhard Sent: 25 March 2008 10:47 AM To: Squeak's User Interface Subject: [UI] Scrolling issue
Hi,
I've been using UIEnhancements for some time now. I like the look
and
many of the features but one thing that is annoying is that the scrolling behavior is broken (I'm on Mac OS X, Squeak VM 3.8.18beta1U). The behavior is that scrolling the list does not
stop
when you stop scrolling the mouse or trackpad. It looks like the scroll events are queued up and processed up until the last one
while
each step takes a lot processing time. The problem is that while it is scrolling the UI is unresponsive. The old behavior was that scrolling fast would also scroll the list fast while now the speed does not seem to differ.
Cheers, Adrian _______________________________________________ UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui
UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui
UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui
_______________________________________________ UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui
Best to give "general guidance" for the moments since various users use varying means to load... (MC on 3.9/3.10, Installer, Universes...). If MC on 3.9 had working pre/postamble it would be feasible (mostly, with a warning for windows closing...).
Gary.
-----Original Message----- From: ui-bounces@lists.squeakfoundation.org [mailto:ui-bounces@lists.squeakfoundation.org]On Behalf Of Bill Schwab Sent: 26 March 2008 12:41 PM To: ui@lists.squeakfoundation.org Subject: RE: [UI] Scrolling issue
Gary,
This might be an opportunity to use some programmatic tricks with settings: grab them now, install via Installer or whatever we decide to do, and then #ensure: the settings back to their original state???
Thanks for all the great work!!
Bill
Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254
Email: bschwab@anest.ufl.edu Tel: (352) 846-1285 FAX: (352) 392-7029
gazzaguru2@btinternet.com 03/25/08 8:09 AM >>>
With the Widgets stuff it is best to have as few Morphs onscreen while loading. In particular, keep the central screen area clear (where the progress appears) and disable any dockingbars/taskbars. Otherwise you may run into problems since the Widgets affects display code and MC is not atomic.
Regards, Gary.
-----Original Message----- From: ui-bounces@lists.squeakfoundation.org [mailto:ui-bounces@lists.squeakfoundation.org]On Behalf Of Adrian Lienhard Sent: 25 March 2008 1:02 PM To: Squeak's User Interface Subject: Re: [UI] Scrolling issue
Wow, that was fast. It works perfectly, thanks!
Note, I cannot load version Pinesoft-Widgets-gvc.302.mcz. It breakes the image during loading. I loaded Pinesoft-Widgets-gvc.301.mcz and then merged the change you did in Pinesoft-Widgets-gvc.303.mcz
Cheers, Adrian
On Mar 25, 2008, at 13:54 , Gary Chambers wrote:
That is down to having changed to generating MouseWheelEvents (rather than keyboard). The Hand procesing seems to lock mouse events to the UI. I have modified the behaviour to be more in line with the old handling. Pinesoft-Widgets-gvc.303.mcz on SqueakSource if you want to try and see if it helps.
Gary.
-----Original Message----- From: ui-bounces@lists.squeakfoundation.org [mailto:ui-bounces@lists.squeakfoundation.org]On Behalf Of Adrian Lienhard Sent: 25 March 2008 10:47 AM To: Squeak's User Interface Subject: [UI] Scrolling issue
Hi,
I've been using UIEnhancements for some time now. I like the look
and
many of the features but one thing that is annoying is that the scrolling behavior is broken (I'm on Mac OS X, Squeak VM 3.8.18beta1U). The behavior is that scrolling the list does not
stop
when you stop scrolling the mouse or trackpad. It looks like the scroll events are queued up and processed up until the last one
while
each step takes a lot processing time. The problem is that while it is scrolling the UI is unresponsive. The old behavior was that scrolling fast would also scroll the list fast while now the speed does not seem to differ.
Cheers, Adrian _______________________________________________ UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui
UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui
UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui
UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui
UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui
Just on SqueakSource, the Vistary theme now leverages the new CompositeFillStyle support to show a "thumb" image on scrollbars.
Pinesoft-Widgets-gvc.304
Gary.
Hmm.. why browser buttons is not decorated by theme anymore?
On 26/03/2008, Gary Chambers gazzaguru2@btinternet.com wrote:
Just on SqueakSource, the Vistary theme now leverages the new CompositeFillStyle support to show a "thumb" image on scrollbars.
Pinesoft-Widgets-gvc.304
Gary.
UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui
Have no problems here, or when loaded into an earlier image. Have loaded into a basic 3.9 final image too (after modifying MC to not show progress while loading, the only viable workaround now it would seem).
Gary
-----Original Message----- From: ui-bounces@lists.squeakfoundation.org [mailto:ui-bounces@lists.squeakfoundation.org]On Behalf Of Igor Stasenko Sent: 27 March 2008 4:44 AM To: Squeak's User Interface Subject: Re: [UI] Latest changes to UI Enhancements
Hmm.. why browser buttons is not decorated by theme anymore?
On 26/03/2008, Gary Chambers gazzaguru2@btinternet.com wrote:
Just on SqueakSource, the Vistary theme now leverages the new CompositeFillStyle support to show a "thumb" image on scrollbars.
Pinesoft-Widgets-gvc.304
Gary.
UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui
-- Best regards, Igor Stasenko AKA sig. _______________________________________________ UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui
Right, I think we want to improve Squeak in terms of user interaction. This may be far-ranging to start with. This is a call for discussion.
Where do we want to be with Squeak, anybody with an investment it the way it currently works is welcome.
We are looking at re-engineering the basics, the VM teams are welcome to add their 2 (cents, pennies, etc).
I think we envisage a framework (for want of a better word) that is rather fundamental, upon which existing Morphic can live, along with opportunities for radical new ui frameworks.
Hands up, and we'll see who can form a team.
Gary.
On 29/03/2008, Gary Chambers gazzaguru2@btinternet.com wrote:
Right, I think we want to improve Squeak in terms of user interaction. This may be far-ranging to start with. This is a call for discussion.
Where do we want to be with Squeak, anybody with an investment it the way it currently works is welcome.
We are looking at re-engineering the basics, the VM teams are welcome to add their 2 (cents, pennies, etc).
I think we envisage a framework (for want of a better word) that is rather fundamental, upon which existing Morphic can live, along with opportunities for radical new ui frameworks.
Hands up, and we'll see who can form a team.
I will be glad to help in future. But currently my hands are pretty busy with other stuff (VM etc). So, consider my hand as 5 cents and 2 pennies :)
Oh, and please, can you describe the new framework envisage to the masses. Here or on wiki :)
Gary.
UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui
Le Saturday 29 March 2008 22:49:47 Gary Chambers, vous avez écrit :
Right, I think we want to improve Squeak in terms of user interaction. This may be far-ranging to start with. This is a call for discussion.
Where do we want to be with Squeak, anybody with an investment it the way it currently works is welcome.
We are looking at re-engineering the basics, the VM teams are welcome to add their 2 (cents, pennies, etc).
I think we envisage a framework (for want of a better word) that is rather fundamental, upon which existing Morphic can live, along with opportunities for radical new ui frameworks.
Hands up, and we'll see who can form a team.
Gary.
Hi all, Miro is hosted at squeaksource. Every one can download and test it (MRVisualTests main). Because all icons are read from files, you have to uncompress current icons separately (Miro-Icons file is attached). Directory Miro-Icons must be located where your image is. It is far from being ready for real using but ready enough for small tests and big explanations. It uses Announcements. You will have to install it before. I have attached related package. alain
UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui
On 30/03/2008, Alain Plantec alain.plantec@univ-brest.fr wrote:
Le Saturday 29 March 2008 22:49:47 Gary Chambers, vous avez écrit :
Right, I think we want to improve Squeak in terms of user interaction. This may be far-ranging to start with. This is a call for discussion.
Where do we want to be with Squeak, anybody with an investment it the way it currently works is welcome.
We are looking at re-engineering the basics, the VM teams are welcome to add their 2 (cents, pennies, etc).
I think we envisage a framework (for want of a better word) that is rather fundamental, upon which existing Morphic can live, along with opportunities for radical new ui frameworks.
Hands up, and we'll see who can form a team.
Gary.
Hi all, Miro is hosted at squeaksource. Every one can download and test it (MRVisualTests main). Because all icons are read from files, you have to uncompress current icons separately (Miro-Icons file is attached). Directory Miro-Icons must be located where your image is. It is far from being ready for real using but ready enough for small tests and big explanations. It uses Announcements. You will have to install it before. I have attached related package.
alain
Loaded. Tried examples.. Except couple of bugs, all is working well.
Can you describe the essential features of your framework?
...
Loaded. Tried examples.. Except couple of bugs, all is working well.
Can you describe the essential features of your framework?
Well, here is a short explanation made on the fly. I will take the time to make a more complete one later somewhere in a wiki.
Miro is based on 4 classes hierarchies: scene, director, announce handler and actor. a scene is responsible for the view and basic input events: a scene displays some content on a canvas and receives mouse and keyboard events. Miro is made so that it should be possible to use any scene hierarchy. For now, used root scene class is MiroScene. It is still Morph2 compatible (a Morph fork). As you can see, only four scene classes are used: MiroImage, MiroCompositeScene, MiroTransformScene and MiroTextScene. (of course, HandMorph and PasteUpMorph are also reused). I think (hope) that it should be possible to use another root scene class based on Tweak or some Gtk wrapper.
Actor hierarchy represent an abstract widgets hierarchy with button, scrollbar, scrolled text, text field, ... Actors are responsible for data management (model management). As an example, with a text field one can manage a string data, with a radio button one can manage a boolean...
A director is a mediator between a scene and an actor. Is is responsible for the composition of the view: a director can be made of a set of directors. as an example, a scrollbar director is made of a scroller director and of two repeat button directors. A director is also responsible for the management of an announcer and of a set of announce handlers.
An announce handler is used to respond to announces. Several announce handlers can be dynamically assigned to a director in order to do something when an announce is received. Basically, the set of announce handlers assigned to one director is fixed by construction (see Director>>setUpAnnounceHandlers). But, there are some cases where an announce handler is really dynamically attached to one director. As an example, when a radio button is added to one container (a box) then, a MiroRadioButtonsBoxSceneHandler is created and assigned to that box in order to control its set of radio buttons (when a radio button is checked then all others in the box are unchecked). see MiroMorphicSceneBuildingHandler>>whenSceneOwnedAnnounce: aMiroAnnounce
The only objects that a client application is manipulating are the actors. the link between an actor and a director is primarily established by the theme (see Theme>>directorsRootClass and Theme>>directorClassFor: anActor).
These explanations are certainly incomplete and maybe difficult to follow. Sorry for that but I can't spend to much time on it now. Hope it helps a little.
alain
I've had a quick look (busy getting the "diff tools" out). Looks really good, I'll have a more in-depth look soon.
-----Original Message----- From: ui-bounces@lists.squeakfoundation.org [mailto:ui-bounces@lists.squeakfoundation.org]On Behalf Of Alain Plantec Sent: 30 March 2008 1:53 PM To: Squeak's User Interface Subject: Re: [UI] Call to arms
...
Loaded. Tried examples.. Except couple of bugs, all is working well.
Can you describe the essential features of your framework?
Well, here is a short explanation made on the fly. I will take the time to make a more complete one later somewhere in a wiki.
Miro is based on 4 classes hierarchies: scene, director, announce handler and actor. a scene is responsible for the view and basic input events: a scene displays some content on a canvas and receives mouse and keyboard events. Miro is made so that it should be possible to use any scene hierarchy. For now, used root scene class is MiroScene. It is still Morph2 compatible (a Morph fork). As you can see, only four scene classes are used: MiroImage, MiroCompositeScene, MiroTransformScene and MiroTextScene. (of course, HandMorph and PasteUpMorph are also reused). I think (hope) that it should be possible to use another root scene class based on Tweak or some Gtk wrapper.
Actor hierarchy represent an abstract widgets hierarchy with button, scrollbar, scrolled text, text field, ... Actors are responsible for data management (model management). As an example, with a text field one can manage a string data, with a radio button one can manage a boolean...
A director is a mediator between a scene and an actor. Is is responsible for the composition of the view: a director can be made of a set of directors. as an example, a scrollbar director is made of a scroller director and of two repeat button directors. A director is also responsible for the management of an announcer and of a set of announce handlers.
An announce handler is used to respond to announces. Several announce handlers can be dynamically assigned to a director in order to do something when an announce is received. Basically, the set of announce handlers assigned to one director is fixed by construction (see Director>>setUpAnnounceHandlers). But, there are some cases where an announce handler is really dynamically attached to one director. As an example, when a radio button is added to one container (a box) then, a MiroRadioButtonsBoxSceneHandler is created and assigned to that box in order to control its set of radio buttons (when a radio button is checked then all others in the box are unchecked). see MiroMorphicSceneBuildingHandler>>whenSceneOwnedAnnounce: aMiroAnnounce
The only objects that a client application is manipulating are the actors. the link between an actor and a director is primarily established by the theme (see Theme>>directorsRootClass and Theme>>directorClassFor: anActor).
These explanations are certainly incomplete and maybe difficult to follow. Sorry for that but I can't spend to much time on it now. Hope it helps a little.
alain
UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui
Just released (as in uploaded versions) of the "Diff Tools" on SqueakSource. Check here: http://wiki.squeak.org/squeak/6005 for details.
Have fun! Gary
****************************************************************************************************************************************** This email is from Pinesoft Limited. Its contents are confidential to the intended recipient(s) at the email address(es) to which it has been addressed. It may not be disclosed to or used by anyone other than the addressee(s), nor may it be copied in anyway. If received in error, please contact the sender, then delete it from your system. Although this email and attachments are believed to be free of virus, or any other defect which might affect any computer or IT system into which they are received and opened, it is the responsibility of the recipient to ensure that they are virus free and no responsibility is accepted by Pinesoft for any loss or damage arising in any way from receipt or use thereof. *******************************************************************************************************************************************
Pinesoft Limited are registered in England, Registered number: 2914825. Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA
-
Alain Plantec -
Bill Schwab -
Gary Chambers -
Gary Chambers -
Igor Stasenko