When I said the package browser+MC was not deterministic, I meant it. My experience was that _sometimes_ packages would be created from categories, and sometimes not. Things get more clear if you fire up the MC GUI and explicitly create a package. Then it suffices (with the other browsers at least) to put a class in the corresponding category, and to categorize methods with *packageName (yuk!!!!, but it works). There are MC tutorials, and you should read one if you have not already done so. My biggest gripe is that I find myself being forced (AFAIK) to type category names far more often than should be the case. There is what appears to be "recent categories" list but it is both hard to read and (I suspect[*]) not predictable. May the overseers be with you if you ever type something with a bad mix of capitalization - deleting the offending package never seems to rid the image of it. As Murphey would have it, type something wrong and the tools never forget; type something correct and you will end up typing it again, at least until you no longer need it :( That is based on fixing a many badly-formatted category names created by SIF. FWIW, I have learned how to use the regex package to make changes to a .sif file before loading it into Pharo, which is a nice way to go. For now, I get along fairly well and am looking forward to a new package system. What I find beyond comprehension is that the rough spots have not been fixed. In my relatively short time making real use of Pharo, I have found it essential to "clone" tools that I use in Dolphin to manage packages. The core of it is no longer an absolute must in Dolphin, mostly because its package system has improved over the years. However, I have something that attempts to identify "your" work that is not assigned to one of a collection of packages identified to it, provides one-shot saving of those packages, and can "easily" be loaded into a new image and load the packages into it. It is rough around the edges, but I plan to make it available to anyone who wants it after it settled down a little more. One thing I would like to be able to do is to create separate .mcz files for Migrate-core and Mirgrate-uf, with assurance that **nothing** from Migrate-uf will end up in Migrate-core.mcz. So far, that is not happening, perhaps my fault. Since I have been spouting complaints all day, I should mention that I have noted that a Pharo image has been serving a Seaside app off of a vmware based win2k3 machine, and has done so with higher reliability than vmware itself, or so it seems. I have frequent problems with network routing, but it appears to happen only when pings fail to the offending host, and magically gets fixed when the pings begin to succeed again. Any déjà vu?? I'd like to hear about how you fixed it. Reports on the net suggest that it could be a known and long-standing defect. I have also had DNS related hassles, but is really no surprise. Years ago, I learned the hard way to disable XP's DNS cache service; it is said to be essential to win2k3, and I hesitate to learn the hard way on a vm. In short, Pharo sucks a LOT less than Windows :) Bill [*] Not meaning to spread FUD, just being honest about my observations. -----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 12:31 PM To: pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Default code browser Schwab,Wilhelm K wrote:
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 think I am with you that class categories are probably a bit overkill here since these class types are already grouped in separate (monticello) packages . Schwab,Wilhelm K wrote:
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??
It's not just that I am a bit confused or think the package browser is too slow, from a usability point of view it just does not make sense to me that it seems so complicated to load/share packages from other projects and/or components. Maybe this discussion belongs more in the 'Pharo IDE usability (was Re: Pharo for Professional Development) ' thread now? -- View this message in context: http://n2.nabble.com/Default-code-browser-tp4183317p4187788.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