Polymorph
Locked
 
|
Given the integration of Polymorph with Pharo and
the distinct direction that Squeak is going I am going to have to mark
an end to Polymorph as an ongoing project, as such.
Further changes/additions/refactorings will now be
limited to Pharo and must be therefore done using the Slice system (will take a
while to get to grips with as time allows).
A final release of Polymorph will be made on
SqueakSource, as time allows soon. This will be the last (allegedly compatible)
version with Squeak, though I expect in its current state it is effectively not
loadable into recent Squeak images.
I'll try to get the time to make any changes via
Pharo slices though I still like the modularity of packaging systems. Can't have
both it seems. Polymorph is mature enough that, moving forward, most else can be
done as additions rather that overrides. Perhaps an "extras"
package?
Thanks to all who have been involved with Pharo and
helping us to move forward. Here's to the new baseline!
Shame the StrikeFonts don't do all that they
should... always a compromise of speed vs. functionality (c.f. translucent
text).
On a personal note, it would be nice to start to
leverage the possiblility of an open approach to visuals, host windows etc.
Valuable lessons have been learned and I think Pharo can provide a baseline for
moving forward to a more flexible and performant ui substrate. Happy to work
with you all to achieve that goal!
Regards, Gary _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
> On a personal note, it would be nice to start to leverage the
> possiblility of an open approach to visuals, host windows etc. > Valuable lessons have been learned and I think Pharo can provide a > baseline for moving forward to a more flexible and performant ui > substrate. Happy to work with you all to achieve that goal! Nice to hear this! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
In reply to this post by Gary Chambers-4
Gary
I feel honored by your trust (which is a ***really*** important value for me - mainly my own value). Now slices are only good when dealing with crosscutting changes. They help us finding the packages in the kind of random order of the inbox :) > Given the integration of Polymorph with Pharo and the distinct direction that Squeak is going I am going to have to mark an end to Polymorph as an ongoing project, as such. > > Further changes/additions/refactorings will now be limited to Pharo and must be therefore done using the Slice system (will take a while to get to grips with as time allows). What I would like is to have a deeper merge (not turning around morphic idiosyncrasies). For fun I wanted to check CUIS Morph since juan removed a lot of unnecessary code. > A final release of Polymorph will be made on SqueakSource, as time allows soon. This will be the last (allegedly compatible) version with Squeak, though I expect in its current state it is effectively not loadable into recent Squeak images. > > I'll try to get the time to make any changes via Pharo slices though I still like the modularity of packaging systems. Can't have both it seems. Polymorph is mature enough that, moving forward, most else can be done as additions rather that overrides. Cool. > Perhaps an "extras" package? > Thanks to all who have been involved with Pharo and helping us to move forward. Here's to the new baseline! > > Shame the StrikeFonts don't do all that they should... always a compromise of speed vs. functionality (c.f. translucent text). > > On a personal note, it would be nice to start to leverage the possiblility of an open approach to visuals, host windows etc. Valuable lessons have been learned and I think Pharo can provide a baseline for moving forward to a more flexible and performant ui substrate. Happy to work with you all to achieve that goal! Excellent! We really want to learn from your experience. I have rome also in my scanner. > Regards, Gary > _______________________________________________ > 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 |
|
|
In reply to this post by Gary Chambers-4
Thank you Steph... it will be a challenge to produce a framework to support all our needs but I believe we have, between us all, the expertise and motivation to make it so! ----- Original message ----- Gary I feel honored by your trust (which is a ***really*** important value for me - mainly my own value). Now slices are only good when dealing with crosscutting changes. They help us finding the packages in the kind of random order of the inbox :) > Given the integration of Polymorph with Pharo and the distinct direction that Squeak is going I am going to have to mark an end to Polymorph as an ongoing project, as such. > > Further changes/additions/refactorings will now be limited to Pharo and must be therefore done using the Slice system (will take a while to get to grips with as time allows). What I would like is to have a deeper merge (not turning around morphic idiosyncrasies). For fun I wanted to check CUIS Morph since juan removed a lot of unnecessary code. > A final release of Polymorph will be made on SqueakSource, as time allows soon. This will be the last (allegedly compatible) version with Squeak, though I expect in its current state it is effectively not loadable into recent Squeak images. > > I'll try to get the time to make any changes via Pharo slices though I still like the modularity of packaging systems. Can't have both it seems. Polymorph is mature enough that, moving forward, most else can be done as additions rather that overrides. Cool. > Perhaps an "extras" package? > Thanks to all who have been involved with Pharo and helping us to move forward. Here's to the new baseline! > > Shame the StrikeFonts don't do all that they should... always a compromise of speed vs. functionality (c.f. translucent text). > > On a personal note, it would be nice to start to leverage the possiblility of an open approach to visuals, host windows etc. Valuable lessons have been learned and I think Pharo can provide a baseline for moving forward to a more flexible and performant ui substrate. Happy to work with you all to achieve that goal! Excellent! We really want to learn from your experience. I have rome also in my scanner. > Regards, Gary > _______________________________________________ > Pharo-project mailing list > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list 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 |