metaTagNamed: (Was Re: [Seaside] inHeadDo:)

[Brian Brown]

On Friday 13 June 2003 06:48 am, Nevin Pratt wrote:
> > Brian
>
> *****************************
> *****************************
> Here's the earlier posts in this thread, which explains
> metaTagNamed:content:
> *****************************
>

Thanks Nevin, I have already read that thread... What I was musing about is 
whether that approach would work well for Javascript in the head of the 
document, or whether some sort of stream based approach would work better. 
Typically, if you are doing Javascript based navigation, there are two parts: 
1) is the code in the <script></script> tags in the head and the other is the 
event code in the html form element or href, like onClick() or onChange().

Usually, you wouldn't want multiple <script></script> tags in the head, 
although they would work. If the handlers could be specified in the same 
methods as the callers of the handlers, thus creating one "submitFunction()" 
that handled all of the javascript actions on a particular page rendering it 
would be ideal.

Even another thought is doing is like the style stuff is done, where a dynamic 
style sheet is created and the link is put in the head... that is probably 
the way to go, isn't it?

any thoughts?

Brian