Thanks for all the great feedback! It's great to discuss because it makes me think about what's really important and why... Mariano Martinez Peck wrote:
I think we should not reinvent the wheel in Pharo. I mean, Morphic is nice, although I would like to have native windows so that I can use my Mac expose features. But no, I have only one window.
I secretly pray for a world where the OS/application paradigm disappears like T-rex in a meteor shower ;-) and I do a lot of cross-platform work (Windows and Mac mostly), so relying on OS features doesn't work for me. Mariano Martinez Peck wrote:
Then, I have something similar but implemented in Pharo using Mac + narrows.
Do you mean the window cycling within Pharo? That's not all that similar! It still has totally (logically) unrelated windows fighting for screen space. There's no way to bring up the *set* of windows related to task A, and then back to B. Mariano Martinez Peck wrote:
I also have tons of image, and each image (or more than one) for a project. Why don't you use your own OS virtual workspaces and spread you different images over the different workspaces? that's easier than Squeak Projects. And maybe faster and better supported.
This seems to come down to vision and work habits. My vision is to use one image for everything, where all my data is available to all other data, and I can explore interesting relationships between (seemingly) unrelated bits. Using many images, to me, is a giant step back toward existing mainstream options. Plus, anything we do in Pharo is infinitely user customizable and fixable - not so with OS features. For example, I have exactly three options for the space-switching shortcut on the Mac - wow, thanks for all the options! Mariano Martinez Peck wrote:
- In Pharo we have a good package management system now (Metacello). If you use it correctly, you can define all your project dependencies (even working in a core or dev image). So you should be able to load your project in any image without any problem.
Yes, definitely! Metacello is great for sharing and deploying, but again, using one system for everything is one of the key reasons I came to the Squeak/Pharo world - if I wanted everything separate, there is Mac software for each task that probably (due to maturity and market) does each better. Mariano Martinez Peck wrote:
- We release images quite frequently, much more than other dialects/languages. So...usually you don't have to wait too much to get a new image with the fixed issue.
[gasp] complain and wait until my issue is fixed!!! I can't imagine it ;-) When I find an issue, if I can, I fix it myself and move on with my work. Mariano Martinez Peck wrote:
- How many times you find an issue that affects all your projects? I don't think this is very common. Usually, when I find a bug or a problem, is not "too" core in the sense that only affects me in a particular place, but not in all my other work.
Often enough with the tools. Two quick examples: * while using SSpec, I've found and fixed various bugs, e.g. in the test runner, which effected all the projects I'm working on simultaneously. I didn't want to stop what I was doing, upload the project, write a Metacello configuration for it, and install it in X other images, and I didn't have to because I only had one image. * while working with the monticello browser, every time I wanted to add a "directory" repository (which I do frequently), I had to start searching from the default directory, even though all my repos are in the same parent folder. So I added a setting for it and kept working. Summary: For me, the separate image approach is a hack to simulate a missing feature, with tradeoffs that don't work for the way I do. Cheers, Sean -- View this message in context: http://forum.world.st/Can-I-use-Projects-in-Pharo-tp2239170p2241621.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.