On Dec 17, 2009, at 12:34 AM, csra...@bol.com.br wrote: > OK. I agree that this advice is important enough to make part of the Welcome > message we're > suggesting to bring back too. > > OTOH, is we could version the scripts that would be very nice!
We can: you have class methods. > > > > > Em 16/12/2009 15:16, Stéphane Ducasse < stephane.duca...@inria.fr > escreveu: > > > So send it back and we will integrate it. > No problem. But really you should use class side methods and versioned these > damned scripts. > > Stef > > >> Stef, >> >> I also miss the ready ability to save a workspace. With respect, it is not >> your place to dictate working methods. You are correct that one can easily >> over-use workspaces and under-use class methods. However, one can also >> over-use class methods when a new test case is more appropriate. >> >> Rather than removing basic features, we should add capabilities to encourage >> good practice by making things as easy as possible. Dolphin's IDE >> extensions are a nice feature that I *really* miss in Pharo. One thing I >> added is a way to create test case methods based on a currently selected >> method. Each class can specify a TestCase subclass, and the methods were >> automatically named based on the selected method's name; the code is >> generated and proposed for optional compiling with warning of conflicts. >> >> Bill >> >> >> -----Original Message----- >> From: pharo-project-boun...@lists.gforge.inria.fr >> [mailto:pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Ramiro >> Diaz Trepat >> Sent: Wednesday, December 16, 2009 8:44 AM >> To: Pharo-project@lists.gforge.inria.fr >> Subject: Re: [Pharo-project] [newbee] How do I save the contents of a >> Workspace? >> >> I really miss that feature. >> In my oppinion it is very useful when you regularly use different images, or >> when you frequently rebuild your development image from newer versions. >> Also, I wonder if the Package Browser should be removed completely since it >> does not even open now when you select it as preferred. >> >> >> -----Original Message----- >> From: pharo-project-boun...@lists.gforge.inria.fr >> [mailto:pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Stéphane >> Ducasse >> Sent: 16 December 2009 12:07 >> To: Pharo-project@lists.gforge.inria.fr >> Subject: Re: [Pharo-project] [newbee] How do I save the contents of a >> Workspace? >> >> for me it was political/educational to remove it. >> >> I saw too many people having expressions in workspace and not in class >> methods (not versioned with the code). >> because if this is really important why not put it in a class method? >> Then you load the code and of course you do not get the magic example >> beacuse they were in the wonderfull scripts left in the other images..... >> >> Stef >> >> On Dec 16, 2009, at 12:51 PM, Cédrick Béler wrote: >> >>> I think this is a valuable feature. >>> >>> Should we save in a particular file extension (.wst ? or simply text files >>> ?) so that we can also have load opening from a a list of files of that >>> format. This would be nice for tutorials instead of saving workspace >>> content in a method. >>> >>> Cédrick >>> >>> 2009/12/16 alesch On Wed, Dec 16, 2009 at 11:45, >>> Damien Cassou [via Smalltalk] <[hidden email]> wrote: >>> >>> On Wed, Dec 16, 2009 at 9:29 AM, alesch <[hidden email]> wrote: >>>> I remember I used a menu item in Squeak, but I cannot find in Pharo. >>> >>> You can't. Do you misss that feature? >>> >>> Yes I do. >>> >>> >>> View this message in context: Re: [Pharo-project] [newbee] How do I save >>> the contents of a Workspace? >>> >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> >>> _______________________________________________ >>> 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 >> This email is confidential and subject to important disclaimers and >> conditions including on offers for the purchase or sale of securities, >> accuracy and completeness of information, viruses, confidentiality, legal >> privilege, and legal entity disclaimers, available at >> http://www.jpmorgan.com/pages/disclosures/email. >> >> _______________________________________________ >> 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 > > > _______________________________________________ > 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
