On Fri, Oct 8, 2010 at 6:38 AM, Torsten Bergmann <[email protected]> wrote:
> Hi Dale, > > again I typically use my MetaSource application to > see if one can bootstrap a full seaside app in Pharo using > Metacello: > > -------------------------------------------------------------------------- > Gofer new > squeaksource: 'MetaSource'; > package: 'ConfigurationOfMetaSource'; > load. > > ((Smalltalk at: #ConfigurationOfMetaSource) project version: '1.4') load > -------------------------------------------------------------------------- > > Works well in "Pharo 1.1." but not in "PharoCore 1.2": > > In Pharo 1.2 some methods are deprecated and Seaside 3.0 still > uses ConfigurationOfKomHttpServer 1.3 instead of the newer 1.5. > As far as I know (and as I can see in the repo), the new KomHttpServer versions are just bugfixes and the deprecation issue you'r talking about :). It seems no dangerous. > > So the question is: is it planned to use the newer KomHttpServer > packages in the near future for Seaside 3.0 so I can switch to > Pharo 1.2 early? Or is this planned when Pharo 1.2 is mature and > released. > Thx > Torsten > > > -- > GMX DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt auch mit > gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
