You didn't ask, but here's how I see it on pakages :) PackageInfo **ABUSES** method categories to associate methods with packages. Methods should be able to belong to multiple categories (you won't miss it until you can do it), and to one package. Dolphin also has a class category option, but I am not aware that anyone ever found it useful - packages are enough to categorize classes. I don't know a nice way to say it: if you are confused about packages, ditch the package browser for a while. I have not used it for a few versions, but I was shocked at how slow it could be, and began to suspect that its behavior was (queue throat-clearing.wav) not deterministic. Another possibility (if this level of re-entrancy is possible??) is that it is SO slow that one fails to appreciate that it is still crunching on the organization?? Bill -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of GeertClaes Sent: Friday, December 18, 2009 3:48 AM To: pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Default code browser Schwab,Wilhelm K wrote:
Re the various browsers, they are not terribly well identified, so it takes work to figure out what I am using.
+1 here Other than that, I find that none of the browsers are at this stage great yet from an intuitive, usability point of view (mind you, I consider myself to be very 'newbie'). I am also looking at Pharo + Seaside or AIDAWeb mainly as an IDE tool to create web apps as I am not that interested (or skilled for that matter) in tinkering with the core. I am hoping that the new package management system (MetaCello in Pharo 1.1?) will streamline some of the confusion and allow the user to have the option to somehow hide "system" or Pharo-Core packages from the IDE. I could be wrong here, but methods of a class can be nicely organized using protocols ... and then there is this whole vague, confusing world of how classes are managed in categories and packages ... but the term package could actually also refer to a category, which is actually a package, but a package can also be a Monticello package, which could be different than the category or should I say package? All this may make perfect sense to the gurus but it is extremely confusing, because packages also need to be able to be grouped into projects (is this the term?) and have dependencies on other packages and/or projects? I haven't even mentioned the confusion of SqueakMap/PharoMap, SqueakSouce/PharoSource, Monticello and Universes. -- View this message in context: http://n2.nabble.com/Default-code-browser-tp4183317p4185502.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project