Mailing-List: contact myfaces-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <myfaces-dev@incubator.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Subject: Re: SV: Javascript Hell
From: Sylvain Vieujot <svieujot@apache.org>
To: MyFaces Development <myfaces-dev@incubator.apache.org>
In-Reply-To: <41ADC294.8090206@apache.org>
References: <1101838655.12472.113.camel@localhost.localdomain>
	 <41AD8904.9090404@apache.org>
	 <1101904367.12472.145.camel@localhost.localdomain>
	 <41ADC294.8090206@apache.org>
Date: Wed, 01 Dec 2004 09:33:17 -0400
Message-Id: <1101907997.12472.158.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=-jY/+VW7owhOSRvZiuD54"


--=-jY/+VW7owhOSRvZiuD54
Content-Transfer-Encoding: 7bit
Content-Type: text/plain

Hello Manfred,

I'll look at it, but I don't think this would work because sometime
(most of the time for me), the JSF part of the page is just a section of
the body.

In starting to implement the Servlet we talked about, I found another
way that I find better :
Today, we have a  Multipart filter for the x:fileUpload.
As we have to declare this filter in the web.xml, I'm generalizing this
filter so that it does the Multipart thing, and serves the resources.
Also, the a filter is better than a servlet, because if we use a
servlet, we have to know it's path in advance, whereas for a filter, we
don't need to add a predefined path to the web.xml.

The name I choose for this filter is :
org.apache.myfaces.component.html.util.ExtensionsFilter

Then, in the doc, we just need to say that to use MyFaces with the
extensions, the above ExtensionsFilter needs to be referenced in the
web.xml

At least, I think this will solve the <script> problem.
I'll work on the CSS part right after (if I can find something).

Sylvain.

On Wed, 2004-12-01 at 14:09 +0100, Manfred Geiler wrote:

> Sylvain,
> I probably found a smarter solution for the "render something in html 
> header afterwards" problem. It's the same problem as the afterwards 
> rendering of hidden input values for client side state saving. So, the 
> statement "the whole page rendering must be buffered (difficult..." is 
> already an issue.
> Have a look at the ViewTag. It uses a buffered body if client state 
> saving is enabled. Components that render state info, do this by calling 
> the StateHandler, which renders temporary tokens. The doAfterBody method 
> in ViewTag finally replaces these tokens by the actual state info.
> There are still some issues to discuss (buffered body necessary also for 
> server state saving, etc.), so please be careful when modifying the 
> ViewTag or any other "deep implementation" class.
> 
> Manfred
> 
> 
> 
> Sylvain Vieujot wrote:
> > I'll try to do the Servlet to handle the script case at least, and I'll 
> > apply it to the popup component, which is one of the simplest case.
> > I think we will find a nice solution for CSS along the road.
> > 
> > Breaking HTML 4 conformance isn't fine, but I don't like either the 
> > solution to add a mandatory tag in the head.
> > Indeed, sometime, it's convenient to use jsf only to a section of a 
> > page, and let jsp handle the rest (including the head).
> > Also, it requires yet another step to use the component, and I really 
> > would like to avoid that.
> > 
> > Sylvain.
> > 
> > On Wed, 2004-12-01 at 10:04 +0100, Manfred Geiler wrote:
> > 
> >>Sylvain Vieujot wrote:
> >>> On Tue, 2004-11-30 at 17:16 +0100, Manfred Geiler wrote:
> >>> 
> >>>>Sylvain,
> >>>>I understand your concerns and I agree that there is already some kind
> >>>>of javascript hell that will become worse.
> >>>>But there are some important issues to consider first:
> >>>>1. There are two kinds of resources
> >>>>   a. those a component needs for rendering directly (e.g. images)
> >>>>   b. those, that must be referenced in HTML Head (javascript, css)
> >>>>2. Handling resources via Servlet can be implemented fast in a simple 
> >>>>way, i.e. getting the Stream for the given name and stream it to the 
> >>>>client. But keep in mind that this is not the only thing a 
> >>>>sophisticated, performance optimized ResourceServlet must do: think of 
> >>>>caching, handling browser HTTP HEAD requests instead of GET, etc.
> >>>>So we should take a look at Tomcats DefaultServlet first, before 
> >>>>reinventing the wheel.
> >>>>
> >>> 
> >>> You're right, but anyway, I think this is not the difficult part.
> >>> 
> >>>>3. The facility method is easy to implement for (1.a.) but difficult to
> >>>>handle for (1.b.). There are two possible solutions:
> >>>>   a. To automatically render the link or script tags in the html head 
> >>>>only if they are really needed, the whole page rendering must be 
> >>>>buffered (difficult, particularly when jsp includes or tiles are used). 
> >>>>Inspecting the component tree prior to rendering is no solution because 
> >>>>on first page access the component tree is empty!
> >>>>   b. The user must configure, which components he is using either 
> >>>>globally in web.xml or as attributes to the tag that Hermod mentions.
> >>>>
> >>> 
> >>> for 1.b, I agree that they might not be any easy way to render the link 
> >>> in the head. But I tried to include script links and css links in the 
> >>> body, and it works fine.
> >>> Is there any objection to do this ? It would really make the all thing easy.
> >>> For the <script src="..."></script>, it's definitely allowed to use it 
> >>> in the body :
> >>> http://www.w3.org/TR/html401/interact/scripts.html
> >>
> >>Yes, only thing to take care of is to not reference a script twice. This 
> >>could either be handled by the components themselves or by the facility 
> >>method you mentioned.
> >>
> >>
> >>> For the <link ...> element the specs says that it should go only in the 
> >>> head ... BUT the limited tests I did show that it works (I don't know if 
> >>> it always works though).
> >>> http://www.w3.org/TR/html401/struct/links.html#h-12.3
> >>> My guess is that it works, but it fails to provide the user with the 
> >>> style sheet alternatives. I don't think this is a problem though as the 
> >>> style sheets we will include this way are meant for the components, not 
> >>> for the whole page display.
> >>> 
> >>> What do you think ?
> >>> Can we still do it for style sheets ?
> >>> Is there another way to do it for <link ...> elements or for style sheets ?
> >>
> >>Hmmm. This means we would knowingly break HTML 4.01 conformance. I fear, 
> >>people will rail against this if they validate the HTML code that is 
> >>rendered by MyFaces.
> >>I suggest the following: We always include a css link for every 
> >>component on every page. This would be the standard configuration and 
> >>since browsers cache css I don't think this would be a performance 
> >>problem. To allow MyFaces to automatically include something in the html 
> >>head we introduce a new extended tag that the user must include in the 
> >>head sections of his JSP. This is the tag that Hermod mentioned.
> >>We could then add expert configuration params that allow to explicitly 
> >>disable single components, so that there is no unnecessary link rendered.
> >>Another way is, to not use <link> or <style> at all and only use inline 
> >>style attributes. This is what the HtmlTabbedPaneRenderer does. Drawback 
> >>is that it is then impossible to alter css for a component without 
> >>subclassing the renderer.
> >>
> >>WDYT?
> >>
> >>
> >>> I don't like the solution of asking the user to configure which 
> >>> components he is using, as it's quiet inefficient, error prone, and add 
> >>> yet another level of complexity.
> >>
> >>Yes, agreed, using components should be as easy as possible.
> >>
> >>
> >>Manfred
> >>
> >>
> >>
> >>
> >>>>
> >>>>hermod.opstvedt@dnbnor.no <mailto:hermod.opstvedt@dnbnor.no> <mailto:hermod.opstvedt@dnbnor.no <mailto:hermod.opstvedt@dnbnor.no>> wrote:
> >>>>> Hi
> >>>>>  
> >>>>> Another solution is to add another tag to the lib, which the developer 
> >>>>> could add at the top of the page - ala the Struts <html:script> tag. 
> >>>>> Making it parameterless so that it could itself find out which librarys 
> >>>>> to load
> >>>>> or
> >>>>> add some more fuctionality to the view <f:tag> so that it would render 
> >>>>> the <link> stuff.
> >>>>>  
> >>>>> Hermod
> >>>>> 
> >>>>>     -----Opprinnelig melding-----
> >>>>>     *Fra:* Sylvain Vieujot [mailto:svieujot@apache.org <mailto:svieujot@apache.org> <mailto:svieujot@apache.org <mailto:svieujot@apache.org>>]
> >>>>>     *Sendt:* 30. november 2004 13:47
> >>>>>     *Til:* MyFaces Development
> >>>>>     *Emne:* Javascript Hell
> >>>>> 
> >>>>>     Hello everybody,
> >>>>> 
> >>>>>     Right now, some components require you to include some javascript
> >>>>>     libraries in your app, and to reference those libraries in your
> >>>>>     page's header.
> >>>>>     Just for your example webapp, the header looks like that :
> >>>>> 
> >>>>>         <!-- JSCook Menu -->
> >>>>> 
> >>>>>   <script language="JavaScript" src="jscookmenu/JSCookMenu.js" type="text/javascript"></script>
> >>>>>   <script language="JavaScript" src="jscookmenu/ThemeOffice/theme.js"></script>
> >>>>>   <link rel="stylesheet" href="jscookmenu/ThemeOffice/theme.css" type="text/css">
> >>>>>   <script language="JavaScript" src="jscookmenu/ThemeMiniBlack/theme.js"></script>
> >>>>>   <link rel="stylesheet" href="jscookmenu/ThemeMiniBlack/theme.css" type="text/css">
> >>>>>   <script language="JavaScript" src="jscookmenu/ThemeIE/theme.js"></script>
> >>>>>   <link rel="stylesheet" href="jscookmenu/ThemeIE/theme.css" type="text/css">
> >>>>>   <script language="JavaScript" src="jscookmenu/ThemePanel/theme.js"></script>
> >>>>>   <link rel="stylesheet" href="jscookmenu/ThemePanel/theme.css" type="text/css">
> >>>>> 
> >>>>>   <!-- JSCalendar -->
> >>>>>   <script language="JavaScript" src="jscalendar/popcalendar.js" type="text/javascript"></script>
> >>>>>   <link rel="stylesheet" href="jscalendar/jscalendar-WH/theme.css" type="text/css">
> >>>>>   <link rel="stylesheet" href="jscalendar/jscalendar-DB/theme.css" type="text/css">
> >>>>> 
> >>>>>   <!-- JSPopup -->
> >>>>>   <script language="JavaScript" src="jspopup/JSPopup.js" type="text/javascript"></script>
> >>>>> 
> >>>>> 
> >>>>>     I'm now working on a new component that is javascript intensive too,
> >>>>>     and that would require the include of at least 5 other .js files.
> >>>>> 
> >>>>>     I think we should make this transparent to the user by :
> >>>>> 
> >>>>>         * Including the scripts/css/whatever required in the myfaces.jar
> >>>>>           file as resources. So, we are sure we always have the .js
> >>>>>           file's version that works, and the developer just needs to
> >>>>>           include the myfaces lib. (this will grow a bite the size of
> >>>>>           the jar though).
> >>>>>         * Have the components load the script/css/whatever in a standard
> >>>>>           way so that the page's developer doesn't need to bother, and
> >>>>>           so that the script/css/... is only included once in the page. 
> >>>>> 
> >>>>>     So, starting to think about a solution for this, here is my first idea :
> >>>>> 
> >>>>>     - Have all those scripts/css/... as resources
> >>>>> 
> >>>>>     - Make an additional servlet that the webapp developper would
> >>>>>     include in his web.xml declarations, and that would be invoqued like :
> >>>>>         http://my.webserver.com/webapp/myFacesRessource?name=jspopup.js
> >>>>> 
> >>>>>         This is the only thing the webapp developper would have to do
> >>>>>         (declare the servlet), but I don't see how we could avoid that
> >>>>>         without writing the scripts/css/... into the page.
> >>>>>         Writing the scripts/css/... into the page would be bad for
> >>>>>         caching, and wouldn't allow us to use standard images with this
> >>>>>         facility.
> >>>>> 
> >>>>>     - Have a facility so that the component's renderer can call
> >>>>>     something like
> >>>>>     includeRessourceScriptLibrary(facesContext,"jspopup/JSPopup.js")
> >>>>>     (similar helper for css, ...), and the code calling the above
> >>>>>     servlet is automatically included in the page.
> >>>>> 
> >>>>>     Any thoughts on this ?
> >>>>> 
> >>>>>     Sylvain. 
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> >>>>> 
> >>>>> This email with attachments is solely for the use of the individual or
> >>>>> entity to whom it is addressed. Please also be aware that the DnB NOR Group
> >>>>> cannot accept any payment orders or other legally binding correspondence 
> >>>>> with
> >>>>> customers as a part of an email.
> >>>>> 
> >>>>> This email message has been virus checked by the virus programs used
> >>>>> in the DnB NOR Group.
> >>>>> 
> >>>>> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> >>
> > 

--=-jY/+VW7owhOSRvZiuD54
Content-Transfer-Encoding: 7bit
Content-Type: text/html; charset=utf-8

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2">
</HEAD>
<BODY>
Hello Manfred,<BR>
<BR>
I'll look at it, but I don't think this would work because sometime (most of the time for me), the JSF part of the page is just a section of the body.<BR>
<BR>
In starting to implement the Servlet we talked about, I found another way that I find better :<BR>
Today, we have a&nbsp; Multipart filter for the x:fileUpload.<BR>
As we have to declare this filter in the web.xml, I'm generalizing this filter so that it does the Multipart thing, and serves the resources.<BR>
Also, the a filter is better than a servlet, because if we use a servlet, we have to know it's path in advance, whereas for a filter, we don't need to add a predefined path to the web.xml.<BR>
<BR>
The name I choose for this filter is :<BR>
org.apache.myfaces.component.html.util.ExtensionsFilter<BR>
<BR>
Then, in the doc, we just need to say that to use MyFaces with the extensions, the above ExtensionsFilter needs to be referenced in the web.xml<BR>
<BR>
At least, I think this will solve the &lt;script&gt; problem.<BR>
I'll work on the CSS part right after (if I can find something).<BR>
<BR>
Sylvain.<BR>
<BR>
On Wed, 2004-12-01 at 14:09 +0100, Manfred Geiler wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Sylvain,</FONT>
<FONT COLOR="#000000">I probably found a smarter solution for the &quot;render something in html </FONT>
<FONT COLOR="#000000">header afterwards&quot; problem. It's the same problem as the afterwards </FONT>
<FONT COLOR="#000000">rendering of hidden input values for client side state saving. So, the </FONT>
<FONT COLOR="#000000">statement &quot;the whole page rendering must be buffered (difficult...&quot; is </FONT>
<FONT COLOR="#000000">already an issue.</FONT>
<FONT COLOR="#000000">Have a look at the ViewTag. It uses a buffered body if client state </FONT>
<FONT COLOR="#000000">saving is enabled. Components that render state info, do this by calling </FONT>
<FONT COLOR="#000000">the StateHandler, which renders temporary tokens. The doAfterBody method </FONT>
<FONT COLOR="#000000">in ViewTag finally replaces these tokens by the actual state info.</FONT>
<FONT COLOR="#000000">There are still some issues to discuss (buffered body necessary also for </FONT>
<FONT COLOR="#000000">server state saving, etc.), so please be careful when modifying the </FONT>
<FONT COLOR="#000000">ViewTag or any other &quot;deep implementation&quot; class.</FONT>

<FONT COLOR="#000000">Manfred</FONT>


<FONT COLOR="#000000">Sylvain Vieujot wrote:</FONT>
<FONT COLOR="#000000">&gt; I'll try to do the Servlet to handle the script case at least, and I'll </FONT>
<FONT COLOR="#000000">&gt; apply it to the popup component, which is one of the simplest case.</FONT>
<FONT COLOR="#000000">&gt; I think we will find a nice solution for CSS along the road.</FONT>
<FONT COLOR="#000000">&gt; </FONT>
<FONT COLOR="#000000">&gt; Breaking HTML 4 conformance isn't fine, but I don't like either the </FONT>
<FONT COLOR="#000000">&gt; solution to add a mandatory tag in the head.</FONT>
<FONT COLOR="#000000">&gt; Indeed, sometime, it's convenient to use jsf only to a section of a </FONT>
<FONT COLOR="#000000">&gt; page, and let jsp handle the rest (including the head).</FONT>
<FONT COLOR="#000000">&gt; Also, it requires yet another step to use the component, and I really </FONT>
<FONT COLOR="#000000">&gt; would like to avoid that.</FONT>
<FONT COLOR="#000000">&gt; </FONT>
<FONT COLOR="#000000">&gt; Sylvain.</FONT>
<FONT COLOR="#000000">&gt; </FONT>
<FONT COLOR="#000000">&gt; On Wed, 2004-12-01 at 10:04 +0100, Manfred Geiler wrote:</FONT>
<FONT COLOR="#000000">&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;Sylvain Vieujot wrote:</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; On Tue, 2004-11-30 at 17:16 +0100, Manfred Geiler wrote:</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;Sylvain,</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;I understand your concerns and I agree that there is already some kind</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;of javascript hell that will become worse.</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;But there are some important issues to consider first:</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;1. There are two kinds of resources</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;   a. those a component needs for rendering directly (e.g. images)</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;   b. those, that must be referenced in HTML Head (javascript, css)</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;2. Handling resources via Servlet can be implemented fast in a simple </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;way, i.e. getting the Stream for the given name and stream it to the </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;client. But keep in mind that this is not the only thing a </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;sophisticated, performance optimized ResourceServlet must do: think of </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;caching, handling browser HTTP HEAD requests instead of GET, etc.</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;So we should take a look at Tomcats DefaultServlet first, before </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;reinventing the wheel.</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; You're right, but anyway, I think this is not the difficult part.</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;3. The facility method is easy to implement for (1.a.) but difficult to</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;handle for (1.b.). There are two possible solutions:</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;   a. To automatically render the link or script tags in the html head </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;only if they are really needed, the whole page rendering must be </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;buffered (difficult, particularly when jsp includes or tiles are used). </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;Inspecting the component tree prior to rendering is no solution because </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;on first page access the component tree is empty!</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;   b. The user must configure, which components he is using either </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;globally in web.xml or as attributes to the tag that Hermod mentions.</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; for 1.b, I agree that they might not be any easy way to render the link </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; in the head. But I tried to include script links and css links in the </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; body, and it works fine.</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; Is there any objection to do this ? It would really make the all thing easy.</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; For the &lt;script src=&quot;...&quot;&gt;&lt;/script&gt;, it's definitely allowed to use it </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; in the body :</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; <A HREF="http://www.w3.org/TR/html401/interact/scripts.html">http://www.w3.org/TR/html401/interact/scripts.html</A></FONT>
<FONT COLOR="#000000">&gt;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;Yes, only thing to take care of is to not reference a script twice. This </FONT>
<FONT COLOR="#000000">&gt;&gt;could either be handled by the components themselves or by the facility </FONT>
<FONT COLOR="#000000">&gt;&gt;method you mentioned.</FONT>
<FONT COLOR="#000000">&gt;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; For the &lt;link ...&gt; element the specs says that it should go only in the </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; head ... BUT the limited tests I did show that it works (I don't know if </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; it always works though).</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; <A HREF="http://www.w3.org/TR/html401/struct/links.html#h-12.3">http://www.w3.org/TR/html401/struct/links.html#h-12.3</A></FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; My guess is that it works, but it fails to provide the user with the </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; style sheet alternatives. I don't think this is a problem though as the </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; style sheets we will include this way are meant for the components, not </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; for the whole page display.</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; What do you think ?</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; Can we still do it for style sheets ?</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; Is there another way to do it for &lt;link ...&gt; elements or for style sheets ?</FONT>
<FONT COLOR="#000000">&gt;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;Hmmm. This means we would knowingly break HTML 4.01 conformance. I fear, </FONT>
<FONT COLOR="#000000">&gt;&gt;people will rail against this if they validate the HTML code that is </FONT>
<FONT COLOR="#000000">&gt;&gt;rendered by MyFaces.</FONT>
<FONT COLOR="#000000">&gt;&gt;I suggest the following: We always include a css link for every </FONT>
<FONT COLOR="#000000">&gt;&gt;component on every page. This would be the standard configuration and </FONT>
<FONT COLOR="#000000">&gt;&gt;since browsers cache css I don't think this would be a performance </FONT>
<FONT COLOR="#000000">&gt;&gt;problem. To allow MyFaces to automatically include something in the html </FONT>
<FONT COLOR="#000000">&gt;&gt;head we introduce a new extended tag that the user must include in the </FONT>
<FONT COLOR="#000000">&gt;&gt;head sections of his JSP. This is the tag that Hermod mentioned.</FONT>
<FONT COLOR="#000000">&gt;&gt;We could then add expert configuration params that allow to explicitly </FONT>
<FONT COLOR="#000000">&gt;&gt;disable single components, so that there is no unnecessary link rendered.</FONT>
<FONT COLOR="#000000">&gt;&gt;Another way is, to not use &lt;link&gt; or &lt;style&gt; at all and only use inline </FONT>
<FONT COLOR="#000000">&gt;&gt;style attributes. This is what the HtmlTabbedPaneRenderer does. Drawback </FONT>
<FONT COLOR="#000000">&gt;&gt;is that it is then impossible to alter css for a component without </FONT>
<FONT COLOR="#000000">&gt;&gt;subclassing the renderer.</FONT>
<FONT COLOR="#000000">&gt;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;WDYT?</FONT>
<FONT COLOR="#000000">&gt;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; I don't like the solution of asking the user to configure which </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; components he is using, as it's quiet inefficient, error prone, and add </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt; yet another level of complexity.</FONT>
<FONT COLOR="#000000">&gt;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;Yes, agreed, using components should be as easy as possible.</FONT>
<FONT COLOR="#000000">&gt;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;Manfred</FONT>
<FONT COLOR="#000000">&gt;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;<A HREF="mailto:hermod.opstvedt@dnbnor.no">hermod.opstvedt@dnbnor.no</A> &lt;mailto:<A HREF="mailto:hermod.opstvedt@dnbnor.no">hermod.opstvedt@dnbnor.no</A>&gt; &lt;mailto:<A HREF="mailto:hermod.opstvedt@dnbnor.no">hermod.opstvedt@dnbnor.no</A> &lt;mailto:<A HREF="mailto:hermod.opstvedt@dnbnor.no">hermod.opstvedt@dnbnor.no</A>&gt;&gt; wrote:</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; Hi</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;  </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; Another solution is to add another tag to the lib, which the developer </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; could add at the top of the page - ala the Struts &lt;html:script&gt; tag. </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; Making it parameterless so that it could itself find out which librarys </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; to load</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; or</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; add some more fuctionality to the view &lt;f:tag&gt; so that it would render </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; the &lt;link&gt; stuff.</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;  </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; Hermod</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     -----Opprinnelig melding-----</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     *Fra:* Sylvain Vieujot [mailto:<A HREF="mailto:svieujot@apache.org">svieujot@apache.org</A> &lt;mailto:<A HREF="mailto:svieujot@apache.org">svieujot@apache.org</A>&gt; &lt;mailto:<A HREF="mailto:svieujot@apache.org">svieujot@apache.org</A> &lt;mailto:<A HREF="mailto:svieujot@apache.org">svieujot@apache.org</A>&gt;&gt;]</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     *Sendt:* 30. november 2004 13:47</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     *Til:* MyFaces Development</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     *Emne:* Javascript Hell</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     Hello everybody,</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     Right now, some components require you to include some javascript</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     libraries in your app, and to reference those libraries in your</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     page's header.</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     Just for your example webapp, the header looks like that :</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;         &lt;!-- JSCook Menu --&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;   &lt;script language=&quot;JavaScript&quot; src=&quot;jscookmenu/JSCookMenu.js&quot; type=&quot;text/javascript&quot;&gt;&lt;/script&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;   &lt;script language=&quot;JavaScript&quot; src=&quot;jscookmenu/ThemeOffice/theme.js&quot;&gt;&lt;/script&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;   &lt;link rel=&quot;stylesheet&quot; href=&quot;jscookmenu/ThemeOffice/theme.css&quot; type=&quot;text/css&quot;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;   &lt;script language=&quot;JavaScript&quot; src=&quot;jscookmenu/ThemeMiniBlack/theme.js&quot;&gt;&lt;/script&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;   &lt;link rel=&quot;stylesheet&quot; href=&quot;jscookmenu/ThemeMiniBlack/theme.css&quot; type=&quot;text/css&quot;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;   &lt;script language=&quot;JavaScript&quot; src=&quot;jscookmenu/ThemeIE/theme.js&quot;&gt;&lt;/script&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;   &lt;link rel=&quot;stylesheet&quot; href=&quot;jscookmenu/ThemeIE/theme.css&quot; type=&quot;text/css&quot;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;   &lt;script language=&quot;JavaScript&quot; src=&quot;jscookmenu/ThemePanel/theme.js&quot;&gt;&lt;/script&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;   &lt;link rel=&quot;stylesheet&quot; href=&quot;jscookmenu/ThemePanel/theme.css&quot; type=&quot;text/css&quot;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;   &lt;!-- JSCalendar --&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;   &lt;script language=&quot;JavaScript&quot; src=&quot;jscalendar/popcalendar.js&quot; type=&quot;text/javascript&quot;&gt;&lt;/script&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;   &lt;link rel=&quot;stylesheet&quot; href=&quot;jscalendar/jscalendar-WH/theme.css&quot; type=&quot;text/css&quot;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;   &lt;link rel=&quot;stylesheet&quot; href=&quot;jscalendar/jscalendar-DB/theme.css&quot; type=&quot;text/css&quot;&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;   &lt;!-- JSPopup --&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;   &lt;script language=&quot;JavaScript&quot; src=&quot;jspopup/JSPopup.js&quot; type=&quot;text/javascript&quot;&gt;&lt;/script&gt;</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     I'm now working on a new component that is javascript intensive too,</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     and that would require the include of at least 5 other .js files.</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     I think we should make this transparent to the user by :</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;         * Including the scripts/css/whatever required in the myfaces.jar</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;           file as resources. So, we are sure we always have the .js</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;           file's version that works, and the developer just needs to</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;           include the myfaces lib. (this will grow a bite the size of</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;           the jar though).</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;         * Have the components load the script/css/whatever in a standard</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;           way so that the page's developer doesn't need to bother, and</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;           so that the script/css/... is only included once in the page. </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     So, starting to think about a solution for this, here is my first idea :</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     - Have all those scripts/css/... as resources</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     - Make an additional servlet that the webapp developper would</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     include in his web.xml declarations, and that would be invoqued like :</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;         <A HREF="http://my.webserver.com/webapp/myFacesRessource?name=jspopup.js">http://my.webserver.com/webapp/myFacesRessource?name=jspopup.js</A></FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;         This is the only thing the webapp developper would have to do</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;         (declare the servlet), but I don't see how we could avoid that</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;         without writing the scripts/css/... into the page.</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;         Writing the scripts/css/... into the page would be bad for</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;         caching, and wouldn't allow us to use standard images with this</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;         facility.</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     - Have a facility so that the component's renderer can call</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     something like</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     includeRessourceScriptLibrary(facesContext,&quot;jspopup/JSPopup.js&quot;)</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     (similar helper for css, ...), and the code calling the above</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     servlet is automatically included in the page.</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     Any thoughts on this ?</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt;     Sylvain. </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; This email with attachments is solely for the use of the individual or</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; entity to whom it is addressed. Please also be aware that the DnB NOR Group</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; cannot accept any payment orders or other legally binding correspondence </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; with</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; customers as a part of an email.</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; This email message has been virus checked by the virus programs used</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; in the DnB NOR Group.</FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; </FONT>
<FONT COLOR="#000000">&gt;&gt;&gt;&gt;&gt; * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *</FONT>
<FONT COLOR="#000000">&gt;&gt;</FONT>
<FONT COLOR="#000000">&gt; </FONT>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>

--=-jY/+VW7owhOSRvZiuD54--