[Pharo-project] Polymorph
All "fun" on squeak-dev... Getting close to abandoning support for Polymorph in Squeak at all now... Only a few apps based on 3.9 left here. Not sure they need any of the ongoing improvements. So, the question is, how would we want future additions/changes/fixes to apply in Pharo. Having Polymorph as an external (mergable, not loadable) package has worked well for us, as much as it can be well. Perhaps changesets are the way to go from here... opinions/advice welcome... Regards, Gary
On Mar 13, 2010, at 5:56 PM, Gary Chambers wrote:
All "fun" on squeak-dev...
Getting close to abandoning support for Polymorph in Squeak at all now... Only a few apps based on 3.9 left here. Not sure they need any of the ongoing improvements.
I'm not sure that maintaining two version is an option for you.
So, the question is, how would we want future additions/changes/fixes to apply in Pharo.
The way you were doing them is ok. You could also publish directly in Pharo But if you want to have you own package and control over it this is ok too.
Having Polymorph as an external (mergable, not loadable) package has worked well for us, as much as it can be well.
Perhaps changesets are the way to go from here... opinions/advice welcome...
Why MC is not good for you?
Regards, Gary _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
I'd recommend to incorporate all Polymorph's overrides into Morphic. Then you can still maintain Polymorph as separate package, but don't fool yourself with a tons of overrides. On 13 March 2010 19:15, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
On Mar 13, 2010, at 5:56 PM, Gary Chambers wrote:
All "fun" on squeak-dev...
Getting close to abandoning support for Polymorph in Squeak at all now... Only a few apps based on 3.9 left here. Not sure they need any of the ongoing improvements.
I'm not sure that maintaining two version is an option for you.
 So, the question is, how would we want future additions/changes/fixes to apply in Pharo.
The way you were doing them is ok. You could also publish directly in Pharo But if you want to have you own package and control over it this is ok too.
Having Polymorph as an external (mergable, not loadable) package has worked well for us, as much as it can be well.
Perhaps changesets are the way to go from here... opinions/advice welcome...
Why MC is not good for you?
Regards, Gary _______________________________________________ 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
-- Best regards, Igor Stasenko AKA sig.
It inevitable that there will be more necessary overrides... not even close to getting Morphic totally hooked for all that will be needed... Regards, Gary On Sat, 2010-03-13 at 23:29 +0200, Igor Stasenko wrote:
I'd recommend to incorporate all Polymorph's overrides into Morphic. Then you can still maintain Polymorph as separate package, but don't fool yourself with a tons of overrides.
On 13 March 2010 19:15, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
On Mar 13, 2010, at 5:56 PM, Gary Chambers wrote:
All "fun" on squeak-dev...
Getting close to abandoning support for Polymorph in Squeak at all now... Only a few apps based on 3.9 left here. Not sure they need any of the ongoing improvements.
I'm not sure that maintaining two version is an option for you.
So, the question is, how would we want future additions/changes/fixes to apply in Pharo.
The way you were doing them is ok. You could also publish directly in Pharo But if you want to have you own package and control over it this is ok too.
Having Polymorph as an external (mergable, not loadable) package has worked well for us, as much as it can be well.
Perhaps changesets are the way to go from here... opinions/advice welcome...
Why MC is not good for you?
Regards, Gary _______________________________________________ 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
-- Best regards, Igor Stasenko AKA sig.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
+1 On Mar 13, 2010, at 10:29 PM, Igor Stasenko wrote:
I'd recommend to incorporate all Polymorph's overrides into Morphic. Then you can still maintain Polymorph as separate package, but don't fool yourself with a tons of overrides.
On 13 March 2010 19:15, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
On Mar 13, 2010, at 5:56 PM, Gary Chambers wrote:
All "fun" on squeak-dev...
Getting close to abandoning support for Polymorph in Squeak at all now... Only a few apps based on 3.9 left here. Not sure they need any of the ongoing improvements.
I'm not sure that maintaining two version is an option for you.
So, the question is, how would we want future additions/changes/fixes to apply in Pharo.
The way you were doing them is ok. You could also publish directly in Pharo But if you want to have you own package and control over it this is ok too.
Having Polymorph as an external (mergable, not loadable) package has worked well for us, as much as it can be well.
Perhaps changesets are the way to go from here... opinions/advice welcome...
Why MC is not good for you?
Regards, Gary _______________________________________________ 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
-- Best regards, Igor Stasenko AKA sig.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
El sáb, 13-03-2010 a las 16:56 +0000, Gary Chambers escribió:
All "fun" on squeak-dev...
Getting close to abandoning support for Polymorph in Squeak at all now... Only a few apps based on 3.9 left here. Not sure they need any of the ongoing improvements.
It is your time and effort what you'll donate. So is up to you if you want to maintain two versions. I think that nobody will have arguments for complain if you decide not to maintain but the Pharo version.
So, the question is, how would we want future additions/changes/fixes to apply in Pharo. Having Polymorph as an external (mergable, not loadable) package has worked well for us, as much as it can be well.
I think that if it is possible to have a external, squeaksource repository hosted, monticello (and later a ConfigurationOfPolymorph) that would be the best. Because: - If someday someone wants to add support for Squeak (supposing that there is only Pharo support) they have the packages to work on. - If they are in an external repository, they can add per-platform packages to handle the differences between squeak/pharo/cuis - Metacello can load the different packages depending on the platform without problems - What we want is a smaller image every day. If the package is loadable (with Metacello for example) a script to build the image from a minimal, non-ui image is possible
Perhaps changesets are the way to go from here... opinions/advice welcome...
Unless that there is something that monticello (and pre and post scripts from monticello) can't handle, I will avoid changesets. Also, if you use changesets, where they will be hosted, not in the list please, that is a nightmare for the people searching for a given .cs. Keep the good work. Cheers
Regards, Gary
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Miguel Cobá http://miguel.leugim.com.mx
participants (4)
-
Gary Chambers -
Igor Stasenko -
Miguel Enrique Cobá Martinez -
Stéphane Ducasse