Tony Collen wrote:
Stefano Mazzocchi wrote:
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 ;-)
Hmm, opening my copy of DWMX, there's an absolute *ton* of stuff that could be done. There's a bunch of API reference stuff in the Help. There are APIs for: File I/O, HTTP, Database integration, JavaBeans, and Source Control Integration.
There's a bunch of documentation for data sources, which would probably allow us to setup some sort of CForms binding with some hacking.
Also taking a quick glance, there's a bunch of GUI stuff, which would probably allow us to graphically build forms.
Like you said, Stefano, it's all possible, it's just a matter of someone taking the time to get really deeply into it an figure out how to do it.
Thanks for the hint.
Do you know whether it is possible to create your own elements for WYSIWIG development or a way to use _nested_ templates in Dreamweaver?
-- Reinhard
