I would like to use the seaside convention so is it ok for you? Then I will proceed and rename eveyrthing. stef On Jan 31, 2009, at 10:51 AM, Stéphane Ducasse wrote:
I like the seaside organization
Top-(Purpose-)(Platform-)Rest
* Seaside-Canvas contains he canvas implementation. * Seaside-Squeak-Canvas contains the platform specific code of the canvas implementation. * Seaside-Examples-Canvas contains example code showing off the canvas implementation. * Seaside-Tests-Canvas contains the tests for the canvas implementation. * Seaside-Tests-Squeak-Canvas contains the platform specific tests of the canvas implementation.
On Jan 30, 2009, at 3:54 PM, Adrian Lienhard wrote:
On Jan 30, 2009, at 15:33 , Michael Rueger wrote:
Stéphane Ducasse wrote:
so what are the organizations we can use? Ideally I would like to have the test associated with their packages.
XXX XXXTests
The problem with that naming scheme is that then the tests would always be loaded together with their tests because of the simple string matching Monticello does. Which isn't something you want when doing application/runtime builds.
That's why I proposed the Plugin-* and Tests-* naming schemes.
+1
Adrian _______________________________________________ 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