Hi, now that we have multiple branches & image types I want to improve
the publishing of test results. I'm lacking a neat way to get the image type and branch number. I don't really want to parse the image file name. Seems the best thing to use is: SystemVersion current version. Is there anything else? results: Pharo Core 1.0 --> 'Pharo1.0rc1' Pharo Core 1.1 --> 'Pharo1.1a Pharo 1.0 --> 'Pharo1.0rc1' We could add some state to SystemVersion, e.g #imageType, #branch, or we agree on a convention for #version that can easily be parsed. What do you think? thanks, Mike _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
good idea.
Now this class should not be alone in one package. Stef On Nov 4, 2009, at 9:17 PM, Michael Roberts wrote: > Hi, now that we have multiple branches & image types I want to improve > the publishing of test results. I'm lacking a neat way to get the > image type and branch number. I don't really want to parse the image > file name. > > Seems the best thing to use is: SystemVersion current version. Is > there anything else? > > results: > Pharo Core 1.0 --> 'Pharo1.0rc1' > Pharo Core 1.1 --> 'Pharo1.1a > Pharo 1.0 --> 'Pharo1.0rc1' > > We could add some state to SystemVersion, e.g #imageType, #branch, or > we agree on a convention for #version that can easily be parsed. > > What do you think? > > thanks, > Mike > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
> Now this class should not be alone in one package.
do you mean it shouldn't be in System-Support? Or in a better named package? System-Support is a mixed bag of classes. thanks, Mike _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
No I checked by accident after and this is better than before because it was in SystemVersion packge :)
On Nov 10, 2009, at 9:29 PM, Michael Roberts wrote: >> Now this class should not be alone in one package. > > do you mean it shouldn't be in System-Support? Or in a better named > package? System-Support is a mixed bag of classes. > > thanks, > Mike > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
ok cool.
before i propose changes, does anyone have any opinion on this mantis entry copied to our tracker. Damien? http://code.google.com/p/pharo/issues/detail?id=1012 If no one does I suggest to close it. thanks, Mike On Tue, Nov 10, 2009 at 8:38 PM, Stéphane Ducasse <[hidden email]> wrote: > No I checked by accident after and this is better than before because it was in SystemVersion packge :) > > On Nov 10, 2009, at 9:29 PM, Michael Roberts wrote: > >>> Now this class should not be alone in one package. >> >> do you mean it shouldn't be in System-Support? Or in a better named >> package? System-Support is a mixed bag of classes. >> >> thanks, >> Mike >> >> _______________________________________________ >> Pharo-project mailing list >> [hidden email] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Free forum by Nabble | Edit this page |