Steven Baker wrote > using Spec It really depends on your aim. The *idea* of Spec was to write once and deploy "everywhere", but as yet there is only a Morphic backend that I know of, and you would be restricting yourself to standard desktop widgets. So, if that is not a problem, Spec might be an easy route to a working application. If you want to create a more imaginative UI, you'll probably have to hand roll on each target (e.g. Morphic for desktop, PharoJS or Amber for web).
Steven Baker wrote > a GTD application in the spirit of nirvanahq, omnifocus, things, nozbe Cool! I'll be your first customer ;) Steven Baker wrote > Are people using one-per-project, or one-per-computer? Yes and yes. I prefer one per project for development projects I'm working on and one per computer for personal images (a la my own personal Dynabook). The former is also fine for personal tools, but the latter can get hairy e.g. if you're digging into the system and accidentally break an image with all your personal data in it (assuming I'm not the only one who is a little sloppy with persistence in personal contexts ha ha)[1]. Steven Baker wrote > Anyone using > PharoLauncher these days? Other tools? Yes! I now use it exclusively and love it. There are minor hiccups here and there as Pharo rapidly evolves in parallel, but Christophe and team are really responsive and helpful. I also made a project called SmallWorld [2] which is like my own personal SqueakMap/Project-catalog that keeps track of projects I care about. What makes it a little different that e.g. Pharo Catalog is that it lets me specify how *I* want to load a project (e.g. which repo/branch), which may not be the canonical way, especially if I am typical in a developer role and not a user. I built a tiny extension which hooks this into Launcher, providing a button to automatically load one of these projects into an image of my choice. Beware I am the only user (that I know of), so the UI is very primitive (a combination of GT and Magritte), but I'm happy to help anyone along if the idea seems helpful. <http://forum.world.st/file/t128965/Screenshot_2017-10-02_11.jpeg> Steven Baker wrote > I'm assuming that the current state of the art is Iceberg; where can I > find a "This is how you should organize your project using Iceberg" > document, blog, book, tutorial, video, or otherwise. As Esteban mentioned, Iceberg is a vcs, so if you mean how to organize *code*, Pharo handles this automatically under the hood. The only thing you have to decide is the root folder. Typically people choose a top level folder inside the git repo for this, named 'source' (or 'src', 'repository', or 'mc'), so that you can have other top level categories like wiki, scripts, etc. If you mean project in a wider context, as in including documentation, this seems to be an open field with many different possibilities. I can't help on the other parts of your question, but am eager to hear any answers! [1] Although the beauty of Smalltalk is that there's (almost) always a way forward (see http://forum.world.st/Fwd-Oops-I-put-a-halt-in-a-startup-method-tp3800729.html) [2] https://github.com/seandenigris/Small-World ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
