Hi again Mariano, 2010/1/4 Mariano Martinez Peck <marianopeck@gmail.com>:
On Mon, Jan 4, 2010 at 8:34 PM, Hernán Morales Durand <hernan.morales@gmail.com> wrote:
Hi Mariano, Â Thank you for the feedback, I've updated the dependency browser package in SqueakSource, have a look for the latest package releases or evaluate the installation script again found in http://swikicaicyt.homeip.net/WebOpus/65
Cool, thank you very much for your work.
Hey! I have more questions :)
3) Please, take a Pharo dev image and you will see that the package OCForOB for example, only depends on OmniBrowser and OB-Standard (using dependency browser). However, that package also depends on OCompletion I think. Look for example the method
OBTextPanel >> createCompletionController (category ocforob)
and you will see that it uses the class OController which is from the package OCompletion....So, shouldn't be OCompletion a dependency ?
True, it is fixed now in the latest release.
Yes, cool. At this in this case It is fixed :)
4) There are certain packages that are not listed in the dependency browser. Examples OB-Standard, OB-Morphic, O2-Standard , etc...most of them (maybe all) seem to have the pattern XXX-YYY. Do you know what can be the problem here? Maybe something related to what you told me about normalized and un-normalized? I would really like to see these packages also.
No, this was a missing line in the package listing. Fixed too.
This is not working very well. When you select OB , Refectoring or any other which is "not normalized" and it brings the popup, even selecting something the popup brings again and again and again....and I THINK the amount of times the pop up raises is the amount of packages you have as dependencies (the size of the collection of the right ;) Maybe this can help you to detect the problem.
Yes, I was aware of the problem, but I don't know if I want to fix it :) Seriously, the problem is a package name is not an object (well, it's a String...) so people can name packages as they want. (e.g. things like : MyPackage-MySubcategory1-MySubcategory2-MySubcategory3-... ) Besides that, or because of that, there are PackageInfo's for packages with names including arbitrary number of separators...please evaluate: ( PackageOrganizer default packages collect: [: pkg | pkg packageName ] ) asSortedCollection and scroll through Collections. There is a 'Collection' package and 11 more 'Collection-XXXX' packages. This kind of textual division of categories with separators is complicating things. My question is: Is the 'Collection' package one and there are 11 dirty package info's which should not be there, or there are 12 Collection packages and the one without subcategory name which is not shown in the Browser?
Another problem I have right now is this example: NewInspector. It extends the class ProtoObject with this method:
ProtoObject>> niChildrenBlockForFixedFields (an extension for NewInspector). In that method, it uses the class TypeCollector which is form RoelTyper. However, RoelTyper is not shon as a dependency.
Do you know what can be the problem ?
I have no idea but I will check it out, thanks for reporting. Cheers, Hernán