[Pharo-project] Seaside and KomHttpServer in Pharo 1.2
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. 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
Torsten, What do you do to test your newly converted Seaside apps? Have you automated it, or is just a matter of trying everything yourself? Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Torsten Bergmann [astares@gmx.de] Sent: Friday, October 08, 2010 5:38 AM To: pharo-project@lists.gforge.inria.fr; dhenrich@vmware.com Subject: [Pharo-project] Seaside and KomHttpServer in Pharo 1.2 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. 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 Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Fri, Oct 8, 2010 at 6:38 AM, Torsten Bergmann <astares@gmx.de> 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 Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Hi Torsten, I have started on the update process for the Seaside configs. I got hung up for a day or two, since recent changes to Grease for Pharo1.1 compat broke Seaside3.0 on Pharo1.0... I will get back on the horse next week and finish up new revs for the Seaside configs Thanks for the gentle reminder:) Dale On 10/08/2010 02:38 AM, Torsten Bergmann 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.
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
participants (4)
-
Dale Henrichs -
Guillermo Polito -
Schwab,Wilhelm K -
Torsten Bergmann