Squeak-dev March 2007

squeak-dev@lists.squeakfoundation.org

143 participants
204 discussions

[ANN][Squeak-dev Image] Version 83
by Damien Cassou 01 Mar '07

01 Mar '07

Squeak-dev image is an image made for squeak developers based on Squeak3.9-final-7067. If you use it, please tell me. You can download it here: http://damien.cassou.free.fr/squeak-dev/ Changes in this version: ------------------------------ - Finally add connectors (sorry for this package) - Prepare Browser Booster - Add a new shortcut to KeyBinder : CTRL+k opens a Workspace (a Shout workspace if installed). - RoelTyper is now downloaded from SqueakSource - Prepare LambdaMessageSend - Bad comment in Connectors - Add example for DebugReport and Sixx - Change minnow.cc.gatech.edu to wiki.squeak.org As usually, all installed packages have been updated. Prepared packages: -------------------------- There are a lot of packages prepared for you in this image. They are not loaded in the image, but they can be easily: - Open ScriptManager (world->open...->Script Manager). - Go to 'Prepared packages' folder (on the left). - Select the package you want to install. - Click the link at the very bottom of the text. Future work: ---------------- - Wait for feedback. - Use Lex Spoon's universes instead of prepared packages. - Base squeak-dev image on Keith Hodges 3.9.1. - Try to pre-download prepared packages (I tried but don't know how to use Monticello like this) Please tell me what is your experience with this version. Please tell me what you want for this image, this is for you. -- Damien Cassou

3 4

packaging style requests
by Lex Spoon 01 Mar '07

01 Mar '07

I have two requests for packaging style, after having delved through 100+ packages for the 3.9 stable universe. First, SAR's with fancy load-time scripts are often too smart for their own good when used in a package universe. A particular example of this is load-time options. Instead of having a single SAR with a load-time option, I wish people would divide the package into smaller packages. Then people can install precisely the component packages they want. As an example, if package Foo's tests are considered optional, then just make it two packages. Post Foo and Foo-Tests, where Foo-Tests depends on Foo. Second, we have a lot of readme windows popping up. A readme popup is very friendly if you are installing 1 package. However, with a package-browsing tool, it's not uncommon to install 5 or 10 packages at a time. When you do so, you end up with more windows than the user can possibly pay attention to. I was installing 100 at a time recently, and the result was just comical. I would like it if we had a registry of readme's, so that packages do not clutter up the main screen just to announce they are now loaded. This would help at package-loading time, and also it would mean people can actually find this documentation again weeks later after the package is installed. Barring such a tool, how about we limit ourselves to one readme per program? You an always add hyperlinks to the other ones. Okay, that's my wishes. Do with them as you will. Happy Squeaking, all! I've had fun browsing through all the great things everyone has posted. -Lex

4 7

Profile with fork
by Frédéric Pluquet 01 Mar '07

01 Mar '07

Hello, I want profile my work to find how reduce the execution time. In my framework I do a lot of fork, creating processes. When I profile, via MessageTally spyOn: [], only the "active" process (the father) is profiled and I don't have any information on the subprocesses :-( Is there a simple way to resolve my problem ? Must I use an another tool ? Thank you for your future answers, Fréd ___________________________________________________________________________ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com

7 7

RE: Exporting Namespaces
by J J 01 Mar '07

01 Mar '07

+1. Just please, no colons. Or at least make it configurable so I don't have to see it. :) The best would be if direct namespace access looked like normal message sends. >From: "Alan Lovejoy" <squeak-dev.sourcery(a)forum-mail.net> >Reply-To: The general-purpose Squeak developers >list<squeak-dev(a)lists.squeakfoundation.org> >To: "'The general-purpose Squeak developers >list'"<squeak-dev(a)lists.squeakfoundation.org> >Subject: RE: Exporting Namespaces >Date: Sun, 18 Feb 2007 17:40:35 -0800 > > > > <Michael van der Gulik> I have an image. In that image is a Namespace. I >need to get that Namespace and the source for the classes in that Namespace >out of that image and in to another image somehow - usually done using e.g. >Monticello, filings stuff out, etc. > >The format for SqueakV9.sources, squeak.changes, changesets and file-outs >will have to change a bit if they were to support Namespaces. Rather than >changing the format, another option is to chuck everything out the window >and use a different system, such as keeping the source code and version >information in the image as Text objects. I'm just wanting people's >opinions >on the technical merits of the options I mentioned in the root of this >thread. < / Michael van der Gulik> > >Ok, thanks for the explanation. I think I now understand your problem. > >My suggestion: Namespaces should be constructed by message sends, just like >classes are constructed by message sends. The instructions to >create/modify >namespaces should be encoded in a file out as "do it" chunks--again, just >like class definitions. This may not be the ideal solution in the long >run, >but it's the only workable/acceptable solution initially. > >I would avoid changing the canonical message sends that define classes if >at >all possible. If necessary, send additional namespace-related messages to >classes in separate "do it" chunks. > >The namespace-related "do it" chunks should silently short-circuit if the >receiving image doesn't support namespaces (although a single warning >message for each file-in might be nice--perhaps a UUID for each file-out >would make that possible.) Or, perhaps your Namespace module could be >auto-installed from SqueakMap or SqueakSource, when needed. > >Evolution almost always works a lot better than revolution. Don't fight >against the tide. Go with the flow. When life hands you a lemon, make >lemonade. > >--Alan > _________________________________________________________________ Dont miss your chance to WIN 10 hours of private jet travel from Microsoft® Office Live http://clk.atdmt.com/MRT/go/mcrssaub0540002499mrt/direct/01/

3 4

Jump to page: