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.