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...<br><br><div class="gmail_quote">On Fri, Aug 3, 2012 at 9:21 PM, Dale Henrichs <span dir="ltr"><<a href="mailto:dhenrich@vmware.com" target="_blank">dhenrich@vmware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Regarding the "step by step" bit - I think we'll have to work that out ...<br>
<br>
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.<br>
<br>
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) ...<br>
<br>
I look forward to working on these things though...<br>
<span class="HOEnZb"><font color="#888888"><br>
Dale<br>
</font></span><div class="im HOEnZb"><br>
----- Original Message -----<br>
| From: "Boris Popov, DeepCove Labs" <<a href="mailto:boris@deepcovelabs.com">boris@deepcovelabs.com</a>><br>
</div><div class="im HOEnZb">| To: "Seaside - general discussion" <<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a>><br>
</div><div class="im HOEnZb">| Sent: Friday, August 3, 2012 12:18:32 PM<br>
| Subject: [Seaside] RE: STIG {was: JSON REST in VisualWork Seaside)<br>
|<br>
</div><div class="HOEnZb"><div class="h5">| Dale,<br>
|<br>
| Do you know of anyone who actually use(s|d) STIG in VisualWorks to<br>
| exchange code with Pharo? I'd love to get my hands on a basic<br>
| step-by-step as it would be key in keeping VisualWorks relevant when<br>
| it comes to Seaside, Amber etcetera IMHO.<br>
|<br>
| -Boris<br>
|<br>
|<br>
| -----Original Message-----<br>
| From: <a href="mailto:seaside-bounces@lists.squeakfoundation.org">seaside-bounces@lists.squeakfoundation.org</a><br>
| [mailto:<a href="mailto:seaside-bounces@lists.squeakfoundation.org">seaside-bounces@lists.squeakfoundation.org</a>] On Behalf Of<br>
| Dale Henrichs<br>
| Sent: Saturday, July 28, 2012 11:29 AM<br>
| To: Seaside - general discussion<br>
| Subject: Re: [Seaside] JSON REST in VisualWork Seaside<br>
|<br>
| Regarding porting code between VW and the Monticello family<br>
| (Squeak/Pharo/GemStone) you could try using a combination of STIG[1]<br>
| and FileTree[3]. STIG is a VW implementation of the Cypress package<br>
| format[2]. FileTree is a (Squeak/Pharo/GemStone) implementation of<br>
| the Cypress package format.<br>
|<br>
| Cypress writes packages to disk, so git/github can be used for<br>
| managing the shared source code. If you go this route you'll be able<br>
| to feedback bugfixes from the VW side and easily import new updates<br>
| to your VW implementation from the FileTree side ...<br>
|<br>
| It's probably easier to go this route...<br>
|<br>
| Dale<br>
|<br>
| [1] <a href="https://github.com/CampSmalltalk/STIG" target="_blank">https://github.com/CampSmalltalk/STIG</a><br>
| [2] <a href="https://github.com/CampSmalltalk/Cypress/blob/master/README.md" target="_blank">https://github.com/CampSmalltalk/Cypress/blob/master/README.md</a><br>
| [3] <a href="https://github.com/dalehenrich/filetree" target="_blank">https://github.com/dalehenrich/filetree</a><br>
| ----- Original Message -----<br>
| | From: "Philippe Marschall" <<a href="mailto:philippe.marschall@gmail.com">philippe.marschall@gmail.com</a>><br>
| | To: "Seaside - general discussion"<br>
| | <<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a>><br>
| | Sent: Friday, July 27, 2012 11:57:30 PM<br>
| | Subject: Re: [Seaside] JSON REST in VisualWork Seaside<br>
| |<br>
| | On Sat, Jul 28, 2012 at 2:07 AM, Roger Whitney<br>
| | <<a href="mailto:whitney@cs.sdsu.edu">whitney@cs.sdsu.edu</a>><br>
| | wrote:<br>
| | > I have an existing Seaside app using Seaside 3.0 in VisualWork<br>
| | > 7.x<br>
| | > (it works in VW7.7 through VW7.9). I want to add a REST component<br>
| | > to<br>
| | > return JSON. The Seaside-REST packages don't ship with VW. I did<br>
| | > find them on the cincom repository but they do not seem to work<br>
| | > (a<br>
| | > lot of exceptions). I also came across James Robertson's old<br>
| | > video<br>
| | > on RESTful services in Seaside but that approach also does not<br>
| | > seem<br>
| | > to work anymore (I get JSON in a web page).<br>
| | ><br>
| | > Does anyone have REST working in Seaside 3 in VisualWorks? Not<br>
| | > clear<br>
| | > if I am missing something simple?<br>
| | ><br>
| | > I can always use the VW WebToolKit to server my REST service, but<br>
| | > would like to know if it is possible in Seaside using VW.<br>
| |<br>
| | It should work in theory, I know it's working on GemStone an VAST.<br>
| | Firstly it uses pragmas but the Pharo/Squeak/GemStone/VAST pragma<br>
| | API<br>
| | is modelled after the VW pragma API. That should work in theory.<br>
| | The<br>
| | second thing it uses are method argument names. You'll need to<br>
| | write<br>
| | one class extension on the VisulalWorks (or Cincom Smalltalk)<br>
| | platform<br>
| | class for this.<br>
| |<br>
| | If you need to port it manually AFAIK there is a tool to directly<br>
| | load<br>
| | the MC package without filing out and in. It's probably best to ask<br>
| | on<br>
| | a Cincom mailing list like vwnc though.<br>
| |<br>
| | Cheers<br>
| | Philippe<br>
| | _______________________________________________<br>
| | seaside mailing list<br>
| | <a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
| | <a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
| |<br>
| _______________________________________________<br>
| seaside mailing list<br>
| <a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
| <a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
|<br>
| _______________________________________________<br>
| seaside mailing list<br>
| <a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
| <a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
|<br>
_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</div></div></blockquote></div><br>