> 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...
Yep, thank you Sean - this more or less nails it. Squeak projects are what comes closest to what i need to be able to quickly change context. It is perfectly ok to have them just in the image without any possibility for load/save. As for the IDEA comparison I raised, there is a big difference in my work style when switching tasks in IDEA/Java and Smalltalk. My impression is that for one this is because in Smalltalk you "live" inside your objects (image) while in Java you mostly have the edit-compile cycle. Also, traditional Smalltalk Browsers show you just one small piece of code (method) at a time while in file oriented environments you think in Files and scroll to get to a method. So what I do in Smalltalk is placing a couple of Browsers, workspaces and often also instances of the developed objects (!). Switching context means to destroy all this setup, and manually build another one. Switching bask, I have to redo all this for my former setup. (I could imagine that all this is a bit less of an issue in web development but I have too little Smalltalk experience here). > Projects as described might be similar to Dolphin's IdeaSpace. For whatever > reason, I never liked them very much, so I am not the best person to comment. I share with Bill that I never use IdeaSpaces in Dolphin. However, IdeaSpaces are very different from Squeak projects as they just allow you to group browsers and workspaces with tabs which does (IMHO) not match Smalltalk work style for above reasons and I would not need a similar tool in Pharo. To summarize, I would be perfectly happy with a streamlined projects implementation that just gives you different view to dive into without any need to save them outside the present image. Ciao ...Jochen Am 02.06.2010 um 15:58 schrieb Sean P. DeNigris: > > > 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 _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
