Porting Seaside and Scriptaculous to VisualWorks

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Porting Seaside and Scriptaculous to VisualWorks

Boris Popov, DeepCove Labs (SNN)
Michel,

Would you mind providing instructions on porting Seaside and Scriptaculous
from Squeak to VisualWorks so I don't have to keep bugging you every time I
want to play with some of the newer stuff. Maybe we could share the
responsibility somewhat given that we'll be using Seaside quite extensively
on VisualWorks from here on out.

Cheers!

-Boris

--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

[hidden email]

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: Porting Seaside and Scriptaculous to VisualWorks

Bany, Michel
> Would you mind providing instructions on porting Seaside and
> Scriptaculous from Squeak to VisualWorks so I don't have to
> keep bugging you every time I want to play with some of the
> newer stuff. Maybe we could share the responsibility somewhat
> given that we'll be using Seaside quite extensively on
> VisualWorks from here on out.

Thanks for this offer !

You will need to set up a Squeak image and load the packages
from http://squeaksource.com/Seaside. You will also need to load
the package exporter from the same source.
The Seaside and Scriptaculous packages include a special class
that is used to drive the exporter, SeasideVWInfo resp.
ScriptaculousVWInfo. I recommend that you review these classes
carefully. That will tell you what portions are exported to VW
and what portions are not.

Then see the readme file in the "contributed\Seaside\Squeak\" area
of the VW distribution.
See also http://www.motionobj.com/seasidefaq/VisualworksSpecific
Porting is further documented in the code, see #portDocumentation
implementors.

Once you have exported the Squeak code, you can use the Seaside
port tool that is available as part of Seaside-VW, see class
SeasidePort and the classes in the SeasidePortStrategy hierarchy.

You can enable the Seaside port tool in the VW Tools menu by
altering #isSeasideDeveloper. You will also have to alter #squeakFolder.
The Seaside port tool is an initial attempt to automate things
as much as possible. Publishing automatically to my local store
works in most cases. I did not dare yet publishing to Cincom store
automatically. Pay careful attention to #portSource implementors and
use the port tool to alter them.

Feel free to contact me, should you need further assistance.
Michel.


_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside