I think you are missing the OP's point. The goal (unless I am missing something) is to have a way to open say four browsers on specific classes and methods and maybe a workspace or two to work on one particular project/task, and to do the same for other tasks. All of this stuff would remain readily accessible with a high-level "table of contents" that allows on to enter a task, change something, and then switch to another task.
My argument against this would be that it seems potentially memory hungry and perhaps sluggish due to all of the potentially invisible tools' updating themselves on various events, but if we ignore it in our images, we won't suffer much. I agree that doing this with separate images is a step backward. Bill ________________________________________ From: [email protected] [[email protected]] On Behalf Of Geert Claes [[email protected]] Sent: Wednesday, June 02, 2010 10:38 AM To: [email protected] Subject: Re: [Pharo-project] Can I use Projects in Pharo? I guess a project in an image-based system is not always easily defined. What is a project exactly? Is it a morphic application, a seaside/AIDAWeb/Iliad based web app, a new framework, a shared component? Which part of the image needs to be "in the project"? Maybe I am wrong here but with the new package management system everyone can freely load and unload "projects" they want to work with/on from repositories like PharoSource uuuh SqueakSource :) -- View this message in context: http://forum.world.st/Can-I-use-Projects-in-Pharo-tp2239170p2240239.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ 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
