[Q] Any documentation of guide for porting seaside to other Smalltalk system?

> Sungjin,
>
> I don't know of any porting documentation, but here is a rough outline
> of how to go about doing the port:
>
>
>
> 1.    As Luka suggests, take a look at the Continuation class and get
> the unit tests to run in GNU smalltalk. Getting Contuations working may
> or may not be a big challenge. At Gemstone, we ended up making mods to
> the vm to get continuations to work.
> 2.    Once you've got continuations in hand, take a look at
> PackageInfo-Exporters. There's a version on SqueakSource (part of
> Seaside project) that is a good starting point. Write a GNU smalltalk
> exporter that will allow you to file out the Seaside package (all
> classes and extension methods for Seaside) in a form acceptable to GNU
> smalltalk.
>
> 3.    File the result into your GNU smalltalk image and resolve the
> filein issues.
> 4.    Run the Seaside unit tests.
> 5.    Now you'll need some sort of HTTP server. We are using
> Swazoo/Hyper. You'll need to write some glue code between Seaside and
> your HTTP server. We used Michel Bany's VW glue code as an example. We
> can provide our code as well. Basically the glue code transforms the
> requests and responses from your HTTP server into Seaside requests and
> responses.
>
> 6.    If GNU smalltalk doesn't have a HTTP server , you might try
> porting the FastCGI code from Squeak to GNU smalltalk. We just recently
> ported FastCGI to Gemstone so we can give you some pointers here. If you
> don't have a HTTP server in GNU smalltalk this is a very good option -
> you simply transform the FastCGI request/responses directly into Seaside
> request/responses.
> 7.    At this point you should be able to begin serving seaside web
> pages. Bring up the WAAllTests application (you'll need to initiale it
> first) and start poking around.
>
> This should be enough to get you started. Good luck!
>
> Dale
>
> Sungjin Chun wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
>
> Hash: SHA1
>
>
>
> Hi,
>
>
>
> I want to port seaside to GNU smalltalk - I'm not sure whether this is
>
> possible or not. My primary objective is to learn network programming in
>
> smalltak, both squeak and gnu smalltalk(gst).
>
>
>
> Is there any guide/documentation for this?
>
>
>
> Thanks in advance.
>
> -----BEGIN PGP SIGNATURE-----
>
> Version: GnuPG v1.4.2.2 (GNU/Linux)
>
> Comment: Using GnuPG with Mozilla -  http://enigmail.mozdev.org
> <http://enigmail.mozdev.org>
>
>
> iD8DBQFF6pZmQqspS1+XJHgRAsG/AJ0YQhUSo9Rx9CByyquY0VSompKJBwCg2G8w
>
> rufsXec1IRGkdorAHxFntHo=
>
> =PJe4
>
> -----END PGP SIGNATURE-----
>
> _______________________________________________
>
> Seaside mailing list
>
> [hidden email]
> <mailto:[hidden email]>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> <http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside>
>
>
>  
>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Seaside mailing list
>[hidden email]
>http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>  
>

> Sungjin,
>
> I don't know of any porting documentation, but here is a rough outline
> of how to go about doing the port:
>
>    1. As Luka suggests, take a look at the Continuation class and get
>       the unit tests to run in GNU smalltalk. Getting Contuations
>       working may or may not be a big challenge. At Gemstone, we ended
>       up making mods to the vm to get continuations to work.
>    2. Once you've got continuations in hand, take a look at
>       PackageInfo-Exporters. There's a version on SqueakSource (part of
>       Seaside project) that is a good starting point. Write a GNU
>       smalltalk exporter that will allow you to file out the Seaside
>       package (all classes and extension methods for Seaside) in a form
>       acceptable to GNU smalltalk.
>    3. File the result into your GNU smalltalk image and resolve the
>       filein issues.
>    4. Run the Seaside unit tests.
>    5. Now you'll need some sort of HTTP server. We are using
>       Swazoo/Hyper. You'll need to write some glue code between Seaside
>       and your HTTP server. We used Michel Bany's VW glue code as an
>       example. We can provide our code as well. Basically the glue code
>       transforms the requests and responses from your HTTP server into
>       Seaside requests and responses.
>    6. If GNU smalltalk doesn't have a HTTP server , you might try
>       porting the FastCGI code from Squeak to GNU smalltalk. We just
>       recently ported FastCGI to Gemstone so we can give you some
>       pointers here. If you don't have a HTTP server in GNU smalltalk
>       this is a very good option - you simply transform the FastCGI
>       request/responses directly into Seaside request/responses.
>    7. At this point you should be able to begin serving seaside web
>       pages. Bring up the WAAllTests application (you'll need to
>       initiale it first) and start poking around.
>
> This should be enough to get you started. Good luck!
>
> Dale
>
> Sungjin Chun wrote:
> Hi,
>
> I want to port seaside to GNU smalltalk - I'm not sure whether this is
> possible or not. My primary objective is to learn network programming in
> smalltak, both squeak and gnu smalltalk(gst).
>
> Is there any guide/documentation for this?
>
> Thanks in advance.