Sylvain, I see your point about the quick reference. Maybe we could use both of our ideas. I think they each have their own uses. We could use the "overview" page as you are describing to show a basic overview. Maybe instead of putting it in the home page of the simple examples we could use it in the new overview page (see the components tab on the new myfaces site.) That page is currently blank but I was planning on putting some general info there. This might be a nice fit. Plus we can link to the TLD docs from there as you are suggesting.
Yes, I think it's a better idea. The website is definitely the place.
A couple of questions about your example. What does [View example] do?
It would link to the component's page in the simple-webapp.
But I guess this doesn't work anymore if we display this page on the web.
Also, what do we do about some of the x components with a lot of HTML. I worry a little that this format might not work for the more complicated custom components. Still, I think its a good idea to try.
Yes, this might be a problem.
I such cases, we could maybe just put a small image.
Back to the simple examples ... I think you have a good idea about having the source visible from the example itself instead of the top level page. I will investigate the display tag solution you are proposing. sean On Tue, 15 Mar 2005 00:12:20 -0400, Sylvain Vieujot <[EMAIL PROTECTED]> wrote: > Hello Sean, > > The main idea was to have a very small example & snipset for all the > components (h: & x:) on a single page instead of having to click on the > links. > For example : > > commandLink > <h:commandLink id="link" action="" <h:outputText > value="#{msg.linkName}"/> </h:commandLink> Next Page [View example] > [View TDL doc] > ..... > > > This is more a quick reference, but using it as the simple webapp home page > would show quickly all the provided components. > The only problem might be that for some components, they can't be rendered > in such a small space. > > Once in the example page, to show the source, you can copy the jsp files to > .jsp.source, and then in the page, link to this file like they do on > displaytag.org : > http://www.displaytag.org/example-nocolumns.jsp > This is easy and doesn't require any servlet. Just a small modification of > the build.xml file. > > Sylvain. > > > On Mon, 2005-03-14 at 22:54 -0500, Sean Schofield wrote: > Sylvain, Thanks for the feedback. I took a look at your link. I am a big > fan of that website and I use if for quick reference sometimes when I forget > the syntax of a standard jsf tag. I had some ideas a while back similar to > this > (http://www.mail-archive.com/[email protected]/msg00624.html). > Now that we have the simple application, we can build on it and show the > source code that corresponds to the page. I am thinking of two links. First > link [view example], second link [view soure]. The view source link would > just return the escaped JSP. Not sure of the best approach for that. Perhaps > a servlet that just reads the JSP file and streams the contents without > processing? Any ideas on that? Also I am making progress on the > documentation. I have a standard template that we can use to document the > components. I ported over the JSCookMenu documentation and I wrote up some > documentation for tree2. I think Matthias is going to commit it for me > shortly. sean On Mon, 14 Mar 2005 21:49:52 -0400, Sylvain Vieujot > <[EMAIL PROTECTED]> wrote: > The simple webapp is great. Thanks. > > Here > is a page I like quite a lot : > > http://www.exadel.com/tutorial/jsf/jsftags-guide.html > Maybe we could use a > page like that as the home page of the simple webapp. > > Any thoughts ? > > > Sylvain.
