Guiding the Albatross to the VW-Seaside? [was: [Seaside]Seasidefor VisualWorks]

[Philippe Marschall]

The request/response loop has been rewritten to not rely on Kom
anymore but only on Seaside. It's now at the point where you can file
it out, file it into VW, chance the reference to ExternalWebBrowser
and see what happens.

Cheers
Philippe

2008/6/24 Rick Flower <rickf at ca-flower.com>:
> I was searching my old emails for Albatross references w/ regards to VW
> and found this as the only thread.. Any ideas on where things stand at
> this point?  I didn't see any references to Albatross in the public store
> so I'll assume its still a no-go -- correct?  I'd love to see Albatross
> going on this platform.. Anyway, just figured it wouldn't hurt to ask..
>
>
> On Wed, June 20, 2007 11:51 pm, Michael Lucas-Smith wrote:
>> Our initial efforts will be in making sure the port is solid so that we
>> don't end up focusing on hundreds of microfires trying to support it.
>> Michel Bany has done an excellent job of this so far so the initial
>> effort should hopefully be low.
>>
>> Improvements there-in come in two forms: New libraries that use Seaside
>> of the ilk of ShoreComponents, where it's on top of Seaside and doesn't
>> change seaside. The other form being improvements to Seaside itself. The
>> latter we intend to avoid in principle to keep compatibility with what
>> Seaside is. I'm sure enhancements will trickle back and forth.
>>
>> And as to the burning question of are the Cincom guys going to use
>> Squeak instead of VisualWorks? funny question, kind of loaded. Obviously
>> we'll be using both.
>>
>> Cheers,
>> Michael
>>
>> Boris Popov wrote:
>>>
>>> I would hope so seeing as that's where majority of development is
>>> happening right now and cincom focus will first be on better
>>> integration and only then on seaside itself if I understand correctly.
>>>
>>> Cheers!
>>>
>>> -Boris
>>> (Sent from a BlackBerry)
>>>
>>> ----- Original Message -----
>>> From: seaside-bounces at lists.squeakfoundation.org
>>> <seaside-bounces at lists.squeakfoundation.org>
>>> To: Seaside - general discussion <seaside at lists.squeakfoundation.org>
>>> Sent: Wed Jun 20 22:37:01 2007
>>> Subject: Re: Guiding the Albatross to the VW-Seaside? [was:
>>> [Seaside]Seasidefor VisualWorks]
>>>
>>> So the current development model with development happening in Squeak
>>> and versions for other dialects being "generated" from there will
>>> stay?
>>>
>>> Philippe
>>>
>>> 2007/6/21, Michael Lucas-Smith <mlucas-smith at cincom.com>:
>>> > Yes, that's very high on the list of laws for this project. We're not
>>> > forking Seaside.
>>> >
>>> > Michael
>>> >
>>> > Ron Teitelbaum wrote:
>>> > > Hi Michael,
>>> > >
>>> > > I'd like to see Cincom maintain squeak compatibility.
>>> > >
>>> > > Ron Teitelbaum
>>> > >
>>> > >
>>> > >> -----Original Message-----
>>> > >> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
>>> > >> bounces at lists.squeakfoundation.org] On Behalf Of Michael
>>> Lucas-Smith
>>> > >> Sent: Wednesday, June 20, 2007 5:15 PM
>>> > >> To: Seaside - general discussion
>>> > >> Subject: Re: Guiding the Albatross to the VW-Seaside? [was:
>>> [Seaside]
>>> > >> Seasidefor VisualWorks]
>>> > >>
>>> > >>
>>> > >>
>>> > >>> Some UI testing tool like Watir (Ruby, see [1][2]) or Albatross
>>> (Squeak,
>>> > >>> see [3][4])on VW would be nice.
>>> > >>> I am aware of the Seaside Testing Tool from David Shaffer[5], but
>>> a
>>> > >>> framework capable of replaying JS scripts and showing the stuff
>>> > >>>
>>> > >> happening
>>> > >>
>>> > >>> in some browser would be nice - both for the test driven
>>> developers and
>>> > >>> their customers.
>>> > >>>
>>> > >>> Maybe guiding the Albatross to the VW-Seaside would be an option?
>>> > >>>
>>> > >>>
>>> > >> This is nice. When we did web testing before I moved to Cincom we
>>> > >> utilised the known properties of the server side code instead of
>>> > >> bouncing back to the web browser itself. Mostly because of:
>>> > >> a) Speed of running the tests
>>> > >> b) Ease of writing the tests
>>> > >>
>>> > >> In the end we wanted to do testing like this - so I whole heartedly
>>> > >> support this idea. It's going on to the project backlog. Thanks for
>>> > >> bringing it to my attention.
>>> > >>
>>> > >> Cheers,
>>> > >> Michael
>>> > >>
>>> > >> _______________________________________________
>>> > >> 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
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> 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
>