Do know what is being executed:
- use the third mouse button to display the allows of the dialog - press this button again until the button is selected (you will see PluggableButtonMorphPlus at the bottom line of the halos) - press the 'wrench' button on the right (named 'debug') - select 'explore morph' - click on the '+' sign to unfold - the 'model' property tells you where the message will be sent (an instance of TextEntryDialogWindow) - the 'actionSelector' property tells you that the message is #ok.
So, #ok will be sent to an instance of TextEntryDialogWindow. You can now browse TextEntryDialogWindow, right click on the class, open ' Protocol browser'. Select '--all--', in the method list select 'ok'. You will see that the #ok method is implemented in the DialogWindow class a superclass of TextEntryDialogWindow.
Have a nice day
On Wed, Apr 9, 2008 at 9:11 PM, Ken G. Brown kbrown@mac.com wrote:
Hi, I have a question about where to find what actually gets executed when you click a button. sq3.10-7159dev08.04.1 with UI Enhancements
eg. Open a simple ChangeSorter, opt-click to make a new ChangeSet, enter the name. What gets done when you click ok? I've dragged a copy of the button off and explored and inspected but cannot find what the button action actually is. I seem to be missing some key understanding on how the button in this case works.
My goal, and reason for looking into this particular thing, is to programmatically create a new ChangeSet in an Installer script, so answering how to do that would help too.
Thx, Ken G. Brown _______________________________________________ UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui
Aha! The mysteries are unfolding! Doesn't quite get me there yet since the #ok message is just: -- ok "Apply the changes and close."
self cancelled: false; applyChanges; delete -- but maybe I can find the right thing now using the same methodology. Looking for how the ChangeSorter actually does its create new ChangeSet deed.
Thx, Ken
At 7:48 AM +0200 4/10/08, Damien Cassou apparently wrote:
Do know what is being executed:
- use the third mouse button to display the allows of the dialog
- press this button again until the button is selected (you will see
PluggableButtonMorphPlus at the bottom line of the halos)
- press the 'wrench' button on the right (named 'debug')
- select 'explore morph'
- click on the '+' sign to unfold
- the 'model' property tells you where the message will be sent (an
instance of TextEntryDialogWindow)
- the 'actionSelector' property tells you that the message is #ok.
So, #ok will be sent to an instance of TextEntryDialogWindow. You can now browse TextEntryDialogWindow, right click on the class, open ' Protocol browser'. Select '--all--', in the method list select 'ok'. You will see that the #ok method is implemented in the DialogWindow class a superclass of TextEntryDialogWindow.
Have a nice day
On Wed, Apr 9, 2008 at 9:11 PM, Ken G. Brown kbrown@mac.com wrote:
Hi, I have a question about where to find what actually gets executed when you click a button. sq3.10-7159dev08.04.1 with UI Enhancements
eg. Open a simple ChangeSorter, opt-click to make a new ChangeSet, enter the name. What gets done when you click ok? I've dragged a copy of the button off and explored and inspected but cannot find what the button action actually is. I seem to be missing some key understanding on how the button in this case works.
My goal, and reason for looking into this particular thing, is to programmatically create a new ChangeSet in an Installer script, so answering how to do that would help too.
Thx, Ken G. Brown _______________________________________________ UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
UI mailing list UI@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/ui
Just a minor issue thought regarding dev image naming convention...
When you release, I find that I bring a fresh dev image and changes into a new folder with the same name, then open it, and immediately save as new version giving the following: sq3.10-7159dev08.04.1 - this is the folder sq3.10-7159dev08.04.1.changes sq3.10-7159dev08.04.1.image sq3.10-7159dev08.04.2.changes sq3.10-7159dev08.04.2.image
which is good, because the versions end up in the right order.
Small problem would come if you released a sq3.10-7159dev08.04.2 since there would be a naming conflict because I already have one of those. I would not be putting it into the same folder in any case, but there would then be versions on my system with same names, with totally different meanings.
Perhaps you have found this as well.
The issue is a side effect of how Squeak figures out the name for the new version, and maybe that is what you do to get the name in the first place.
No biggy, but this will most likely apply to other release versions too so if we give it some thought, it might be helpful.
As you might have guessed, messy versioning systems is one of my pet peeves! :) I haven't really looked into it seriously but one would think version numbering must have been beaten to death somewhere already, wouldn't you think?
Any ideas?
Love the dev releases by the way. I'm now able to build my customized image from your new releases via Installer in about 15 minutes, loading all Keith's stuff, everything I need to use VMMaker, all my own work, reloaded custom named Workspaces from text files with various snippets and stuff I need to keep around, etc., etc.
It drives me crazy to know that someone somewhere has fixed stuff that might be an issue I would run into, therefore I like to keep up to date. Don't know how people can stand to work in old images.
Ken G. Brown
-
Damien Cassou -
Ken G. Brown