Send the code. Stef
On Dec 21, 2008, at 11:44 PM, Bill Schwab wrote: > Sounds good. And in that case (OB Tools at the end of the list), I > urge > serious attention to having a notifier. Learning from history, and > all > that. > > Bill > > > > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: [email protected] > Tel: (352) 273-6785 > FAX: (352) 392-7029 > >>>> [email protected] 12/21/08 5:31 PM >>> > Here is an answer for "what is Pharo?" > > There will be two images: > "Pharo-Core": the image in which the development of Pharo takes place > "Pharo": the image to develop your application with (= "Pharo-Core" + > IDE tools [1]) > > "Pharo" is the image that will be officially shipped (packaged as a > one-click image). "Pharo-Core" on the other hand will be important for > deployment as it has a low memory footprint. > > Cheers, > Adrian > > [1] http://code.google.com/p/pharo/wiki/Packages > > > On Dec 21, 2008, at 15:46 , Bill Schwab wrote: > >> Lukas, >> >> You are correct to question "what is Pharo?" We cannot hope to >> ensure >> that everything anyone ever does with Pharo will work - those kinds >> of >> promises are made only during political campaigns :) But, note the >> recent discussion of package integrity. It should be as easy as >> possible to install anything one wants, but the things that Pharo >> invites the user to install should be solid. Certainly, the >> development >> tools should fall into that category. >> >> For example, I have a love/hate relationship with the RB, but I >> certainly hope to see it integrated into Pharo. But given a choice >> between a polished presentation of the RB commands and a stable >> system, >> I'll go for the stable system. We should have both. >> >> Bill >> >> >> >> >> Wilhelm K. Schwab, Ph.D. >> University of Florida >> Department of Anesthesiology >> PO Box 100254 >> Gainesville, FL 32610-0254 >> >> Email: [email protected] >> Tel: (352) 273-6785 >> FAX: (352) 392-7029 >> >>>>> [email protected] 12/21/08 3:07 AM >>> >>> My understanding is that the OB tool set is the presumptive choice >>> for >>> Pharo - unless I'm wrong, that makes this a Pharo related topic, if >> only >>> to reopen the choice in light of your position. >> >> I don't know which is the official Pharo image? There is a plain one >> without any extras loaded that the Pharo team uses for their >> releases, >> and then there is one with additional tools loaded by Damien that >> also >> contains OB-Tools. >> >>> Do as you want, but >>> Object Arts had this idea and very quickly decided the simpler >> notifier >>> had a very essential role. They left the option, activated the >> notifier >>> by default, and strongly warned against deactivating it. That was >> based >>> on being bitten by the kinds of concerns I have documented here. >> >> Don't get me wrong. Feel free to add this preference and the >> additional dialog, but don't expect me to do it: >> >> http://mail.wiresong.ca/pipermail/ob-dev/2008-August/000580.html >> >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
