Stefano Mazzocchi wrote:
Thanks Stefano. I don't have an immediate itch but things could change.Reinhard Poetz wrote:
- WYSIWIG publishing not possible (or only with some limitations)
I think that for Tapestry you have to change the plus and minus signs. JSF tools probably need some time (years?) to become as mature as HTML-WYSIWIG tools like Dreamweaver.
After a lot of thinking a few questions remain?
- See the (dis)advantages above? Are there any more and which ones are the bigger ones?
- Is 'roundtrip' WYSIWIG-editing with Cocoon Forms a goal for us or do we say "... if you need it take Tapestry, JSF, ..."
- If it is a goal, is 'roundtrip' WYSIWIG-editing with Cocoon Forms possible?
- Then, how to integrate the data layer (binding)?
I agree that making Cocoon more "dreamweaver"-friendly would give us lots of new friends.
and I don't see why we can't do it right now: all we need is a pipeline component that is capable of understanding a tapestry-like, dreamweaver-friendly syntactic addition to HTML (thru attributes, comments or whatever else).
This component can "augment" the page in a more XML-ish way and from that point on you can still do whatever you want with cocoon, including further site-wide XSLT (could be *very* useful for HTML cleanup and normalization), xinclusion or just serialization if your generated content is good enough (I do that most of the time).
In short, I don't see an architectural problem, just a matter of scratching your itch if you have one ;-)
For the time being I try to find possible alternatives to satisfy the "corporate developer". Not all like/want/buy abstract definitions but want WYSIWIG (dreamweaver-like) development.
-- Reinhard
