> -----Original Message----- > From: Wendy Smoak [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 22, 2004 12:02 PM > To: Struts Users Mailing List > Subject: Struts and DreamWeaver > > > This is my first time having someone else do the page design. > I'm thrilled > to have someone else do it, but they use DreamWeaver and I'm > not sure what's > going to happen if it sees <html-el:form>. Then there's the > fun of JSTL > tags embedded within HTML tags, which works fine but can't exactly be > considered valid syntax. > > I checked the archives, but only found suggestions to use > something other > than DreamWeaver. I don't think that's going to go over well.
If you're paying them... who cares? It's your dime, your way or the highway :) > > My current plan is to have them use plain-old html form > elements, and I'll > automate as much as possible the task of switching them over to > <html-el:...> tags. Not much fun, but far better than > having to do the > page design. Having done that... don't. It's a pain in the rear. > > Does anyone have suggestions for coordinating page design > with Struts webapp > development? DreamWeaver should support the tags, and ignore the JSTL. My biggest worry with DreamWeaver would be the HTML code the thing generates. Typically it's pretty abysmal. I have marketing people who generate better HTML then DreamCleaver does. I'd write into the contract, the jsp tags and W3C compliant HTML code, all for a fixed price or you'll end up paying for their cleaning up after their "tool". --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
