headers
Julian Fitzell | 9 Nov 21:28

ANN: Seaside 2.9a1 release

After months of development, the Seaside Development Team is very
pleased to announce the release of Seaside 2.9 Alpha 1. We are
announcing this first release in stages: first to the developer
mailing list, then the main seaside list, and finally to the website.
We hope this will let us catch any major problems with this first
release as soon as possible.

Here's what we need to cover:

1. What's new
2. Things to be aware of
3. How to get it
4. When things go wrong (as they certainly will)
5. How-To's

===================
What's new
===================

The focus of this release has been on flexibility, portability, and
understandability.

Some highlights include:

 * Sub-packages. The code has been split up. This facilitates porting
because platform-specific code has been put into platform-specific
packages. It also means that you can load only the parts of Seaside
that you need. For example, when building your production image, you
can leave out tests, examples, and development tools.
(Continue reading)

Permalink | Reply |
headers
Sophie (itsme213 | 10 Nov 02:53
Favicon

Re: Seaside 2.9a1 release

Wonderful news !!

Congratulations, Lukas, Julian, Philippe, and all others on the team!

- Sophie

===========================

"Julian Fitzell" <jfitzell <at> gmail.com> wrote in message 
news:4a5dbd430811091231n4891f1e3pee2608d7c9eb4568 <at> mail.gmail.com...
> After months of development, the Seaside Development Team is very
> pleased to announce the release of Seaside 2.9 Alpha 1. We are
> announcing this first release in stages: first to the developer
> mailing list, then the main seaside list, and finally to the website.
> We hope this will let us catch any major problems with this first
> release as soon as possible.
>
> Here's what we need to cover:
>
> 1. What's new
> 2. Things to be aware of
> 3. How to get it
> 4. When things go wrong (as they certainly will)
> 5. How-To's
>
>
> ===================
> What's new
> ===================
> ......
(Continue reading)

Permalink | Reply |
headers
"Lautaro =?iso-8859-1?q?Fern=E1ndez=22?= | 11 Nov 15:37

Re: ANN: Seaside 2.9a1 release

Hi,

2008/11/9 Julian Fitzell <jfitzell <at> gmail.com>
[...]
A more complete list of change and new features can be found at
http://seaside.st/community/development/seaside29

That page (under Modularization) says the following:

[...] 
It allows for smaller Seaside installations. For example you can have Seaside without the tests or without Kom and use Swazoo 2 instead. 
[...]

This mean that just a few changes need to be made in order to get a working Swazoo-Seaside server?
Could you tell me a place to see a how-to use this modularity in order to make the port of Swazoo to work with Seaside?

Thanks in advance,
Lautaro Fernández

--
Luke LAut SkyFernadezWalker
_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Permalink | Reply |
headers
Philippe Marschall | 11 Nov 15:43

Re: ANN: Seaside 2.9a1 release

2008/11/11 Lautaro Fernández <evaklo <at> gmail.com>:
> Hi,
>
> 2008/11/9 Julian Fitzell <jfitzell <at> gmail.com>
>>
>> [...]
>> A more complete list of change and new features can be found at
>> http://seaside.st/community/development/seaside29
>
> That page (under Modularization) says the following:
>
>> [...]
>>
>> It allows for smaller Seaside installations. For example you can have
>> Seaside without the tests or without Kom and use Swazoo 2 instead.
>>
>> [...]
>
> This mean that just a few changes need to be made in order to get a working
> Swazoo-Seaside server?
> Could you tell me a place to see a how-to use this modularity in order to
> make the port of Swazoo to work with Seaside?

- don't load Kom, DynamicBindings, KomServices, Seaside-Adapters-Swazoo
- load SPort
- load Swazoo 2
- load Swazoo-Seaside form http://www.squeaksource.com/Seaside29LGPL
- load Seaside-Adaptors-Swazoo (from the mail repsitory)
- done

The whole thing is outlined here:
http://code.google.com/p/seaside/wiki/LoadOrder
With the very latest code, starting it is a bit different.

Cheers
Philippe

_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Permalink | Reply |
headers
Philippe Marschall | 15 Nov 15:36

Re: ANN: Seaside 2.9a1 release

2008/11/11, Lautaro Fernández <evaklo <at> gmail.com>:
> Hi,
>
> 2008/11/9 Julian Fitzell <jfitzell <at> gmail.com>
>
>> [...]
>> A more complete list of change and new features can be found at
>> http://seaside.st/community/development/seaside29
>>
>
> That page (under Modularization) says the following:
>
> [...]
>
> It allows for smaller Seaside installations. For example you can have
>> Seaside without the tests or without Kom and use Swazoo 2 instead.
>
> [...]
>>
>
> This mean that just a few changes need to be made in order to get a working
> Swazoo-Seaside server?

It means no changes need to be made. Swazoo 2.1 is supported out of
the box (well in theory at least, in practice it has only been tested
on Squeak).

> Could you tell me a place to see a how-to use this modularity in order to
> make the port of Swazoo to work with Seaside?

To get everything working in Squeak you need to:
- open an "empty" Squeak image doesn't have Seaside, Sport or Swazoo loaded
- drag and drop the attached file over the Squeak window
- select "fileIn entire file"
- if a debugger opens telling you that instance variables start with a
lower case letter hit proceed
- when everything is done evaluate
  WASwazooAdaptor startOn: 8080
- go to http://127.0.0.1:8080/seaside/tests/alltests

If you open the Monticello Browser from the world menu you'll see a
lot of Seaside-*, Javascript-*, Scriptaculous-*, RSS-* and JQuery-*
packages that make up Seaside. Everything that has no -Squeak- in the
package name should load directly into VW. Everything that has a
-Squeak- in the package name has to be reimplemented (only if you want
it of course). However most parts can probably be salvaged either from
the existing 2.8 port or the Squeak implementation.

Cincom supports Seaside so it's probably best to talk to them.

Cheers
Philippe

_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Permalink | Reply |
headers
Philippe Marschall | 15 Nov 15:36

Re: ANN: Seaside 2.9a1 release

2008/11/15, Philippe Marschall <philippe.marschall <at> gmail.com>:
> 2008/11/11, Lautaro Fernández <evaklo <at> gmail.com>:
>> Hi,
>>
>> 2008/11/9 Julian Fitzell <jfitzell <at> gmail.com>
>>
>>> [...]
>>> A more complete list of change and new features can be found at
>>> http://seaside.st/community/development/seaside29
>>>
>>
>> That page (under Modularization) says the following:
>>
>> [...]
>>
>> It allows for smaller Seaside installations. For example you can have
>>> Seaside without the tests or without Kom and use Swazoo 2 instead.
>>
>> [...]
>>>
>>
>> This mean that just a few changes need to be made in order to get a
>> working
>> Swazoo-Seaside server?
>
> It means no changes need to be made. Swazoo 2.1 is supported out of
> the box (well in theory at least, in practice it has only been tested
> on Squeak).
>
>> Could you tell me a place to see a how-to use this modularity in order to
>> make the port of Swazoo to work with Seaside?
>
> To get everything working in Squeak you need to:
> - open an "empty" Squeak image doesn't have Seaside, Sport or Swazoo loaded
> - drag and drop the attached file over the Squeak window
> - select "fileIn entire file"
> - if a debugger opens telling you that instance variables start with a
> lower case letter hit proceed
> - when everything is done evaluate
>   WASwazooAdaptor startOn: 8080
> - go to http://127.0.0.1:8080/seaside/tests/alltests
>
> If you open the Monticello Browser from the world menu you'll see a
> lot of Seaside-*, Javascript-*, Scriptaculous-*, RSS-* and JQuery-*
> packages that make up Seaside. Everything that has no -Squeak- in the
> package name should load directly into VW. Everything that has a
> -Squeak- in the package name has to be reimplemented (only if you want
> it of course). However most parts can probably be salvaged either from
> the existing 2.8 port or the Squeak implementation.
>
> Cincom supports Seaside so it's probably best to talk to them.

It would probably help if I actually attached the change set.

Cheers
Philippe
Attachment (seaside-2.9.0-alpha1.cs): application/octet-stream, 6132 bytes
_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Permalink | Reply |
headers
"Lautaro =?iso-8859-1?q?Fern=E1ndez=22?= | 17 Nov 15:05

Re: ANN: Seaside 2.9a1 release



2008/11/15 Philippe Marschall <philippe.marschall <at> gmail.com>
2008/11/11, Lautaro Fernández <evaklo <at> gmail.com>:
> Hi,
>
> 2008/11/9 Julian Fitzell <jfitzell <at> gmail.com>
>
>> [...]
>> A more complete list of change and new features can be found at
>> http://seaside.st/community/development/seaside29
>>
>
> That page (under Modularization) says the following:
>
> [...]
>
> It allows for smaller Seaside installations. For example you can have
>> Seaside without the tests or without Kom and use Swazoo 2 instead.
>
> [...]
>>
>
> This mean that just a few changes need to be made in order to get a working
> Swazoo-Seaside server?

It means no changes need to be made. Swazoo 2.1 is supported out of
the box (well in theory at least, in practice it has only been tested
on Squeak).

> Could you tell me a place to see a how-to use this modularity in order to
> make the port of Swazoo to work with Seaside?

To get everything working in Squeak you need to:
- open an "empty" Squeak image doesn't have Seaside, Sport or Swazoo loaded
- drag and drop the attached file over the Squeak window
- select "fileIn entire file"
- if a debugger opens telling you that instance variables start with a
lower case letter hit proceed
- when everything is done evaluate
 WASwazooAdaptor startOn: 8080
- go to http://127.0.0.1:8080/seaside/tests/alltests

All ran OK, except to save the image. The WASqueakPlatfrorm (class) does not understand the method "withName:withPriority:fork:", which is called from the CTPusher(classs)>>startUp. I commented that part and the where no more troubles anymore.



About the first seaside-2-9-0a1.cs that Julian had attached, I keep getting an error if I tried to load it on a fresh Squeak 3.9 image.
Internal Server Error
MessageNotUnderstood: WAKom>>dispatchRequest:

I'm loading it wrong? (this didn't happened to me on last Thursday)

 

If you open the Monticello Browser from the world menu you'll see a
lot of Seaside-*, Javascript-*, Scriptaculous-*, RSS-* and JQuery-*
packages that make up Seaside. Everything that has no -Squeak- in the
package name should load directly into VW. Everything that has a
-Squeak- in the package name has to be reimplemented (only if you want
it of course). However most parts can probably be salvaged either from
the existing 2.8 port or the Squeak implementation.

Good to know, thank =]
 
Cincom supports Seaside so it's probably best to talk to them.

The main problem is that they will port (or made it avaible) Seaside 2.9 for the next realise (which will be in US summer), but now we need to work with Swazoo instead of Opentalk-Http (which does not support streaming responses quite well).
But I'll try again to see if they can give me a workaround.

Thanks again Philippe.
Lautaro Fernández



Cheers
Philippe

_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside




--
Luke LAut SkyFernadezWalker
_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Permalink | Reply |
headers
Philippe Marschall | 18 Nov 07:48

Re: ANN: Seaside 2.9a1 release

2008/11/17, Lautaro Fernández <evaklo <at> gmail.com>:
> 2008/11/15 Philippe Marschall <philippe.marschall <at> gmail.com>
>
>> 2008/11/11, Lautaro Fernández <evaklo <at> gmail.com>:
>> > Hi,
>> >
>> > 2008/11/9 Julian Fitzell <jfitzell <at> gmail.com>
>> >
>> >> [...]
>> >> A more complete list of change and new features can be found at
>> >> http://seaside.st/community/development/seaside29
>> >>
>> >
>> > That page (under Modularization) says the following:
>> >
>> > [...]
>> >
>> > It allows for smaller Seaside installations. For example you can have
>> >> Seaside without the tests or without Kom and use Swazoo 2 instead.
>> >
>> > [...]
>> >>
>> >
>> > This mean that just a few changes need to be made in order to get a
>> working
>> > Swazoo-Seaside server?
>>
>> It means no changes need to be made. Swazoo 2.1 is supported out of
>> the box (well in theory at least, in practice it has only been tested
>> on Squeak).
>>
>> > Could you tell me a place to see a how-to use this modularity in order
>> > to
>> > make the port of Swazoo to work with Seaside?
>>
>> To get everything working in Squeak you need to:
>> - open an "empty" Squeak image doesn't have Seaside, Sport or Swazoo
>> loaded
>> - drag and drop the attached file over the Squeak window
>> - select "fileIn entire file"
>> - if a debugger opens telling you that instance variables start with a
>> lower case letter hit proceed
>> - when everything is done evaluate
>>  WASwazooAdaptor startOn: 8080
>> - go to http://127.0.0.1:8080/seaside/tests/alltests
>>
>
> All ran OK, except to save the image. The WASqueakPlatfrorm (class) does not
> understand the method "withName:withPriority:fork:", which is called from
> the CTPusher(classs)>>startUp. I commented that part and the where no more
> troubles anymore.

Right, I forgot to add Comet-Squeak-Core.

> About the first seaside-2-9-0a1.cs that Julian had attached, I keep getting
> an error if I tried to load it on a fresh Squeak 3.9 image.
> Internal Server Error
> MessageNotUnderstood: WAKom>>dispatchRequest:
>
> I'm loading it wrong? (this didn't happened to me on last Thursday)

Nope the script is wrong. It should load Seaside-Core-jf.320. It's
probably time to publish an alpha2 script.

>> If you open the Monticello Browser from the world menu you'll see a
>> lot of Seaside-*, Javascript-*, Scriptaculous-*, RSS-* and JQuery-*
>> packages that make up Seaside. Everything that has no -Squeak- in the
>> package name should load directly into VW. Everything that has a
>> -Squeak- in the package name has to be reimplemented (only if you want
>> it of course). However most parts can probably be salvaged either from
>> the existing 2.8 port or the Squeak implementation.
>
>
> Good to know, thank =]
>
>
>> Cincom supports Seaside so it's probably best to talk to them.
>
>
> The main problem is that they will port (or made it avaible) Seaside 2.9 for
> the next realise (which will be in US summer), but now we need to work with
> Swazoo instead of Opentalk-Http (which does not support streaming responses
> quite well).
> But I'll try again to see if they can give me a workaround.

Ok, let's to for another round. The attached change set contains the
very latest code from yesterday evening. It has seen only very little
testing. It loads almost everything including both Comanche and Swazoo
because we only implemented Comet on Comanche.

However the Seaside Control Panel now seems to work. You'll find it in
the world menu under tools.

Cheers
Philippe
Attachment (seaside-2.9.0-alpha1.cs): application/octet-stream, 8 KiB
_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Permalink | Reply |
headers
"Lautaro =?iso-8859-1?q?Fern=E1ndez=22?= | 18 Nov 13:29

Re: ANN: Seaside 2.9a1 release



2008/11/18 Philippe Marschall <philippe.marschall <at> gmail.com>
2008/11/17, Lautaro Fernández <evaklo <at> gmail.com>:
> 2008/11/15 Philippe Marschall <philippe.marschall <at> gmail.com>
>
>> 2008/11/11, Lautaro Fernández <evaklo <at> gmail.com>:
>> > Hi,
>> >
>> > 2008/11/9 Julian Fitzell <jfitzell <at> gmail.com>
>> >
>> >> [...]
>> >> A more complete list of change and new features can be found at
>> >> http://seaside.st/community/development/seaside29
>> >>
>> >
>> > That page (under Modularization) says the following:
>> >
>> > [...]
>> >
>> > It allows for smaller Seaside installations. For example you can have
>> >> Seaside without the tests or without Kom and use Swazoo 2 instead.
>> >
>> > [...]
>> >>
>> >
>> > This mean that just a few changes need to be made in order to get a
>> working
>> > Swazoo-Seaside server?
>>
>> It means no changes need to be made. Swazoo 2.1 is supported out of
>> the box (well in theory at least, in practice it has only been tested
>> on Squeak).
>>
>> > Could you tell me a place to see a how-to use this modularity in order
>> > to
>> > make the port of Swazoo to work with Seaside?
>>
>> To get everything working in Squeak you need to:
>> - open an "empty" Squeak image doesn't have Seaside, Sport or Swazoo
>> loaded
>> - drag and drop the attached file over the Squeak window
>> - select "fileIn entire file"
>> - if a debugger opens telling you that instance variables start with a
>> lower case letter hit proceed
>> - when everything is done evaluate
>>  WASwazooAdaptor startOn: 8080
>> - go to http://127.0.0.1:8080/seaside/tests/alltests
>>
>
> All ran OK, except to save the image. The WASqueakPlatfrorm (class) does not
> understand the method "withName:withPriority:fork:", which is called from
> the CTPusher(classs)>>startUp. I commented that part and the where no more
> troubles anymore.

Right, I forgot to add Comet-Squeak-Core.

> About the first seaside-2-9-0a1.cs that Julian had attached, I keep getting
> an error if I tried to load it on a fresh Squeak 3.9 image.
> Internal Server Error
> MessageNotUnderstood: WAKom>>dispatchRequest:
>
> I'm loading it wrong? (this didn't happened to me on last Thursday)

Nope the script is wrong. It should load Seaside-Core-jf.320. It's
probably time to publish an alpha2 script.

>> If you open the Monticello Browser from the world menu you'll see a
>> lot of Seaside-*, Javascript-*, Scriptaculous-*, RSS-* and JQuery-*
>> packages that make up Seaside. Everything that has no -Squeak- in the
>> package name should load directly into VW. Everything that has a
>> -Squeak- in the package name has to be reimplemented (only if you want
>> it of course). However most parts can probably be salvaged either from
>> the existing 2.8 port or the Squeak implementation.
>
>
> Good to know, thank =]
>
>
>> Cincom supports Seaside so it's probably best to talk to them.
>
>
> The main problem is that they will port (or made it avaible) Seaside 2.9 for
> the next realise (which will be in US summer), but now we need to work with
> Swazoo instead of Opentalk-Http (which does not support streaming responses
> quite well).
> But I'll try again to see if they can give me a workaround.

Ok, let's to for another round. The attached change set contains the
very latest code from yesterday evening. It has seen only very little
testing. It loads almost everything including both Comanche and Swazoo
because we only implemented Comet on Comanche.

However the Seaside Control Panel now seems to work. You'll find it in
the world menu under tools.
 
Thanks, but again I have no success, the script is inconsistent with their errors..
(first try)
when is loading at some point the script gave me the following error:
ZipArchive(Object)>> 'can't find EOCD position'

(second try)
the same as the first...
ZipArchive(Object)>> 'file is too short'

I tried both in Squeak and also Pharo.

Bye,
Lautaro Fernández


Cheers
Philippe

_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside




--
Luke LAut SkyFernadezWalker
_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Permalink | Reply |
headers
Cédrick Béler | 18 Nov 17:55

Re: ANN: Seaside 2.9a1 release

It works for me on Pharo0.1Core-10156.

>
> I tried both in Squeak and also Pharo.
>
>
--

-- 
Cédrick

_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Permalink | Reply |
headers
"Lautaro =?iso-8859-1?q?Fern=E1ndez=22?= | 19 Nov 04:02

Re: ANN: Seaside 2.9a1 release

2008/11/18 Cédrick Béler <cdrick65 <at> gmail.com>

It works for me on Pharo0.1Core-10156.

You are right, I've tried at work without success, but now in my home did ran very well.
Sorry for all the noise I've made.

Lautaro Fernández

 


>
> I tried both in Squeak and also Pharo.
>
>
--
Cédrick

_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside




--
Luke LAut SkyFernadezWalker
_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Permalink | Reply |
headers
Philippe Marschall | 18 Nov 21:31

Re: ANN: Seaside 2.9a1 release

2008/11/18, Lautaro Fernández <evaklo <at> gmail.com>:
> 2008/11/18 Philippe Marschall <philippe.marschall <at> gmail.com>
>
>> 2008/11/17, Lautaro Fernández <evaklo <at> gmail.com>:
>> > 2008/11/15 Philippe Marschall <philippe.marschall <at> gmail.com>
>> >
>> >> 2008/11/11, Lautaro Fernández <evaklo <at> gmail.com>:
>> >> > Hi,
>> >> >
>> >> > 2008/11/9 Julian Fitzell <jfitzell <at> gmail.com>
>> >> >
>> >> >> [...]
>> >> >> A more complete list of change and new features can be found at
>> >> >> http://seaside.st/community/development/seaside29
>> >> >>
>> >> >
>> >> > That page (under Modularization) says the following:
>> >> >
>> >> > [...]
>> >> >
>> >> > It allows for smaller Seaside installations. For example you can have
>> >> >> Seaside without the tests or without Kom and use Swazoo 2 instead.
>> >> >
>> >> > [...]
>> >> >>
>> >> >
>> >> > This mean that just a few changes need to be made in order to get a
>> >> working
>> >> > Swazoo-Seaside server?
>> >>
>> >> It means no changes need to be made. Swazoo 2.1 is supported out of
>> >> the box (well in theory at least, in practice it has only been tested
>> >> on Squeak).
>> >>
>> >> > Could you tell me a place to see a how-to use this modularity in
>> >> > order
>> >> > to
>> >> > make the port of Swazoo to work with Seaside?
>> >>
>> >> To get everything working in Squeak you need to:
>> >> - open an "empty" Squeak image doesn't have Seaside, Sport or Swazoo
>> >> loaded
>> >> - drag and drop the attached file over the Squeak window
>> >> - select "fileIn entire file"
>> >> - if a debugger opens telling you that instance variables start with a
>> >> lower case letter hit proceed
>> >> - when everything is done evaluate
>> >>  WASwazooAdaptor startOn: 8080
>> >> - go to http://127.0.0.1:8080/seaside/tests/alltests
>> >>
>> >
>> > All ran OK, except to save the image. The WASqueakPlatfrorm (class) does
>> not
>> > understand the method "withName:withPriority:fork:", which is called
>> > from
>> > the CTPusher(classs)>>startUp. I commented that part and the where no
>> more
>> > troubles anymore.
>>
>> Right, I forgot to add Comet-Squeak-Core.
>>
>> > About the first seaside-2-9-0a1.cs that Julian had attached, I keep
>> getting
>> > an error if I tried to load it on a fresh Squeak 3.9 image.
>> > Internal Server Error
>> > MessageNotUnderstood: WAKom>>dispatchRequest:
>> >
>> > I'm loading it wrong? (this didn't happened to me on last Thursday)
>>
>> Nope the script is wrong. It should load Seaside-Core-jf.320. It's
>> probably time to publish an alpha2 script.
>>
>> >> If you open the Monticello Browser from the world menu you'll see a
>> >> lot of Seaside-*, Javascript-*, Scriptaculous-*, RSS-* and JQuery-*
>> >> packages that make up Seaside. Everything that has no -Squeak- in the
>> >> package name should load directly into VW. Everything that has a
>> >> -Squeak- in the package name has to be reimplemented (only if you want
>> >> it of course). However most parts can probably be salvaged either from
>> >> the existing 2.8 port or the Squeak implementation.
>> >
>> >
>> > Good to know, thank =]
>> >
>> >
>> >> Cincom supports Seaside so it's probably best to talk to them.
>> >
>> >
>> > The main problem is that they will port (or made it avaible) Seaside 2.9
>> for
>> > the next realise (which will be in US summer), but now we need to work
>> with
>> > Swazoo instead of Opentalk-Http (which does not support streaming
>> responses
>> > quite well).
>> > But I'll try again to see if they can give me a workaround.
>>
>> Ok, let's to for another round. The attached change set contains the
>> very latest code from yesterday evening. It has seen only very little
>> testing. It loads almost everything including both Comanche and Swazoo
>> because we only implemented Comet on Comanche.
>>
>> However the Seaside Control Panel now seems to work. You'll find it in
>> the world menu under tools.
>
>
> Thanks, but again I have no success, the script is inconsistent with their
> errors..
> (first try)
> when is loading at some point the script gave me the following error:
> ZipArchive(Object)>> 'can't find EOCD position'
>
> (second try)
> the same as the first...
> ZipArchive(Object)>> 'file is too short'
>
> I tried both in Squeak and also Pharo.

That often happens when a file can't be downloaded. There should be a
folder named 'package-cache' in the directory of your image. Can you
delete it and try again.

If that fails again, can you:
- check if downloading
http://www.squeaksource.com/Seaside29/Seaside-Core-pmm.337.mcz works
- tell us what platform and VM you use

Cheers
Philippe

_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Permalink | Reply |
headers
Sophie (itsme213 | 13 Nov 04:05
Favicon

Re: Seaside 2.9a1 release

"Julian Fitzell" <jfitzell <at> gmail.com> wrote in message

> They will probably also work in Squeak 3.10 but this has not been tested.

On OSX:

- loads successfully into Damien's 3.9 dev image
- loads successfully into Damien's 3.10 dev image
- On either image, running the tests gives this walkback (not clear to me if 
it has to do with Seaside):

- Sophie
====================

VM: Mac OS - a SmalltalkImage
Image: Squeak3.10.2 [latest update: #7179]

WASqueakMimeDocumentTest class(Object)>>doesNotUnderstand: 
#allSelectorsBelow:
 Receiver: WASqueakMimeDocumentTest
 Arguments and temporary variables:
  aMessage:  allSelectorsBelow: TestCase
 Receiver's instance variables:
  superclass:  WAFormTestCase
  methodDict:  a MethodDictionary(#testAsMIMEDocumentForm->a CompiledMethod 
(953) ...etc...
  format:  132
  instanceVariables:  nil
  organization:  ('testing' testAsMIMEDocumentForm 
testAsMIMEDocumentFormColon tes...etc...
  subclasses:  nil
  name:  #WASqueakMimeDocumentTest
  classPool:  nil
  sharedPools:  nil
  environment:  a SystemDictionary(lots of globals)
  category:  #'Seaside-Tests-Squeak-Core'
  traitComposition:  nil
  localSelectors:  nil

WASqueakMimeDocumentTest class(TestCase class)>>withInheritedSelectors
 Receiver: WASqueakMimeDocumentTest
 Arguments and temporary variables:

 Receiver's instance variables:
  superclass:  WAFormTestCase
  methodDict:  a MethodDictionary(#testAsMIMEDocumentForm->a CompiledMethod 
(953) ...etc...
  format:  132
  instanceVariables:  nil
  organization:  ('testing' testAsMIMEDocumentForm 
testAsMIMEDocumentFormColon tes...etc...
  subclasses:  nil
  name:  #WASqueakMimeDocumentTest
  classPool:  nil
  sharedPools:  nil
  environment:  a SystemDictionary(lots of globals)
  category:  #'Seaside-Tests-Squeak-Core'
  traitComposition:  nil
  localSelectors:  nil

WASqueakMimeDocumentTest class(TestCase class)>>testsSelect:
 Receiver: WASqueakMimeDocumentTest
 Arguments and temporary variables:
  aBlock:  [] in WASqueakMimeDocumentTest class(TestCase 
class)>>suiteWithSelector...etc...
  selector:  nil
  s:  nil
 Receiver's instance variables:
  superclass:  WAFormTestCase
  methodDict:  a MethodDictionary(#testAsMIMEDocumentForm->a CompiledMethod 
(953) ...etc...
  format:  132
  instanceVariables:  nil
  organization:  ('testing' testAsMIMEDocumentForm 
testAsMIMEDocumentFormColon tes...etc...
  subclasses:  nil
  name:  #WASqueakMimeDocumentTest
  classPool:  nil
  sharedPools:  nil
  environment:  a SystemDictionary(lots of globals)
  category:  #'Seaside-Tests-Squeak-Core'
  traitComposition:  nil
  localSelectors:  nil

[] in WASqueakMimeDocumentTest class(TestCase 
class)>>suiteWithSelectorsMatching: {[:testClass | suite   addTests: 
(testClass     testsSelect: [:sel | pattern ...]}
 Arguments and temporary variables:
  pattern:  'test*'
  suite:  a TestSuite
  testClass:  WASqueakMimeDocumentTest
  sel:  nil

--- The full stack ---
WASqueakMimeDocumentTest class(Object)>>doesNotUnderstand: 
#allSelectorsBelow:
WASqueakMimeDocumentTest class(TestCase class)>>withInheritedSelectors
WASqueakMimeDocumentTest class(TestCase class)>>testsSelect:
[] in WASqueakMimeDocumentTest class(TestCase 
class)>>suiteWithSelectorsMatching: {[:testClass | suite   addTests: 
(testClass     testsSelect: [:sel | pattern ...]}
 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Array(SequenceableCollection)>>do:
[] in WASqueakMimeDocumentTest class(TestCase 
class)>>suiteWithSelectorsMatching: {[:suite | self theClasses   do: 
[:testClass | suite     addTests: (testClass...]}
TestSuite(Object)>>in:
TestSuite class>>define:
WASqueakMimeDocumentTest class(TestCase class)>>suiteWithSelectorsMatching:
WASqueakMimeDocumentTest class(TestCase class)>>allStandardTests
WASqueakMimeDocumentTest class(TestCase class)>>suite:
[] in TestSuite>>fromClasses:suites:select:reject: {[:suite | self addTests: 
(testClass suite: suite) tests]}
Set>>do:
[] in TestSuite>>fromClasses:suites:select:reject: {[:testClass |  suites 
do: [:suite | self addTests: (testClass suite: suite...]}
Set>>do:
TestSuite>>fromClasses:suites:select:reject:
TestSuite class>>classes:suites:select:reject:
TestRunner>>suiteAll
TestRunner>>runAll
PluggableButtonMorphPlus(PluggableButtonMorph)>>performAction
PluggableButtonMorphPlus>>performAction
[] in PluggableButtonMorphPlus(PluggableButtonMorph)>>mouseUp: {[:m | (m 
containsPoint: evt cursorPoint)   ifTrue: [m performAction]]}
Array(SequenceableCollection)>>do:
...etc...
Permalink | Reply |
headers
Keith Hodges | 13 Nov 11:49

Re: Re: Seaside 2.9a1 release

Sophie (itsme213) wrote:

Hello Sophie, it looks like you are using SUnit-improved which requires
#allSelectorsBellow: this is available in Kernel-Extensions or from mantis.

Installer mantis ensureFix: 7166.

If you let me know how you loaded SUnit-improved I will try and add this

Keith
Permalink | Reply |
headers
Sophie (itsme213 | 13 Nov 19:10
Favicon

Re: Re: Seaside 2.9a1 release

Hi Keith,

I was just using Damien's latest 3.9 and 3.10 dev images, using whatever 
test runner appears under the normal Open->... menu. Maybe those images are 
missing something?

Thanks - Sophie

"Keith Hodges" <keith_hodges <at> yahoo.co.uk> wrote in message 
news:491C062A.2070406 <at> yahoo.co.uk...
> Sophie (itsme213) wrote:
>
> Hello Sophie, it looks like you are using SUnit-improved which requires
> #allSelectorsBellow: this is available in Kernel-Extensions or from 
> mantis.
>
> Installer mantis ensureFix: 7166.
>
> If you let me know how you loaded SUnit-improved I will try and add this
>
>
> Keith
Permalink | Reply |
headers
Sophie (itsme213 | 13 Nov 21:31
Favicon

Re: Re: Seaside 2.9a1 release

"Keith Hodges" <keith_hodges <at> yahoo.co.uk> wrote in message

> Hello Sophie, it looks like you are using SUnit-improved which requires
> #allSelectorsBellow: this is available in Kernel-Extensions or from 
> mantis.
>
> Installer mantis ensureFix: 7166.

All Seaside tests run fine in 3.10 (after this SUnit fix).

Sophie
Permalink | Reply |
headers
Sophie (itsme213 | 14 Nov 02:51
Favicon

Re: Seaside 2.9a1 release


"Julian Fitzell" <jfitzell <at> gmail.com> wrote in message

> After months of development, the Seaside Development Team is very
> pleased to announce the release of Seaside 2.9 Alpha 1.

Should this release run the demos/tests after WAKom startOn: 8080?

When I browse to:
    localhost:8080/seaside/browse
I get:
Internal Server Error
MessageNotUnderstood: WAKom>>dispatchRequest:

Thanks - Sophie
Permalink | Reply |
headers
Julian Fitzell | 14 Nov 08:16

Re: Re: Seaside 2.9a1 release

On Thu, Nov 13, 2008 at 5:51 PM, Sophie (itsme213) <itsme213 <at> hotmail.com> wrote:
>
> "Julian Fitzell" <jfitzell <at> gmail.com> wrote in message
>
>> After months of development, the Seaside Development Team is very
>> pleased to announce the release of Seaside 2.9 Alpha 1.
>
> Should this release run the demos/tests after WAKom startOn: 8080?
>
> When I browse to:
>    localhost:8080/seaside/browse
> I get:
> Internal Server Error
> MessageNotUnderstood: WAKom>>dispatchRequest:

You just used the load script I posted? The tests definitely work in
every image I've loaded that into.  And I'm pretty sure the
#dispatchRequest: method was not even created until after we built
that load script.

My guess is you have updated some packages from the development
repository?. You'll need to pay pretty close attention to the
development mailing list and commit messages at the moment if you want
to follow the development repositories.

If this is not the case then make sure you are using one of the images
I provided links for in the announcement. Loading has been tested in
both of those images and the tests definitely work.

Julian
Permalink | Reply |
headers
Sophie (itsme213 | 14 Nov 15:01
Favicon

Re: Re: Seaside 2.9a1 release

"Julian Fitzell" <jfitzell <at> gmail.com> wrote in message

> You just used the load script I posted? The tests definitely work in
> every image I've loaded that into.  And I'm pretty sure the
> #dispatchRequest: method was not even created until after we built
> that load script.

Just used your load script with Damien's current 3.9 and 3.10 images, no 
updates from the development repository. #dispatchRequest: must have somehow 
come in with that script.

> If this is not the case then make sure you are using one of the images
> I provided links for in the announcement. Loading has been tested in
> both of those images and the tests definitely work.

I just tried it with your linked 3.9 image, same error from the browser.

Hth -- Sophie
Permalink | Reply |
headers
Sophie (itsme213 | 21 Nov 02:47
Favicon

Re: Seaside 2.9a1 release

"Julian Fitzell" <jfitzell <at> gmail.com> wrote in message

> We have tested the load scripts in the following images:
>
> * Squeak 3.9:
> * Pharo:

The load script runs fine and tests pass in these images. But I get
    MessageNotUnderstood: WAKom>>dispatchRequest:
when I browse localhost:8080/seaside. Tried on both the above images, on XP 
and on Mac.

Any ideas what I might be doing wrong? I am interested in digging into and 
helping a bit with jQuery.

Thanks!
Permalink | Reply |
headers
"Lautaro =?iso-8859-1?q?Fern=E1ndez=22?= | 21 Nov 12:57

Re: Re: Seaside 2.9a1 release

2008/11/20 Sophie (itsme213) <itsme213 <at> hotmail.com>

"Julian Fitzell" <jfitzell <at> gmail.com> wrote in message

> We have tested the load scripts in the following images:
>
> * Squeak 3.9:
> * Pharo:

The load script runs fine and tests pass in these images. But I get
   MessageNotUnderstood: WAKom>>dispatchRequest:
when I browse localhost:8080/seaside. Tried on both the above images, on XP and on Mac.

Any ideas what I might be doing wrong?

I'm attaching the same script that Philippe put in the following mail:
http://lists.squeakfoundation.org/pipermail/seaside/2008-November/019254.html

It has both servers, Comanche (Kom I think) and Swazoo.
Open a Workspace and do:
WAKom startOn: 8080 and you are ready to go.
or you could also do
WASwazooAdaptor startOn: 8888

Hope it helps.
Bye,
Lautaro
 
I am interested in digging into and helping a bit with jQuery.

Thanks!



_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside



--
Luke LAut SkyFernadezWalker
Attachment (seaside-2.9.0-alpha1.cs): application/octet-stream, 8 KiB
_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Permalink | Reply |
headers
Philippe Marschall | 21 Nov 13:30

Re: Re: Seaside 2.9a1 release

2008/11/21 Lautaro Fernández <evaklo <at> gmail.com>:
> 2008/11/20 Sophie (itsme213) <itsme213 <at> hotmail.com>
>>
>> "Julian Fitzell" <jfitzell <at> gmail.com> wrote in message
>>
>> > We have tested the load scripts in the following images:
>> >
>> > * Squeak 3.9:
>> > * Pharo:
>>
>> The load script runs fine and tests pass in these images. But I get
>>    MessageNotUnderstood: WAKom>>dispatchRequest:
>> when I browse localhost:8080/seaside. Tried on both the above images, on
>> XP and on Mac.
>>
>> Any ideas what I might be doing wrong?
>
> I'm attaching the same script that Philippe put in the following mail:
> http://lists.squeakfoundation.org/pipermail/seaside/2008-November/019254.html
>
> It has both servers, Comanche (Kom I think) and Swazoo.
> Open a Workspace and do:
> WAKom startOn: 8080 and you are ready to go.
> or you could also do
> WASwazooAdaptor startOn: 8888

Actually the server adaministration tool should work pretty well in
this version.

Cheers
Philippe

_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Permalink | Reply |
headers
"Lautaro =?iso-8859-1?q?Fern=E1ndez=22?= | 21 Nov 14:11

Re: Re: Seaside 2.9a1 release



2008/11/21 Philippe Marschall <philippe.marschall <at> gmail.com>
2008/11/21 Lautaro Fernández <evaklo <at> gmail.com>:
> 2008/11/20 Sophie (itsme213) <itsme213 <at> hotmail.com>
>>
>> "Julian Fitzell" <jfitzell <at> gmail.com> wrote in message
>>
>> > We have tested the load scripts in the following images:
>> >
>> > * Squeak 3.9:
>> > * Pharo:
>>
>> The load script runs fine and tests pass in these images. But I get
>>    MessageNotUnderstood: WAKom>>dispatchRequest:
>> when I browse localhost:8080/seaside. Tried on both the above images, on
>> XP and on Mac.
>>
>> Any ideas what I might be doing wrong?
>
> I'm attaching the same script that Philippe put in the following mail:
> http://lists.squeakfoundation.org/pipermail/seaside/2008-November/019254.html
>
> It has both servers, Comanche (Kom I think) and Swazoo.
> Open a Workspace and do:
> WAKom startOn: 8080 and you are ready to go.
> or you could also do
> WASwazooAdaptor startOn: 8888

Actually the server adaministration tool should work pretty well in
this version.

Cheers
Philippe

How can I enable the "server adaministration tool" ? Or show it up maybe.

Thanks,
Lautaro
--
Luke LAut SkyFernadezWalker
_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Permalink | Reply |
headers
Philippe Marschall | 21 Nov 14:46

Re: Re: Seaside 2.9a1 release

2008/11/21 Lautaro Fernández <evaklo <at> gmail.com>:
>
>
> 2008/11/21 Philippe Marschall <philippe.marschall <at> gmail.com>
>>
>> 2008/11/21 Lautaro Fernández <evaklo <at> gmail.com>:
>> > 2008/11/20 Sophie (itsme213) <itsme213 <at> hotmail.com>
>> >>
>> >> "Julian Fitzell" <jfitzell <at> gmail.com> wrote in message
>> >>
>> >> > We have tested the load scripts in the following images:
>> >> >
>> >> > * Squeak 3.9:
>> >> > * Pharo:
>> >>
>> >> The load script runs fine and tests pass in these images. But I get
>> >>    MessageNotUnderstood: WAKom>>dispatchRequest:
>> >> when I browse localhost:8080/seaside. Tried on both the above images,
>> >> on
>> >> XP and on Mac.
>> >>
>> >> Any ideas what I might be doing wrong?
>> >
>> > I'm attaching the same script that Philippe put in the following mail:
>> >
>> > http://lists.squeakfoundation.org/pipermail/seaside/2008-November/019254.html
>> >
>> > It has both servers, Comanche (Kom I think) and Swazoo.
>> > Open a Workspace and do:
>> > WAKom startOn: 8080 and you are ready to go.
>> > or you could also do
>> > WASwazooAdaptor startOn: 8888
>>
>> Actually the server adaministration tool should work pretty well in
>> this version.
>>
>> Cheers
>> Philippe
>
> How can I enable the "server adaministration tool" ? Or show it up maybe.

In the world menu under tools.

Cheers
Philippe

_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Permalink | Reply |
headers
"Lautaro =?iso-8859-1?q?Fern=E1ndez=22?= | 21 Nov 14:59

Re: Re: Seaside 2.9a1 release



2008/11/21 Philippe Marschall <philippe.marschall <at> gmail.com>
2008/11/21 Lautaro Fernández <evaklo <at> gmail.com>:
>
>
> 2008/11/21 Philippe Marschall <philippe.marschall <at> gmail.com>
>>
>> 2008/11/21 Lautaro Fernández <evaklo <at> gmail.com>:
>> > 2008/11/20 Sophie (itsme213) <itsme213 <at> hotmail.com>
>> >>
>> >> "Julian Fitzell" <jfitzell <at> gmail.com> wrote in message
>> >>
>> >> > We have tested the load scripts in the following images:
>> >> >
>> >> > * Squeak 3.9:
>> >> > * Pharo:
>> >>
>> >> The load script runs fine and tests pass in these images. But I get
>> >>    MessageNotUnderstood: WAKom>>dispatchRequest:
>> >> when I browse localhost:8080/seaside. Tried on both the above images,
>> >> on
>> >> XP and on Mac.
>> >>
>> >> Any ideas what I might be doing wrong?
>> >
>> > I'm attaching the same script that Philippe put in the following mail:
>> >
>> > http://lists.squeakfoundation.org/pipermail/seaside/2008-November/019254.html
>> >
>> > It has both servers, Comanche (Kom I think) and Swazoo.
>> > Open a Workspace and do:
>> > WAKom startOn: 8080 and you are ready to go.
>> > or you could also do
>> > WASwazooAdaptor startOn: 8888
>>
>> Actually the server adaministration tool should work pretty well in
>> this version.
>>
>> Cheers
>> Philippe
>
> How can I enable the "server adaministration tool" ? Or show it up maybe.

In the world menu under tools.

Cheers
Philippe

Thanks!
Lautaro
 


_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside




--
Luke LAut SkyFernadezWalker
_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Permalink | Reply |
headers
Philippe Marschall | 21 Nov 06:36

Re: Re: Seaside 2.9a1 release

2008/11/21 Sophie (itsme213) <itsme213 <at> hotmail.com>:
> "Julian Fitzell" <jfitzell <at> gmail.com> wrote in message
>
>> We have tested the load scripts in the following images:
>>
>> * Squeak 3.9:
>> * Pharo:
>
> The load script runs fine and tests pass in these images. But I get
>    MessageNotUnderstood: WAKom>>dispatchRequest:
> when I browse localhost:8080/seaside. Tried on both the above images, on XP
> and on Mac.
>
> Any ideas what I might be doing wrong? I am interested in digging into and
> helping a bit with jQuery.

The posted script is broken. See previous mails.

Cheers
Philippe
Permalink | Reply |

Gmane