seaside-dev July 2008

seaside-dev@lists.squeakfoundation.org

11 participants
124 discussions

Issue 108 in seaside: Table Data's should render '  ' when rendering nil
by codesite-noreply＠google.com 31 Jul '08

31 Jul '08

Issue 108: Table Data's should render ' ' when rendering nil http://code.google.com/p/seaside/issues/detail?id=108 Comment #3 by renggli: (No comment was entered for this change.) Issue attribute updates: Status: WontFix -- 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 108 in seaside: Table Data's should render '  ' when rendering nil
by codesite-noreply＠google.com 31 Jul '08

31 Jul '08

Issue 108: Table Data's should render ' ' when rendering nil http://code.google.com/p/seaside/issues/detail?id=108 Comment #2 by Thornborrow.John: That works fine for me, and makes better sense than to add unecessary characters to the markup. -- 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

encoding/decoding Streams
by Paolo Bonzini 31 Jul '08

31 Jul '08

I have two questions: 1) Would it make sense to change WACodec>>#encode: and WACodec>>#decode: to accept streams instead of Strings? 2) The tests for codecs assume that the source encoding is ISO-8859-1. This is fine for testing purposes, but not necessarily for deployment. Would it make sense then to change the constructor so that it can take a source and destination encoding? Or is there something I'm missing? Paolo

2 5

Issue 13 in seaside: Dispatcher #basePath should be fully customizable
by codesite-noreply＠google.com 31 Jul '08

31 Jul '08

Issue 13: Dispatcher #basePath should be fully customizable http://code.google.com/p/seaside/issues/detail?id=13 Comment #1 by jfitzell: In the config cleanup branch, I've pushed the URL configuration preferences up so they are usable by all entry points. I assume this is what you were looking for? I've also set it up so that a request handler inherits its #baseUrl from its parent, overwriting elements from its own configuration and then adding its own name. -- 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

Seaside 2.9 Package Depenedencies
by Lukas Renggli 30 Jul '08

30 Jul '08

I created a new graph with the package dependencies within the Seaside 2.9 repository: http://www.lukas-renggli.ch/dropbox/seaside-2.9/seaside.dot http://www.lukas-renggli.ch/dropbox/seaside-2.9/seaside.png http://www.lukas-renggli.ch/dropbox/seaside-2.9/seaside.svg The SVG is the most useful output format (in Safari and FireFox), moving the mouse over the dependencies displays the reason within a tooltip. Quickly glancing over the result I see a single circular reference. The one discussed in the mailing-list and reported here: http://code.google.com/p/seaside/issues/detail?id=28 To reproduce the result load Package-Dependencies from http://source.lukas-renggli.ch/unsorted. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

3 6

#decorationClasses preference
by Julian Fitzell 29 Jul '08

29 Jul '08

Lukas, As I look at the preference for decoration classes, I wonder how useful it is. First of all, most of the decoration classes require parameters to be set, so they can't be created just by knowing the class. Secondly, there's the issue of property value inheritance, which we were discussing. While I can imagine an implementation of a collection attribute value that allows additions and/or deletions from the inherited value instead of just overriding it, the ordering of decorations is going to be frequently very important. Plus, if you are inheriting a value from several parents, how do you merge those (or do you?) If I try to picture an interface that lets you deal with merging several inherited collections coming up with a working ordering, and then defining deletions and insertions in the correct location so you *still* have a correct ordering I just can't imagine how it would work. I'm inclined to drop that preference and add one that adds a tool decoration, since that was presumably the immediate need. Thoughts? Julian

5 11

Issue 109 in seaside: Get rid of IDs for Styling
by codesite-noreply＠google.com 28 Jul '08

28 Jul '08

Issue 109: Get rid of IDs for Styling http://code.google.com/p/seaside/issues/detail?id=109 Comment #1 by obi068: - I could check the SU examples and components. - Not sure if we should also change the lightbox CSS -- 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 109 in seaside: Get rid of IDs for Styling
by codesite-noreply＠google.com 28 Jul '08

28 Jul '08

Issue 109: Get rid of IDs for Styling http://code.google.com/p/seaside/issues/detail?id=109 New issue report by renggli: - check Scriptaculous - check Seaside Issue attributes: Status: Accepted Owner: renggli Labels: Type-Other Priority-Low -- 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

Re: Configurations
by Julian Fitzell 26 Jul '08

26 Jul '08

On Sat, Jul 26, 2008 at 7:08 PM, Lukas Renggli <renggli(a)iam.unibe.ch> wrote: >> + the name of the preference? > > What about just dropping the session prefix? #continuationCacheSize? > > The fact that the continuations are within the session is already given as > the attribute is defined in WASessionConfiguration. Well, it may be defined on WASessionConfiguration but the namespace for attribute keys is still global. Namespacing everything by prefix is not so important for attributes in core, obviously, so as long as we don't anticipate any other continuation caches any time soon we could drop it... but it also doesn't bother me *per se* that it's long. The attribute's only used one place and we can now override the label shown in the UI to be shorter. >> + the name and existence of #performDefaultRequest: >> >> I tend to think the complex chaing of request handling methods sucks >> and I hate to make it bigger but my thinking was that: > > I agree that the long chain of request handling methods suck. It also > wastest memory when continuations are used. In Seaside 2.8 we reduced if > from around 120 down to about 50 stack frames. You can see this number in > WAFlowFunctionalTest (in the context of a flow). mm... good point. >> - I can't do what I need to do in the constructor because the >> application isn't set (no preferences) > > What about overriding #setParent: of WASession? This is where the > application is set and therefore the place to fetch any preferences. > > Name: Seaside-Core-lr.configcleanup.40 > Author: lr > Time: 26 July 2008, 1:06:14 pm > UUID: 73e232cf-be36-44a8-9644-f6d6fbc173b1 > Ancestors: Seaside-Core-jf.configcleanup.36 Yeah I considered doing it that way. I'm fine with that if you like it. > - set #sessionContinuationCacheSize in WASession>>#setParent: > > Another thing: Do we really need the test "self sessionContinuationCacheSize > isNil"? I think this can never be nil, as the default value is taken > otherwise. Well originally I had no default because I wanted it to use the default from the code in WALRUCache. Then I didn't like the big glaring text box in the UI so I decided to put in a default. :) I was also considering defining WASession>>preferenceAt: as: preferenceAt: aSymbol ^ self application isNil ifFalse: [self application preferenceAt: aSymbol] since there seems to be code (at least in the tests) that uses WASession without setting a parent (and if you can't use it without a parent then it really ought to be passed into the initialization method). That was my reasoning. > Cheers, > Lukas > > PS: I think we should continue this kind of discussion on seaside-dev. Agreed. Done. Julian

1 0

Issue 108 in seaside: Table Data's should render '  ' when rendering nil
by codesite-noreply＠google.com 24 Jul '08

24 Jul '08

Issue 108: Table Data's should render ' ' when rendering nil http://code.google.com/p/seaside/issues/detail?id=108 Comment #1 by renggli: This is a CSS issue in IE. I suggest not to do anything about that in Seaside. There is a CSS property called "empty-cells" (http://www.w3.org/TR/CSS21/tables.html#empty-cells). It defaults to show on all browser, except for IE that does not support the property and defaults to hide. There are several workarounds available that you might find through Google, like http://www.tgrayimages.com/show-empty-table-cells-with-css-in-internet-expl… -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev July 2008