Re: seaside Digest, Vol 71, Issue 26

> Send seaside mailing list submissions to
> [hidden email]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> or, via email, send a message with subject or body 'help' to
> [hidden email]
>
> You can reach the person managing the list at
> [hidden email]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of seaside digest..."
>
>
> Today's Topics:
>
>   1. Re: Seaside 2.9 & dynamic variable (G?ran Krampe)
>   2. Re: ANN: Seaside 2.9a1 release ( Lautaro Fern?ndez )
>   3. Re: Seaside 2.9 & dynamic variable (Julian Fitzell)
>   4. Re: Seaside 2.9 & dynamic variable (Karsten)
>   5. Re: Seaside 2.9 & dynamic variable (Julian Fitzell)
>   6. Re: ANN: Seaside 2.9a1 release (Philippe Marschall)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 17 Nov 2008 13:52:18 +0100
> From: G?ran Krampe <[hidden email]>
> Subject: Re: [Seaside] Seaside 2.9 & dynamic variable
> To: Seaside - general discussion <[hidden email]>
> Message-ID: <[hidden email]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hey!
>
> Just wanted to mention that someone said at OOPSLA (when I showed
> Blackfoot - my SimpleCGI implementation) that the Notification-trick
> actually shows up in performance profiling, so we might want to change
> to something else. Keith has made a package for "Process locals"  
> btw, we
> use it in Gjallar.
>
> regards, Göran
>
> PS. But Julian is of course still correct regarding debugger.
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 17 Nov 2008 11:05:53 -0300
> From: " Lautaro Fern?ndez " <[hidden email]>
> Subject: Re: [Seaside] ANN: Seaside 2.9a1 release
> To: "Seaside - general discussion"
> <[hidden email]>
> Message-ID:
> <[hidden email]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> 2008/11/15 Philippe Marschall <[hidden email]>
>
>> 2008/11/11, Lautaro Fernández <[hidden email]>:
>>> Hi,
>>>
>>> 2008/11/9 Julian Fitzell <[hidden email]>
>>>
>>>> [...]
>>>> 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
>> [hidden email]
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>>
>
>
> --
> Luke LAut SkyFernadezWalker
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20081117/2b9319da/attachment-0001.htm
>
> ------------------------------
>
> Message: 3
> Date: Mon, 17 Nov 2008 08:02:00 -0800
> From: "Julian Fitzell" <[hidden email]>
> Subject: Re: [Seaside] Seaside 2.9 & dynamic variable
> To: "Seaside - general discussion"
> <[hidden email]>
> Message-ID:
> <[hidden email]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi Göran,
>
> What do you mean the "notification trick"? Are you talking about 2.8
> or 2.9? In 2.9, an Error is only signaled when the process variable is
> accessed but not defined. This should only happen due to a
> misconfiguration or in the debugger. The exception handlers facilitate
> debugging by handling the error and resuming with the correct value.
>
> Julian
>
> On Mon, Nov 17, 2008 at 4:52 AM, Göran Krampe <[hidden email]> wrote:
>> Hey!
>>
>> Just wanted to mention that someone said at OOPSLA (when I showed  
>> Blackfoot
>> - my SimpleCGI implementation) that the Notification-trick actually  
>> shows up
>> in performance profiling, so we might want to change to something  
>> else.
>> Keith has made a package for "Process locals" btw, we use it in  
>> Gjallar.
>>
>> regards, Göran
>>
>> PS. But Julian is of course still correct regarding debugger.
>>
>> _______________________________________________
>> seaside mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 17 Nov 2008 17:11:11 +0100
> From: Karsten <[hidden email]>
> Subject: Re: [Seaside] Seaside 2.9 & dynamic variable
> To: Seaside - general discussion <[hidden email]>
> Message-ID: <[hidden email]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> I think he refers to the WADynamicVariable implementation as a
> Notification subclass.
>
> Kind Regards
> Karsten
>
>
>
> Julian Fitzell wrote:
>> Hi Göran,
>>
>> What do you mean the "notification trick"? Are you talking about 2.8
>> or 2.9? In 2.9, an Error is only signaled when the process variable  
>> is
>> accessed but not defined. This should only happen due to a
>> misconfiguration or in the debugger. The exception handlers  
>> facilitate
>> debugging by handling the error and resuming with the correct value.
>>
>> Julian
>>
>> On Mon, Nov 17, 2008 at 4:52 AM, Göran Krampe <[hidden email]>  
>> wrote:
>>
>>> Hey!
>>>
>>> Just wanted to mention that someone said at OOPSLA (when I showed  
>>> Blackfoot
>>> - my SimpleCGI implementation) that the Notification-trick  
>>> actually shows up
>>> in performance profiling, so we might want to change to something  
>>> else.
>>> Keith has made a package for "Process locals" btw, we use it in  
>>> Gjallar.
>>>
>>> regards, Göran
>>>
>>> PS. But Julian is of course still correct regarding debugger.
>>>
>>> _______________________________________________
>>> 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
>>
>>
>>
>
> --
> Karsten Kusche - Dipl.Inf. - [hidden email]
> Tel: +49 3496 21 43 29
> Georg Heeg eK - Köthen
> Handelsregister: Amtsgericht Dortmund A 12812
>
>
>
> ------------------------------
>
> Message: 5
> Date: Mon, 17 Nov 2008 21:34:06 -0800
> From: "Julian Fitzell" <[hidden email]>
> Subject: Re: [Seaside] Seaside 2.9 & dynamic variable
> To: "Seaside - general discussion"
> <[hidden email]>
> Message-ID:
> <[hidden email]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Ok, well in that case, that is no longer used in 2.9. As the original
> poster said, we are now using a process variable.
>
> Julian
>
> On Mon, Nov 17, 2008 at 8:11 AM, Karsten <[hidden email]> wrote:
>> I think he refers to the WADynamicVariable implementation as a  
>> Notification
>> subclass.
>>
>> Kind Regards
>> Karsten
>>
>>
>>
>> Julian Fitzell wrote:
>>>
>>> Hi Göran,
>>>
>>> What do you mean the "notification trick"? Are you talking about 2.8
>>> or 2.9? In 2.9, an Error is only signaled when the process  
>>> variable is
>>> accessed but not defined. This should only happen due to a
>>> misconfiguration or in the debugger. The exception handlers  
>>> facilitate
>>> debugging by handling the error and resuming with the correct value.
>>>
>>> Julian
>>>
>>> On Mon, Nov 17, 2008 at 4:52 AM, Göran Krampe <[hidden email]>  
>>> wrote:
>>>
>>>>
>>>> Hey!
>>>>
>>>> Just wanted to mention that someone said at OOPSLA (when I showed
>>>> Blackfoot
>>>> - my SimpleCGI implementation) that the Notification-trick  
>>>> actually shows
>>>> up
>>>> in performance profiling, so we might want to change to something  
>>>> else.
>>>> Keith has made a package for "Process locals" btw, we use it in  
>>>> Gjallar.
>>>>
>>>> regards, Göran
>>>>
>>>> PS. But Julian is of course still correct regarding debugger.
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>>
>>>
>>
>> --
>> Karsten Kusche - Dipl.Inf. - [hidden email]
>> Tel: +49 3496 21 43 29
>> Georg Heeg eK - Köthen
>> Handelsregister: Amtsgericht Dortmund A 12812
>>
>> _______________________________________________
>> seaside mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>
>
> ------------------------------
>
> Message: 6
> Date: Tue, 18 Nov 2008 07:48:42 +0100
> From: "Philippe Marschall" <[hidden email]>
> Subject: Re: [Seaside] ANN: Seaside 2.9a1 release
> To: "Seaside - general discussion"
> <[hidden email]>
> Message-ID:
> <[hidden email]>
> Content-Type: text/plain; charset="utf-8"
>
> 2008/11/17, Lautaro Fernández <[hidden email]>:
>> 2008/11/15 Philippe Marschall <[hidden email]>
>>
>>> 2008/11/11, Lautaro Fernández <[hidden email]>:
>>>> Hi,
>>>>
>>>> 2008/11/9 Julian Fitzell <[hidden email]>
>>>>
>>>>> [...]
>>>>> 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
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: seaside-2.9.0-alpha1.cs
> Type: application/octet-stream
> Size: 8253 bytes
> Desc: not available
> Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20081118/9b32991a/seaside-2.9.0-alpha1.obj
>
> ------------------------------
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
> End of seaside Digest, Vol 71, Issue 26
> ***************************************