Re: [Pharo-project] New pharo-dev based on latest version
Stef, Thanks for the pointer. It could use some work though. One of my favorite mantras for GUI design is "never punish the user." I have been roundly scolded :) It seems I was confused over what would be used for search string, and was thus forced to wait a fairly long time for results having little to do with my intended search. If I may mix features a little, Dolphin sometimes populates prompters with either text on the clipboard, and perhaps current line/selected text, allowing one to accept/cancel an action w/o risk of assuming a search the user did not intend to do. Dolphin's find-methods-containing-text is also MUCH faster than Pharo's. It might just be the relative speeds of the two systems (I hope not), lack of important primitives, or perhaps code that can be greatly improved. The latter reminds me of DSDN, which I wrote for Dolphin, getting it to (reliably) CRAWL through searches across documentation, newsgroup archives, and the image itself. Ian Bartholomew promptly made it FLY by comparison (measured in orders of magnitude, as I recall). Hopefully a similar coding style could buy us a big boost here. Somewhat related, Dolphin's search for references to either the selected method or to text that can be entered in a prompter. The non-prompting search is available from a context menu in the method pane, so it tends to "just 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) 273-6785 FAX: (352) 392-7029
stephane.ducasse@inria.fr 08/20/08 5:51 PM >>> You bring the menu on the method pane then more.... then source code with .... it will scan all the methods for the string you pass
On Aug 20, 2008, at 10:09 PM, laurent laffont wrote:
Thank you.
I have another super newbie question. I want to disable the warning that SqueakV39.sources is not found when we load an image. I found the preference and the message Preferences>>warnIfNoSourcesFile but this is not called on startup (I've put a halt in it to check)
I try to find a tool to search for the string "Squeak cannot find the sources file named ..." to know which code popup the dialog.
I want to disable this dialog and the "Enter your initials" one by code in my squeakci script, as it prevent me from drinking my coffee or taking a nap while all tests runs without any human intervention.
Laurent _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
squeak was not really engineered over some years, just funnily hacked and we pay the price now. Stef On Aug 21, 2008, at 6:07 AM, Bill Schwab wrote:
Stef,
Thanks for the pointer. It could use some work though. One of my favorite mantras for GUI design is "never punish the user." I have been roundly scolded :) It seems I was confused over what would be used for search string, and was thus forced to wait a fairly long time for results having little to do with my intended search.
If I may mix features a little, Dolphin sometimes populates prompters with either text on the clipboard, and perhaps current line/selected text, allowing one to accept/cancel an action w/o risk of assuming a search the user did not intend to do. Dolphin's find-methods-containing-text is also MUCH faster than Pharo's. It might just be the relative speeds of the two systems (I hope not), lack of important primitives, or perhaps code that can be greatly improved. The latter reminds me of DSDN, which I wrote for Dolphin, getting it to (reliably) CRAWL through searches across documentation, newsgroup archives, and the image itself. Ian Bartholomew promptly made it FLY by comparison (measured in orders of magnitude, as I recall). Hopefully a similar coding style could buy us a big boost here.
Somewhat related, Dolphin's search for references to either the selected method or to text that can be entered in a prompter. The non- prompting search is available from a context menu in the method pane, so it tends to "just 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) 273-6785 FAX: (352) 392-7029
stephane.ducasse@inria.fr 08/20/08 5:51 PM >>> You bring the menu on the method pane then more.... then source code with .... it will scan all the methods for the string you pass
On Aug 20, 2008, at 10:09 PM, laurent laffont wrote:
Thank you.
I have another super newbie question. I want to disable the warning that SqueakV39.sources is not found when we load an image. I found the preference and the message Preferences>>warnIfNoSourcesFile but this is not called on startup (I've put a halt in it to check)
I try to find a tool to search for the string "Squeak cannot find the sources file named ..." to know which code popup the dialog.
I want to disable this dialog and the "Enter your initials" one by code in my squeakci script, as it prevent me from drinking my coffee or taking a nap while all tests runs without any human intervention.
Laurent _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On 21.08.2008, at 06:07, Bill Schwab wrote:
Dolphin's find-methods-containing-text is also MUCH faster than Pharo's. It might just be the relative speeds of the two systems (I hope not), lack of important primitives, or perhaps code that can be greatly improved.
The reason for slow search in source-text is that the sources are read from Disk. I did once a small experiment to store the source as a method property instead. This made the seach faster a lot. The whole source/changes stuff is really ugly. It was designed for a machine of 30 years ago and the code is a mess. In addition, it's ugly and slow. Marcus -- Marcus Denker -- denker@iam.unibe.ch http://www.iam.unibe.ch/~denker
participants (3)
-
Bill Schwab -
Marcus Denker -
Stéphane Ducasse