> This is very interesting... I need to know more. > > My biggest concern (right now) with switching to JSF is having > to teach our web designers JSF tages. > They want to work in HTML and Javascript and use there favorite > Web design tools (e.g. Dreamweaver). > They also often have to begin designing the pages and flow etc > before any of the application is ready. > > Where can I find more info on this? >
The documentation is pretty light. The features documentation has not been updated for the full html views yet. http://struts.apache.org/shale/features.html#clay http://people.apache.org/~craigmcc/shale-clay-javadocs/ But, the rolodex usecase example in the nightly builds shows the three types of Clay composition including full html views. http://cvs.apache.org/builds/struts/nightly/struts-shale/use-cases/ We encourage your feedback :-) Gary > > > -----Original Message----- > From: Wendy Smoak [mailto:[EMAIL PROTECTED] > Sent: Monday, August 08, 2005 7:18 PM > To: Struts Users Mailing List > Subject: Re: [OT] JSP Clutter > > From: "Michael Jouravlev" <[EMAIL PROTECTED]> > > > With Tapestry you create HTML template for each page, then stick data > > into it, using jwcid attribute. Your webdesigner is happy. > > > With JSF you compose page using JSF tags either manually or using > > visual IDE, and then JSP/JSF engine will generate HTML in the runtime > > (I don't know how HTML is generated if you do not wrap JSF markup with > > JSP). Your webdesigner is not too happy, he needs to learn new IDE and > > the final page design may be not too... er... artistic, as with plain > > HTML/Tapestry. > > Or... with JSF + Shale, you create an HTML template for each page, then > > stick data into it, using the 'jsfid' attribute. Your webdesigner is > happy > again. ;) > > Here's an example using Shale's Tapestry-like views from the Rolodex in > the > 'use cases' webapp: > http://svn.apache.org/viewcvs.cgi/struts/shale/trunk/use-cases/src/web/r > olodex/address.html?rev=209993&view=markup > > -- > Wendy Smoak > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
