[Seaside] RE: STIG {was: JSON REST in VisualWork Seaside)

[Julian Fitzell]

The platform-specific packages are definitely a workaround and we'd be
better with branches if there was better support for them in the tools...

On Fri, Aug 3, 2012 at 9:21 PM, Dale Henrichs <dhenrich at vmware.com> wrote:

> Regarding the "step by step" bit - I think we'll have to work that out ...
>
> my current thinking is that the source for each platform should be managed
> on a separate branch, to make sharing code across multiple dialects easier
> ... I use this technique for FileTree and it has advantages and
> disadvantages so it's not quite a slam dunk.
>
> I'm not a big fan of the platform-specific packages, because the code
> cannot really be shared between dialects and it doesn't work for all cases
> (I end up branching the "common packages" for gemstone anyway) ...
>
> I look forward to working on these things though...
>
> Dale
>
> ----- Original Message -----
> | From: "Boris Popov, DeepCove Labs" <boris at deepcovelabs.com>
> | To: "Seaside - general discussion" <seaside at lists.squeakfoundation.org>
> | Sent: Friday, August 3, 2012 12:18:32 PM
> | Subject: [Seaside] RE: STIG {was: JSON REST in VisualWork Seaside)
> |
> | Dale,
> |
> | Do you know of anyone who actually use(s|d) STIG in VisualWorks to
> | exchange code with Pharo? I'd love to get my hands on a basic
> | step-by-step as it would be key in keeping VisualWorks relevant when
> | it comes to Seaside, Amber etcetera IMHO.
> |
> | -Boris
> |
> |
> | -----Original Message-----
> | From: seaside-bounces at lists.squeakfoundation.org
> | [mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of
> | Dale Henrichs
> | Sent: Saturday, July 28, 2012 11:29 AM
> | To: Seaside - general discussion
> | Subject: Re: [Seaside] JSON REST in VisualWork Seaside
> |
> | Regarding porting code between VW and the Monticello family
> | (Squeak/Pharo/GemStone) you could try using a combination of STIG[1]
> | and FileTree[3]. STIG is a VW implementation of the Cypress package
> | format[2]. FileTree is a (Squeak/Pharo/GemStone) implementation of
> | the Cypress package format.
> |
> | Cypress writes packages to disk, so git/github can be used for
> | managing the shared source code. If you go this route you'll be able
> | to feedback bugfixes from the VW side and easily import new updates
> | to your VW implementation from the FileTree side ...
> |
> | It's probably easier to go this route...
> |
> | Dale
> |
> | [1] https://github.com/CampSmalltalk/STIG
> | [2] https://github.com/CampSmalltalk/Cypress/blob/master/README.md
> | [3] https://github.com/dalehenrich/filetree
> | ----- Original Message -----
> | | From: "Philippe Marschall" <philippe.marschall at gmail.com>
> | | To: "Seaside - general discussion"
> | | <seaside at lists.squeakfoundation.org>
> | | Sent: Friday, July 27, 2012 11:57:30 PM
> | | Subject: Re: [Seaside] JSON REST in VisualWork Seaside
> | |
> | | On Sat, Jul 28, 2012 at 2:07 AM, Roger Whitney
> | | <whitney at cs.sdsu.edu>
> | | wrote:
> | | > I have an existing Seaside app using Seaside 3.0 in VisualWork
> | | > 7.x
> | | > (it works in VW7.7 through VW7.9). I want to add a REST component
> | | > to
> | | > return JSON. The Seaside-REST packages don't ship with VW. I did
> | | > find them on the cincom repository but they do not seem to work
> | | > (a
> | | > lot of exceptions). I also came across James Robertson's old
> | | > video
> | | > on RESTful services in Seaside but that approach also does not
> | | > seem
> | | > to work anymore (I get JSON in a web page).
> | | >
> | | > Does anyone have REST working in Seaside 3 in VisualWorks? Not
> | | > clear
> | | > if I am missing something simple?
> | | >
> | | > I can always use the VW WebToolKit to server my REST service, but
> | | > would like to know if it is possible in Seaside using VW.
> | |
> | | It should work in theory, I know it's working on GemStone an VAST.
> | | Firstly it uses pragmas but the Pharo/Squeak/GemStone/VAST pragma
> | | API
> | | is modelled after the VW pragma API. That should work in theory.
> | | The
> | | second thing it uses are method argument names. You'll need to
> | | write
> | | one class extension on the VisulalWorks (or Cincom Smalltalk)
> | | platform
> | | class for this.
> | |
> | | If you need to port it manually AFAIK there is a tool to directly
> | | load
> | | the MC package without filing out and in. It's probably best to ask
> | | on
> | | a Cincom mailing list like vwnc though.
> | |
> | | Cheers
> | | Philippe
> | | _______________________________________________
> | | seaside mailing list
> | | seaside at lists.squeakfoundation.org
> | | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> | |
> | _______________________________________________
> | seaside mailing list
> | seaside at lists.squeakfoundation.org
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> | _______________________________________________
> | seaside mailing list
> | seaside at lists.squeakfoundation.org
> | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> |
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20120804/d6e83d92/attachment-0001.htm