You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Jean Pierre LeJacq <jp...@quoininc.com> on 2004/09/02 12:14:46 UTC
Re: AW: lenya cforms
On Thu, 2 Sep 2004, Rolf Kulemann wrote:
> IMHO XML documents from Lenya's point of view should not contain any
> cforms markup. My idea is to have a doctype, which defines markup like
> <myns:submit-comment someattribslike_title="bla"/> than u need a xslt
> for your doctype which substitutes <myns:submit-comment.../> with the
> appropriate cforms markup and further markup. Then you do the cforms
> transformation.
>
> In other words: The cforms markup is transformed on the basis of
> document and markup semantics, which is not the cforms semantic.
Hmmm, doesn't cforms' separation into form definition and form
template achieve this already?
--
JP
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: AW: lenya cforms
Posted by Torsten Schlabach <TS...@gmx.net>.
>> IMHO XML documents from Lenya's point of view should not contain any
>> cforms markup. My idea is to have a doctype, which defines markup like
>> <myns:submit-comment someattribslike_title="bla"/> than u need a xslt
>> for your doctype which substitutes <myns:submit-comment.../> with the
>> appropriate cforms markup and further markup. Then you do the cforms
>> transformation.
I completely agree. You need to be careful with what editor's you want to
edit your pages later! The solution I was talking about in my other email is
built around that idea.
In fact you need to be careful not to turn your Lenya publication into a
very custom and very weired Cocoon app. This happens very fast if you as the
XML guru are happily hacking at this on the file level. But always think of
your non-XML-aware editors!!!
If you don't have them and just want to use cool XML to hack together your
website you don't need Lenya in my view. In that case you can go straight to
Cocoon.
I was asking for and I am currently working on a sort of "aggregation
template doctype" kind of thing. The fuzzy naming suggests that I am not yet
really done with it, but I am looking for a good solution how to be sure
that editors can edit the text above or below a form for example in Kupu
without destroying the form in the middle! I have some ideas and I will post
them as soon as I have them.
In short words I think the form template (and only the form template) should
be made a doctype that is transformed into xhtml that can then be included
in such a template page.
I think this is just another way of explaining what Rolf has suggested.
Remember this ASCII art - it helped me shape my thinking:
rss document -> rss2xhtml --+
linklist document -> linklist2xhtml --+
gallery document -> gallery2xhtml --+---> page2xhtml.xsl -> Browser
docbook document -> docbook2xhtml --+ (add navigation)
xhtml document -> xhtml2xhtml.xsl --+
Torsten
> On Thu, 2004-09-02 at 12:14, Jean Pierre LeJacq wrote:
> > On Thu, 2 Sep 2004, Rolf Kulemann wrote:
> >
> > > IMHO XML documents from Lenya's point of view should not contain any
> > > cforms markup. My idea is to have a doctype, which defines markup like
> > > <myns:submit-comment someattribslike_title="bla"/> than u need a xslt
> > > for your doctype which substitutes <myns:submit-comment.../> with the
> > > appropriate cforms markup and further markup. Then you do the cforms
> > > transformation.
> > >
> > > In other words: The cforms markup is transformed on the basis of
> > > document and markup semantics, which is not the cforms semantic.
> >
> > Hmmm, doesn't cforms' separation into form definition and form
> > template achieve this already?
>
> Yes, it goes into that direction. But it still uses wi:instance stuff
> iirc all around. But one can use that, but it is still low level
> semantics imho.
>
> So u mean my custom doctype markup needs to be merged with the the wi:
> markup?
>
> --
> Rolf Kulemann
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lenya-user-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: lenya-user-help@cocoon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-user-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-user-help@cocoon.apache.org
Re: AW: lenya cforms
Posted by Rolf Kulemann <ro...@apache.org>.
On Thu, 2004-09-02 at 12:14, Jean Pierre LeJacq wrote:
> On Thu, 2 Sep 2004, Rolf Kulemann wrote:
>
> > IMHO XML documents from Lenya's point of view should not contain any
> > cforms markup. My idea is to have a doctype, which defines markup like
> > <myns:submit-comment someattribslike_title="bla"/> than u need a xslt
> > for your doctype which substitutes <myns:submit-comment.../> with the
> > appropriate cforms markup and further markup. Then you do the cforms
> > transformation.
> >
> > In other words: The cforms markup is transformed on the basis of
> > document and markup semantics, which is not the cforms semantic.
>
> Hmmm, doesn't cforms' separation into form definition and form
> template achieve this already?
Yes, it goes into that direction. But it still uses wi:instance stuff
iirc all around. But one can use that, but it is still low level
semantics imho.
So u mean my custom doctype markup needs to be merged with the the wi:
markup?
--
Rolf Kulemann
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-user-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-user-help@cocoon.apache.org