Squeak / Gemstone / VisualWorks with Seaside
Locked
 
|
VW appears to be quite polished and robust for development work ... Is any
developing a Seaside app with VW to deploy on Squeak or Gemstone/S? How easy is it to keep from getting tied up in platform-specifics, and how hard to port? Does it even make sense to consider this path? Thanks _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: Squeak / Gemstone / VisualWorks with Seaside
|
|
Hi, it should be a straight forward process if you do not use anything
specific to VW that doesn't exist in deployment environment.
Also, you'll need to file-out your code so that you can imported into
the deployment platform. I forget the exact package name that's
used for the package but I'll post later if no one posts that
information. Lastly, there may be other tid-bits in this regard
but those are the two that comes to mind.
Good luck, -Conrad On 10/22/07, itsme213 <[hidden email]> wrote: VW appears to be quite polished and robust for development work ... Is any _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by Sophie424
For GemStone/S we are focussed on making life easy for folks developing
their application in Squeak and deploying in GemStone/S. We support Monticello and our development tools are based on the OmniBrowser tool set, in fact it is possible to edit code in the GemStone repository using a Squeak image and the tools we provide ... Going from VW to GemStone is not something that we have focussed on ... VW does not support Monticello and we (and Squeak) do not support Store - passing .st files (or the equivalent) around is not really acceptable for ongoing development...managing your code on the target platform and getting your changes back into VW becomes problematic if you use fileins... I esperienced that when I began porting Seaside from Squeak to GemStone and that experience lead to porting Monticello to GemStone.... We have a GBS product that makes it somewhat easier to move code between VW and GemStone but GBS support is not included in the Free version... I'm not aware of a slam-dunk solution for developing in VW and deploying to Squeak or GemStone. Porting Monticello to VW would be a start, but I assume that there are some issues with name spaces that would have to be dealt with. Dale itsme213 wrote: >VW appears to be quite polished and robust for development work ... Is any >developing a Seaside app with VW to deploy on Squeak or Gemstone/S? How easy >is it to keep from getting tied up in platform-specifics, and how hard to >port? Does it even make sense to consider this path? > >Thanks > > > >_______________________________________________ >seaside mailing list >[hidden email] >http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by Conrad Taylor
That's encouraging.
Please let me know if this reasoning is flawed ... If my eventual deployment will be on Gemstone/S (rather than Squeak), I will need to develop in a different environment than deployment anyway, so I might as well choose VW over Squeak. Also (and this may be a bit religious, not my intention ...) is VW a better development environment than Squeak (costs aside) ? Thanks. =================== "Conrad Taylor" <[hidden email]> wrote in message news:[hidden email]... Hi, it should be a straight forward process if you do not use anything specific to VW that doesn't exist in deployment environment. Also, you'll need to file-out your code so that you can imported into the deployment platform. I forget the exact package name that's used for the package but I'll post later if no one posts that information. Lastly, there may be other tid-bits in this regard but those are the two that comes to mind. Good luck, -Conrad On 10/22/07, itsme213 <[hidden email]> wrote: VW appears to be quite polished and robust for development work ... Is any developing a Seaside app with VW to deploy on Squeak or Gemstone/S? How easy is it to keep from getting tied up in platform-specifics, and how hard to port? Does it even make sense to consider this path? Thanks _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
If your eventual deployment environment is GemStone/S you _can_ choose
to develop entirely in GemStone ... the GemStone tool set _will_ be more limited than you can get in either Squeak or VW, especially in the beginning, but as time goes by I assume that we (and our users) will continue to improve the tools. At the moment, I think that I would prefer to develop in Squeak and deploy in GemStone because of the close coupling you get with Monticello. It is very reasonable to think that one would develop/test along in Squeak, deploy to GemStone (sandbox environment) and go through a develop/test cycle in GemStone, saving changes back to Squeak via Monticello. If it was easy to move code back and forth to VW, then I would let religion be my guide:) Seriously, though, I don't have enough experience using the current set of VW tools (I lived in VW during the late 80's to mid 90's, but the tools have changed a lot since then) to make that judgement call. Dale itsme213 wrote: >That's encouraging. > >Please let me know if this reasoning is flawed ... If my eventual deployment >will be on Gemstone/S (rather than Squeak), I will need to develop in a >different environment than deployment anyway, so I might as well choose VW >over Squeak. > >Also (and this may be a bit religious, not my intention ...) is VW a better >development environment than Squeak (costs aside) ? > >Thanks. > >=================== > >"Conrad Taylor" <[hidden email]> wrote in message >news:[hidden email]... >Hi, it should be a straight forward process if you do not use anything >specific to VW that doesn't exist in deployment environment. Also, you'll >need to file-out your code so that you can imported into the deployment >platform. I forget the exact package name that's used for the package but >I'll post later if no one posts that information. Lastly, there may be >other tid-bits in this regard but those are the two that comes to mind. > >Good luck, > >-Conrad > > >On 10/22/07, itsme213 <[hidden email]> wrote: >VW appears to be quite polished and robust for development work ... Is any >developing a Seaside app with VW to deploy on Squeak or Gemstone/S? How easy >is it to keep from getting tied up in platform-specifics, and how hard to >port? Does it even make sense to consider this path? > >Thanks > > > >_______________________________________________ >seaside mailing list >[hidden email] >http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > > > > >_______________________________________________ >seaside mailing list >[hidden email] >http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > >_______________________________________________ >seaside mailing list >[hidden email] >http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by Dale
Thank you, Dale, Conrad. I feel at least a little bit safer from a totally
uninformed decision :-) "Dale Henrichs" <[hidden email]> wrote in message news:[hidden email]... > For GemStone/S we are focussed on making life easy for folks developing > their application in Squeak and deploying in GemStone/S. We support > Monticello and our development tools are based on the OmniBrowser tool > set, in fact it is possible to edit code in the GemStone repository using > a Squeak image and the tools we provide ... > > Going from VW to GemStone is not something that we have focussed on ... VW > does not support Monticello and we (and Squeak) do not support Store - > passing .st files (or the equivalent) around is not really acceptable > for ongoing development...managing your code on the target platform and > getting your changes back into VW becomes problematic if you use > fileins... I esperienced that when I began porting Seaside from Squeak to > GemStone and that experience lead to porting Monticello to GemStone.... We > have a GBS product that makes it somewhat easier to move code between VW > and GemStone but GBS support is not included in the Free version... > > I'm not aware of a slam-dunk solution for developing in VW and deploying > to Squeak or GemStone. Porting Monticello to VW would be a start, but I > assume that there are some issues with name spaces that would have to be > dealt with. > > Dale > > itsme213 wrote: > >>VW appears to be quite polished and robust for development work ... Is any >>developing a Seaside app with VW to deploy on Squeak or Gemstone/S? How >>easy is it to keep from getting tied up in platform-specifics, and how >>hard to port? Does it even make sense to consider this path? >> >>Thanks >> >> >>_______________________________________________ >>seaside mailing list >>[hidden email] >>http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by Dale
What's the easiest way to use an image for an
anchor? Is there a simple way to include an image spec like so between the
start and end tags without subclassing or modifying what's there? I've
poked around but nothing jumped out at me.
<a blah blah><img
src="image.gif"></a>
-Carl Gundel
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: [2.6]Images and anchors
|
|
I’ve found some solutions for this. The first is for relative paths. And the second for an absolute path for the image: Html anchorWithUrl: ‘http://www.amazon.com’ do: [html image: ‘/cartoon.jpg’] Html anchorWithUrl: ‘http://www.amazon.com’ do: [html image: ‘<a href="http://www.foo.com/cartoon.jpg¹]">http://www.foo.com/cartoon.jpg’] To get the image to serve relative paths I use the slug of code at the beginning of the David Shaffer tutorial that allows me to put images in a folder called FileRoot. Anyway, that’s my solution. I’d be happy to told that there’s a better way by someone on this list. Chris What's the easiest way to use an image for an anchor? Is there a simple way to include an image spec like so between the start and end tags without subclassing or modifying what's there? I've poked around but nothing jumped out at me. _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by Carl Gundel
>What's the easiest way to use an image for an anchor? Is there a simple
>way to include an image >spec like so between the start and end tags >without subclassing or modifying what's there? I've >poked around but >nothing jumped out at me. > > <a blah blah><img src="image.gif"></a> Oh that wasn't so hard. Don't know why it took me so long: html anchor with: [ html html: '<img src=''', self imagePath, '''>' ] -Carl Gundel http://www.runbasic.com _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
> -----Original Message-----
> From: [hidden email] > [mailto:[hidden email]] On Behalf > Of Carl Gundel > Sent: Monday, October 22, 2007 6:54 PM > To: Seaside - general discussion > Subject: Re: [Seaside] [2.6]Images and anchors > > >What's the easiest way to use an image for an anchor? Is there a > >simple way to include an image >spec like so between the > start and end > >tags without subclassing or modifying what's there? I've > >poked around > >but nothing jumped out at me. > > > > <a blah blah><img src="image.gif"></a> > > Oh that wasn't so hard. Don't know why it took me so long: > > html anchor > with: [ html html: '<img src=''', self imagePath, '''>' ] > > -Carl Gundel > http://www.runbasic.com How about something simpler... html anchor url: 'bla'; with: [ html image src: 'bla' ] Ramon Leon http://onsmalltalk.com _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by Carl Gundel
Hi,
What imagePath is returning ? an URL or a standard local filename ? In the first case that's work but in the second it won't. You can not add a local filename in the source of your web page 'c:\...\picture.jpg' does not mean anything in a web page except if you are running on localhost. You can create a virtual site web with visualwave or better creata a WAFileLibrary and add your picture in it. After doing that you will be able to call your image using an URL Tell me if you want more details. 2007/10/23, Carl Gundel <[hidden email]>: >What's the easiest way to use an image for an anchor? Is there a simple Try something like this instead. html anchor with: [ html image url: 'myurl' ] hope this helps -Carl Gundel Sylvain _______________________________________________ _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by Ramon Leon-5
On Oct 23, 2007, at 7:53 AM, Ramon Leon wrote: > > How about something simpler... > > html anchor url: 'bla'; with: [ html image src: 'bla' ] > I even think the following was already available in 2.6. html anchor url: 'bla'; with: [ html image url: self imagePath ] _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
«
Return to Seaside General
|
1 view|%1 views
| Free forum by Nabble | Edit this page |