[Seaside] Re: 2.5b2

Thu Jul 29 00:50:18 CEST 2004

On Jul 28, 2004, at 2:03 AM, Kamil Kukura wrote:

> Avi Bryant wrote:
>> Hi folks,
>> Just released Seaside 2.5b2.  The changes from b1, mostly thanks to  
>> Adrian Lienhard and Michel Bany, are:
>
> I just upgraded to this version and here are some remarks:
>
> - still don't have asMutator used in 
> WAHtmlRenderer)>>radioButtonInGroup:withValue:on:of: so I needed to 
> backfix this.

Oh, weird, sorry.  I was sure I put that in.  Ok, will definitely go 
into the next round of fixes.

> - using scripts and styles in external files I had to put everything 
> regarding <head>...</head> content into #updateRoot: while holding on 
> its super's counterpart. I use #addHeadElement: so now I'm not sure if 
> it will survive next versions. More on that below.

I think #addHeadElement: will stick around.  But if you find yourself 
using it, it's a sign that there's a missing convenience method.  What 
kind of elements are you adding?  You need #addStyleLink: or something?

> - now updating document's title from #updateRoot: in the root 
> component.  Perhaps there could be better way for a component to 
> alternate document's title.

Perhaps.   But what? :) Do you have any suggestions?

> Well, but I see all of WAStandardScripts and WAStandardStyles in every 
> application configured. First I was shocked why simple counter has so 
> many stylesheets attached to it.

Yeah, I know, I was a bit unsure about that too.  But I don't see that 
it hurts that much (they're cached by the browser and presumably 
ignored from then on).  And otherwise there's a huge configuration 
hassle trying to figure out which ones to include and which not to.

> I must admit I don't understand library browser much.

Yeah, it's clunky, and of limited use right now.  I expect people 
mostly to edit style libraries with the normal system browser for now.  
But in the long run I would like to get the library browser to the 
point where designers could reasonably use it.  The idea I was starting 
with was that you should be able to easily find the appropriate styles 
for a given component using the halos, which is what the #findStyles 
stuff and the search box in the library browser are all about.  But 
they're very much works in progress, and all suggestions are 
appreciated.

> I think WARenderedHtmlRoot>>write[Script|Style]:on: is quite rough. I 
> see there idea of "EITI - Everything In The Image" but I guess there 
> could be finer control for styles/scripts inclusion.
> How do you like the idea of having classes such as WAScriptContent 
> having #scriptType and #isDeferred that would correspond to <style>'s 
> attributes. Similiarly, for WAStyleContent there would be #styleType, 
> #title, #isAlternate, #media. And finally their master WALinkedContent 
> would have #charset.
> In any case I agree with EITI philosophy but I think there still 
> should be an easy way to add <head>'s element with an explicit URL.

So you would have one class per style instead of one method per style?  
That might be ok.  I think there should still be an easy way to package 
them up into "suites" for easy inclusion (StandardStyleSuite, etc).

> - no remove action for "config" in "config" web application

That's intentional.  Why do you want to remove it?

> - in configuration window, button "Save" packed within "General" 
> section

Put Save with General, and keep Done where it is now?

> - toolbar's items separated with " | "

Anyone else also prefer this?  I'm fine either way.

Thanks very much for the comments.  Keep them coming.

Avi