seaside-dev September 2008

seaside-dev@lists.squeakfoundation.org

13 participants
301 discussions

Re: [Seaside-dev] basicNew
by Avi Bryant 07 Jan '09

07 Jan '09

On Mon, Sep 29, 2008 at 12:43 PM, Randal L. Schwartz <merlyn(a)stonehenge.com> wrote: > Avi> Change super to self in this method, and (given the rest of the code > Avi> in my example) you would have infinite recursion. > > I didn't see that you had a local initialize. If you had, then > *it* should have been the one to have super initialize, since the local > initialize is superceding it by extension. And what would the rest of that method look like? What would the other methods look like? This is a fairly intricate convention and it doesn't make sense to look at an individual piece of it in isolation. If you're arguing that the local initialize should call its super method, can you also show what the rest of this (tiny) example would look like so I can understand the entire control flow you're proposing? Avi

6 14

Issue 191 in seaside: WAConvenienceFunctionalTest is failing
by codesite-noreply＠google.com 06 Oct '08

06 Oct '08

Issue 191: WAConvenienceFunctionalTest is failing http://code.google.com/p/seaside/issues/detail?id=191 Comment #4 by renggli: This bug is very odd. Indeed the bug shows up in recent changes of WATask, but these changes used to work. Was there anything recently changed on how the render loop works? Issue attribute updates: Owner: --- -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

2 1

Issue 192 in seaside: clean up WASqueakPlatform
by codesite-noreply＠google.com 06 Oct '08

06 Oct '08

Issue 192: clean up WASqueakPlatform http://code.google.com/p/seaside/issues/detail?id=192 Comment #2 by jfitzell: +1 to both -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

2 1

basicNew
by Julian Fitzell 05 Oct '08

05 Oct '08

Seaside-Core-pmm.267.mcz - use #new instead of #basicNew for WACallbackRegistry, using #basicNew has already lead to interesing bugs in other places I always thought the pattern was: Foo class>>bar: param ^ self basicNew initializeWithBar: param Foo>>initializeWithBar: param self initialize. bar := param I guess calling new instead of basicNew and not call #initialize from #initializeWithBar: also works, but means you don't have control over when (or if) #initialize gets called. I have to admit that the whole initialization pattern feels a bit ugly both ways though. Is this the preferred pattern throughout now? Julian

4 9

expiry policies
by Julian Fitzell 05 Oct '08

05 Oct '08

Comments please... :) Name: Seaside-Core-jf.expirypolicy.1 Author: jf Time: 17 September 2008, 4:35:48 pm UUID: 7c944d9c-8681-cb45-b1e4-66c8a18d38f6 Ancestors: Seaside-Core-jf.239 Expirment pulling session expiry behaviour (actually expiring handler expiry) into its own set of expiry policy classes. Name: Seaside-Session-jf.expirypolicy.1 Author: jf Time: 17 September 2008, 4:37:26 pm UUID: 77c0b7ef-77ec-9347-a1c6-a99f8bc1cd89 Ancestors: Seaside-Session-pmm.12 The introduction of expiry policies in Seaside-Core-jf.expirypolicy.1 allows us to remove #incomingRequest: from WASession and just use #responseForContext: Not sure how best (or whether) to mark the old method as deprecated...

5 13

Issue 16 in seaside: Lightbox with WATask
by codesite-noreply＠google.com 30 Sep '08

30 Sep '08

Issue 16: Lightbox with WATask http://code.google.com/p/seaside/issues/detail?id=16 Comment #2 by renggli: Name: Seaside-Component-lr.11 Author: lr Time: 30 September 2008, 6:54:50 pm UUID: 91dbace0-ee93-4849-8f92-7d7868a58dae Ancestors: Seaside-Component-jf.10 - restored the old and crappy code of WATask that does a redirect, but that's the only thing that seems to work - this re-opens Issue 16 and Issue 121 - this closes Issue 191 Issue attribute updates: Status: Accepted Owner: --- -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 121 in seaside: WATask does a redirect
by codesite-noreply＠google.com 30 Sep '08

30 Sep '08

Issue 121: WATask does a redirect http://code.google.com/p/seaside/issues/detail?id=121 Comment #4 by renggli: Name: Seaside-Component-lr.11 Author: lr Time: 30 September 2008, 6:54:50 pm UUID: 91dbace0-ee93-4849-8f92-7d7868a58dae Ancestors: Seaside-Component-jf.10 - restored the old and crappy code of WATask that does a redirect, but that's the only thing that seems to work - this re-opens Issue 16 and Issue 121 - this closes Issue 191 Issue attribute updates: Status: Accepted Owner: --- -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 191 in seaside: WAConvenienceFunctionalTest is failing
by codesite-noreply＠google.com 30 Sep '08

30 Sep '08

Issue 191: WAConvenienceFunctionalTest is failing http://code.google.com/p/seaside/issues/detail?id=191 Comment #6 by renggli: Name: Seaside-Component-lr.11 Author: lr Time: 30 September 2008, 6:54:50 pm UUID: 91dbace0-ee93-4849-8f92-7d7868a58dae Ancestors: Seaside-Component-jf.10 - restored the old and crappy code of WATask that does a redirect, but that's the only thing that seems to work - this re-opens Issue 16 and Issue 121 - this closes Issue 191 Issue attribute updates: Status: Fixed Owner: renggli -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 191 in seaside: WAConvenienceFunctionalTest is failing
by codesite-noreply＠google.com 30 Sep '08

30 Sep '08

Issue 191: WAConvenienceFunctionalTest is failing http://code.google.com/p/seaside/issues/detail?id=191 Comment #5 by jfitzell: I'm playing with the RenderLoop a bit in a branch but I can't think of anything off the top of my head that has changed in the mainline... at least nothing directly to the render loop... -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 191 in seaside: WAConvenienceFunctionalTest is failing
by codesite-noreply＠google.com 29 Sep '08

29 Sep '08

Issue 191: WAConvenienceFunctionalTest is failing http://code.google.com/p/seaside/issues/detail?id=191 Comment #3 by renggli: I can confirm this bug. Seems to be indeed related to the WATask refactoring. I'll have a look. Issue attribute updates: Owner: renggli -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev September 2008