I attended OSCON last week and was introduced to Tapestry, JSF's "competitor". Tapestry doesn't have the exact same problems as JSF because instead of creating a whole new line of tags it uses existing HTML tags (i.e. <input>) and marks them up further by adding new attributes to them. This aids in graphical development for non-JSF compliant editors because the <input> tag will still render as it should when going into preview mode.
Note that there was talk on the Dreamweaver site of having support for JSF in the future. I haven't looked at it in several months, so I don't know the status of it. On my last project I was fortunate enough to have a designer that was looking forward to the challenge of doing JSF in Dreamweaver, and it all worked out. But I know where you are coming from. Aaron Bartell -----Original Message----- From: Lindholm, Greg [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 09, 2005 2:47 PM To: [email protected] Subject: Web designers want to work with there favorite web design tools My biggest concern (right now) with switching to JSF is having to teach our web designers JSF tags. 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. If our web designers can't use there favorite tools they become significantly less productive and a fair bit cranky. This seems to me like a significant obstacle to adoption. I heard about an HTML template mechanism using Shale (doesn't seem like it's quite ready yet.) I've seen an occasional reference to HTML/JSF templates here without much detail. Can anyone tell me what is available now in the JSF world that will keep the web designers happy and productive? (Are these ready for real use now?) (Sorry for the cross-posting, I posted a similar message to the Struts list regarding Shale but I really wanted to hear what the MyFaces group has to say.)
