[Pharo-project] Improve pharo modularity: a first step
Hi all, I would like to improve the modularity of packages in pharo. A first simple thing that I see, is methods "example" use a lot of things in the system. And create cycles between packages. So, I propose to create a new package named "Examples" and put in it all methods named "example2"... Jannik
2009/10/23 Laval Jannik <jannik.laval@gmail.com>:
Hi all,
I would like to improve the modularity of packages in pharo.
You might want to look at it: http://www.comtalk.cz/Squeak/98
A first simple thing that I see, is methods "example" use a lot of things in the system. And create cycles between packages.
So, I propose to create a new package named "Examples" and put in it all methods named "example2"...
Just a warning: if you gather all examples irrespectible to packages, you will create a single package with a lot of dependencies.
Jannik
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Best regards, Igor Stasenko AKA sig.
Jannik may be we should have PackageCore PackageTest PackageSetting PackageExamples in the future On Oct 23, 2009, at 9:02 AM, Laval Jannik wrote:
Hi all,
I would like to improve the modularity of packages in pharo.
A first simple thing that I see, is methods "example" use a lot of things in the system. And create cycles between packages.
So, I propose to create a new package named "Examples" and put in it all methods named "example2"...
Jannik
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Hi Stéphane, Am 23.10.2009 um 12:50 schrieb Stéphane Ducasse: > Jannik > may be we should have > > PackageCore > PackageTest > PackageSetting > PackageExamples A convention we follow here is - for VA Smalltalk code, though: - Package (includes all code needed at runtime) - PackageDev (includes all code needed only at Development: tests, scripts, tools) This allows for nicely separating runtime packages from those only needed for development while keeping the numbers of packages smaller. Just my 2 cents. Cheers, Bernhard
yes we did the same in VW. Stef On Oct 25, 2009, at 6:45 PM, Bernhard Pieber wrote: > Hi Stéphane, > > Am 23.10.2009 um 12:50 schrieb Stéphane Ducasse: >> Jannik >> may be we should have >> >> PackageCore >> PackageTest >> PackageSetting >> PackageExamples > A convention we follow here is - for VA Smalltalk code, though: > - Package (includes all code needed at runtime) > - PackageDev (includes all code needed only at Development: tests, > scripts, tools) > > This allows for nicely separating runtime packages from those only > needed for development while keeping the numbers of packages smaller. > > Just my 2 cents. > > Cheers, > Bernhard > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Em 23/10/2009 05:02, Laval Jannik <jannik.laval@gmail.com> escreveu:
Hi all, I would like to improve the modularity of packages in pharo. A first simple thing that I see, is methods "example" use a lot of things in the system. And create cycles between packages. So, I propose to create a new package named "Examples" and put in it all methods named "example2"...
I agree there are opportunities for improvement in Pharo's packages but I see the attempt to lump _all_ examples in a single package as a backward move. I think a better approach would be similar to the on going discussion on the tests packages. We should have the package for the specific functionality, some convention on the test (generally Unit Test, which some argue also make as some part of the usage examples) related package, and some convention on example related package. I would argue even further that we should have a documentation related package, but that will digression right now! my .019999.... -- Cesar Rabak
participants (5)
-
Bernhard Pieber -
csrabak＠bol.com.br -
Igor Stasenko -
Laval Jannik -
Stéphane Ducasse