Posted by
Lukas Renggli on
Jul 14, 2010; 11:34am
URL: https://forum.world.st/Evaluation-of-Pharo-for-Commercial-Project-tp2288574p2288596.html
> 1 - Package Management
>
> From what I have seen so far, the concept of “packages and categories”
> is confusing. We are used to VisualAge and VisualWorks, which clearly
> shows the structure of packages in the browsers. In Pharo we cannot
> find browsers which give us the same overview. We are uncertain how
> packages are made and how they show up in Monticello. At one point we
> thought category == package, but that seems not to be correct. We note
> that method extensions are possible, but we also struggle to
> understand all aspects of them.
You might want to read the chapter on Monticello from Pharo by Example 2:
https://gforge.inria.fr/frs/download.php/27018/Monticello.pdf> 2 - Dependency Management between Packages
> Since we are unable to organize our code in packages, controlling and
> verifying dependencies between them is hard. But from what I
> understand, there are not many tools for controlling that packages do
> not break dependency rules.
For Seaside we wrote some tools to manage our 80+ packages and their
dependencies:
http://source.lukas-renggli.ch/packaging> 3 - Name Space Support
> I understand name spaces will not be supported any soon. We have a
> project with thousands of classes, and name space support would be
> nice to have.
Albeit nice, it is not a big deal not to have first class namespaces.
Again see Seaside.
> 4 - Break Point Support
> It would be better to have break points, than having to insert code
> like “self halt” into the code.
I think there is support, see the class BreakpointManager. I have
never used it though.
Lukas
--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
Pharo-users mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users