Stéphane Ducasse wrote: > > to do what? > which one exactly? >
The only thing I use projects for is to separate the different tasks I am working on at the same time (like spaces on the Mac), so I can have one world where I'm working on a client project, and a whole other world if I find a bug in the system that I want to fix - I want to move to another world, fix the bug, and move right back to my client world, with the windows exactly the way I left them. For my use case, saving projects doesn't come into play. Why not remove the save functionality, since that seems to be the objection everyone raises, and keep them as a workspace organization tool - in image only? Lukas Renggli wrote: > > I have my different "projects" in different images. That works perfectly. > For my workflow, this is too heavyweight. In my mind, that's like buying multiple separate computers to run different apps. Even though I am working on multiple tasks at once, they are not *that* different. For example, in my "fix a bug" task above, I want the fix to be in my working image (which is automatic in the projects solution), without having to load into all the other images I'm working on. One of the killer features of Squeak/Pharo to me is that the whole system is available to itself. If I start breaking the image into smaller task-based images, it feels like going back to applications and files - yuck! ;-) Sean -- View this message in context: http://forum.world.st/Can-I-use-Projects-in-Pharo-tp2239170p2240170.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
