Re: [Pharo-project] Product Brand Pharo
Gary, There are two topics here: (1) allowing ourselves and others to easily retrofit tools into the various menus; (2) building a fast and elegant GUI framework. BookMorphs are a (not terribly good) implementation attempts at the latter. For the newbie (or even us trying to get something done), it can be very helpful to have tools offered in the right places. Cleaner is better of course, but the "user" in the case is more interested in whether the tool works than in how the tool works. Set out to write your own helpful wizard, and elegance is appreciated. 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
gazzaguru2@btinternet.com 09/23/08 7:16 AM >>> I remember doing a "Wizard" framework in VisualAge... shudders... Still, nice to have standardised support for such things rather than ad-hoc BookMorphs (for example).
Regards, Gary. ----- Original Message ----- From: "Bill Schwab" <BSchwab@anest.ufl.edu> To: <pharo-project@lists.gforge.inria.fr> Sent: Tuesday, September 23, 2008 12:03 PM Subject: Re: [Pharo-project] Product Brand Pharo
Markus,
Based on the discussion, I started noting how long it takes my images to load; a splash screen might be in order; I also fear that by the time VM loads and the GUI is able to draw itself, it is no longer needed :( Still, I'd add it to the milestones, but probably late in the process.
About help, I am not very sympathetic on the "no documentation" front. Someone seeking to join us will quickly find tutorials, and can post questions. Dolphin's MVP framework almost invariably had the newbie expressing pain and confusion, followed by "why was this so hard last week???" Conversely, the MS Office IDL for Automation has LOTS of "help" - almost all of it useless. The message (pun intended) needs to be "this is not trivial to learn, but very worth your time." Ensuring that good tutorials are linked from our Wiki would be a nice gesture.
Wizards in the IDE - that's a very good idea, and Dolphin helps it along through the IDE extension framework, which is little more than events triggered at the right time, off of each tool's class and giving the needed instances for the code to make the desired changes. Dolphin's view resources, and our lack of them, would require some adaptation. However we do it, it would be a nice addition. The idea is to do _something_ that allows each of us to provide hooks into the IDE w/o having to alter the code. That way, building a new image and updating an existing one will not destroy the extensions.
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
_______________________________________________ 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
My thoughts about splash. It could be useful only in case, when there is not a VM who driving it, but image instead. Yes, image, at the point when it just loaded, can instruct VM to show window with splash image (held in image, not in file,btw), and show some progress bar during its initialization, and then destroy this window and create a normal main window (if its required). Of course this will be possible only when all windowing could be controlled by language side through HostWindowPlugin, which i proposed earlier, not by VM like currently :) -- Best regards, Igor Stasenko AKA sig.
participants (2)
-
Bill Schwab -
Igor Stasenko