[Pharo-project] For milestone 2
Hi guys I would like to get DrDoc to document each package or bundle of packages. As part of the documentation I would also like to include SmallLint rules that have to hold. If you have any idea how we can support the creation of better package with meta data please let me know.
I would like to get DrDoc to document each package or bundle of packages. As part of the documentation I would also like to include SmallLint rules that have to hold. If you have any idea how we can support the creation of better package with meta data please let me know.
PackageInfo was designed so that it can be subclassed within packages to define additional meta-data. Currently only very few packages use this feature. The advantage of the existing mechanism is that Monticello already integrates with PackageInfo. Lukas -- Lukas Renggli http://www.lukas-renggli.ch
What is "DrDoc"? Adrian On Jun 22, 2008, at 09:27 , Stéphane Ducasse wrote:
Hi guys
I would like to get DrDoc to document each package or bundle of packages. As part of the documentation I would also like to include SmallLint rules that have to hold. If you have any idea how we can support the creation of better package with meta data please let me know. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Yes I was planning to migrate my solution so that the class I generate is a subclass of PackageInfo. On Jun 22, 2008, at 9:43 AM, Lukas Renggli wrote:
I would like to get DrDoc to document each package or bundle of packages. As part of the documentation I would also like to include SmallLint rules that have to hold. If you have any idea how we can support the creation of better package with meta data please let me know.
PackageInfo was designed so that it can be subclassed within packages to define additional meta-data. Currently only very few packages use this feature. The advantage of the existing mechanism is that Monticello already integrates with PackageInfo.
I do not get your last sentence. What kind of integration?
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Just a stupid little project I started to be able to add metadata (diagram, text,.... to packages). On Jun 22, 2008, at 11:17 AM, Adrian Lienhard wrote:
What is "DrDoc"? Adrian
On Jun 22, 2008, at 09:27 , Stéphane Ducasse wrote:
Hi guys
I would like to get DrDoc to document each package or bundle of packages. As part of the documentation I would also like to include SmallLint rules that have to hold. If you have any idea how we can support the creation of better package with meta data please let me know. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
I do not get your last sentence. What kind of integration?
Most prominent, Monticello dispatches through PackageInfo to find out what parts of the system belong to that package. Earlier versions of Seaside used this mechanism to have overlapping packages (e.g. for specific platforms). Furthermore PackageInfo defines a mechanism to define pre-load, post-load, pre-unload and post-unload scripts. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch
On Jun 22, 2008, at 2:11 PM, Lukas Renggli wrote:
I do not get your last sentence. What kind of integration?
Most prominent, Monticello dispatches through PackageInfo to find out what parts of the system belong to that package. Earlier versions of Seaside used this mechanism to have overlapping packages (e.g. for specific platforms). Ok but I think that this part should be change in the future to get first class package.
Furthermore PackageInfo defines a mechanism to define pre-load, post-load, pre-unload and post-unload scripts.
So I will hook into packageInfo. This should be one line change for what I have done (nothing exciting for now).
Cheers, Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (3)
-
Adrian Lienhard -
Lukas Renggli -
Stéphane Ducasse