[Seaside] Seaside Portability Between Different Vendors?
renggli at gmail.com
Tue May 18 12:17:34 UTC 2010
AFAIK more or less recent versions of Magritte and Pier are ported to
all platforms. After all, both frameworks build on the same
portability code as Seaside 3.
On Tuesday, May 18, 2010, Davorin Rusevljan <davorin.rusevljan at gmail.com> wrote:
> On Mon, May 17, 2010 at 11:24 PM, Paul B <papabravo3000 at gmail.com> wrote:
> If I wrote a moderately complex Seaside app.. let's say in Pharo.. could
> I move that app to Gemstone, or Cincom, or Dolphin etc. without making
> allot of changes?
> I was wondering if writing an app for one
> vendor image kind of locks you in to that image.
> What coding practices should one avoid if they want the option to
> change images in the future?
> (..so many good vendors out there ;)
> There are obvious differences in base classes between different dialects, but more importantly Seaside itself is supported in 2 basic levels. With and without continuations - and latter has much more restricted functionality. And Pier is also not ported to all Smalltalks that run Seaside, probably because it relies on Magritte, which is also not available on all platforms that have Seaside.
> So, if you like to remain platform independent, you would need to be very careful, and use only parts that are available everywhere.
More information about the seaside