The main draw to SqueakDBX was the support for a wide variety of databases, whereas Seaside only seems to support a database called SandstoneDB which does not allow concurrent access, it looks like. In particular, I was looking into using PostgreSQL for the database.
I also didn't see anything mentioning if various aspects of Seaside could be used for non-web-oriented applications.
Getting started in learning Squeak, I also noticed that the main way to share programs involves sending a code file in some form or another. Is there any way to set a program to not be open-source?
On Mon, 7 Nov 2011, Matt Chelen wrote:
The main draw to SqueakDBX was the support for a wide variety of databases, whereas Seaside only seems to support a database called SandstoneDB which
Seaside can be used with any kind of persistence solution. SandstoneDB was written for Seaside and not the other way.
does not allow concurrent access, it looks like. In particular, I was looking into using PostgreSQL for the database.
We're using the native PostgresSQL libraries (both V2 and V3) with Seaside. Never tried SqueakDBX for real, but AFAIK it still uses FFI (which is still single threaded in most cases).
I also didn't see anything mentioning if various aspects of Seaside could be used for non-web-oriented applications.
Seaside is for web developement only.
Getting started in learning Squeak, I also noticed that the main way to share programs involves sending a code file in some form or another. Is there any way to set a program to not be open-source?
You don't have to share the source code at all, but with any other language which uses bytecodes (java, c#, actionscript, etc), decompilation is possible.
Levente
-- Matt
beginners@lists.squeakfoundation.org