[Seaside] Seaside Portability Between Different Vendors?

James Foster Smalltalk at JGFoster.net
Mon May 17 22:11:59 UTC 2010


http://code.google.com/p/seaside/wiki/CodingConventions contains a good list of ways of ensuring maximum portability. If you stick mostly to ANSI Smalltalk and don't use dialect-specific libraries, then even a complex application should be mostly portable. 

GemStone has a package to which Squeak/Pharo code is added to increase portability.


On May 17, 2010, at 2:24 PM, Paul B 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 ;) _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list