[Pharo-project] Comments on Metacello and ConfigurationOfExternalWebBrowser
Come on!!! That's not an excuse
Yes it is - maybe there is already a better or fixed version in a private repo of dale or the tutorial is not maintained anymore since according to http://code.google.com/p/metacello/wiki/Tutorial there is a real tutorial in preparation. Who knows without asking...
#commonSqueak or something like that , which is for pharo and squeak (but not gemstone)
It's called "squeakCommon" and I have no idea if "gemstone" means the pharo based gemstone image or the server. Anything I see is that FFI config also uses #common and developers for it are Esteban, you and Dale. So you should know ;) However - what if Metacello gets ported. Do we have an "commercialSmalltalksCommon", "vastAndVW", ... or any other combination or do we have to maintain a spec for any each platform. Would'nt it be better to have a spec and tell on which (multiple) targets it is able to run. Questions over Questions ... Bye T. -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser
On Wed, Jan 13, 2010 at 5:11 PM, Torsten Bergmann wrote:
It's called "squeakCommon" and I have no idea if "gemstone" means the pharo based gemstone image or the server.
#gemstone refers to the server "platform", which has among other things a separate class library. The GemTools, or client, can be loaded into any Pharo or Squeak image and is not a platform on its own.
However - what if Metacello gets ported. Do we have an "commercialSmalltalksCommon", "vastAndVW", ... or any other combination or do we have to maintain a spec for any each platform.
Squeak and Pharo still shares enough of a common base that you can load in most things into any one of them without modification. Hence #squeakCommon. When Metacello gets ported, that question will be addressed :-) -- Danie Roux *shuffle* Adore Unix - http://danieroux.com
#commonSqueak or something like that , which is for pharo and squeak (but not gemstone)
It's called "squeakCommon" and I have no idea if "gemstone" means the pharo based gemstone image
Not, that's GemTools. Gemstone, is the Smalltalk gemstone.
or the server. Anything I see is that FFI config also uses #common and developers for it are Esteban, you and Dale.
I didn't do the FFI ;) In addition, if you see all the confs I announced I put everything in #pharo because I didn't test it in squeak. Actually, at the beginning, I put everything in #common but then Dale suggest me to put them in #pharo if I only tested there, and that's what I did. If them someone test it in squeak or gemstone, and works ok, then we can put it as common. But yes, everything that uses FFI, I think should be only in Squeak and Pharo as Gemstone does not support a "similar" FFI.
So you should know ;)
However - what if Metacello gets ported. Do we have an "commercialSmalltalksCommon", "vastAndVW", ... or any other combination or do we have to maintain a spec for any each platform.
Would'nt it be better to have a spec and tell on which (multiple) targets it is able to run.
+1 I totally agree. That solution doesn't scale. The ideal would be if for: can also an array, as load: do for example: You can do load: 'aGroup' or load: #('group1' 'group2' ) So, maybe would be cool to do: for: #('squeak' 'pharo' .... ) what do you think? Questions over Questions ...
Bye T.
-- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
El mié, 13-01-2010 a las 16:20 +0100, Mariano Martinez Peck escribió:
>#commonSqueak or something like that , which is for pharo and squeak (but >not gemstone)
It's called "squeakCommon" and I have no idea if "gemstone" means the pharo based gemstone image
Not, that's GemTools. Gemstone, is the Smalltalk gemstone.
or the server. Anything I see is that FFI config also uses #common and developers for it are Esteban, you and Dale.
I didn't do the FFI ;) In addition, if you see all the confs I announced I put everything in #pharo because I didn't test it in squeak. Actually, at the beginning, I put everything in #common but then Dale suggest me to put them in #pharo if I only tested there, and that's what I did. If them someone test it in squeak or gemstone, and works ok, then we can put it as common.
So if I only tested on Pharo I shouldn't use #common but #pharo and when someone makes it work on Squeak the will change it to #commonSqueak and when someone else verifies that works in every know platform he/she will have to change it to #common?
But yes, everything that uses FFI, I think should be only in Squeak and Pharo as Gemstone does not support a "similar" FFI.
So you should know ;)
However - what if Metacello gets ported. Do we have an "commercialSmalltalksCommon", "vastAndVW", ... or any other combination or do we have to maintain a spec for any each platform.
Would'nt it be better to have a spec and tell on which (multiple) targets it is able to run.
+1 I totally agree. That solution doesn't scale. The ideal would be if for: can also an array, as load: do for example:
You can do load: 'aGroup' or load: #('group1' 'group2' )
So, maybe would be cool to do:
for: #('squeak' 'pharo' .... )
what do you think?
Questions over Questions ...
Bye T.
-- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser
_______________________________________________ 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
-- Miguel Cobá http://miguel.leugim.com.mx
2010/1/13 Miguel Enrique Cobá Martinez <miguel.coba@gmail.com>
El mié, 13-01-2010 a las 16:20 +0100, Mariano Martinez Peck escribió:
>#commonSqueak or something like that , which is for pharo and squeak (but >not gemstone)
It's called "squeakCommon" and I have no idea if "gemstone" means the pharo based gemstone image
Not, that's GemTools. Gemstone, is the Smalltalk gemstone.
or the server. Anything I see is that FFI config also uses #common and developers for it are Esteban, you and Dale.
I didn't do the FFI ;) In addition, if you see all the confs I announced I put everything in #pharo because I didn't test it in squeak. Actually, at the beginning, I put everything in #common but then Dale suggest me to put them in #pharo if I only tested there, and that's what I did. If them someone test it in squeak or gemstone, and works ok, then we can put it as common.
So if I only tested on Pharo I shouldn't use #common but #pharo and when someone makes it work on Squeak the will change it to #commonSqueak and when someone else verifies that works in every know platform he/she will have to change it to #common?
At least that's what I understood. But maybe I am wrong. Let's hear the opinion of our god Dale :)
But yes, everything that uses FFI, I think should be only in Squeak and Pharo as Gemstone does not support a "similar" FFI.
So you should know ;)
However - what if Metacello gets ported. Do we have an "commercialSmalltalksCommon", "vastAndVW", ... or any other combination or do we have to maintain a spec for any each platform.
Would'nt it be better to have a spec and tell on which (multiple) targets it is able to run.
+1 I totally agree. That solution doesn't scale. The ideal would be if for: can also an array, as load: do for example:
You can do load: 'aGroup' or load: #('group1' 'group2' )
So, maybe would be cool to do:
for: #('squeak' 'pharo' .... )
what do you think?
Questions over Questions ...
Bye T.
-- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser
_______________________________________________ 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
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (4)
-
Danie Roux -
Mariano Martinez Peck -
Miguel Enrique Cobá Martinez -
Torsten Bergmann