You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Karri Niemelä <Ka...@eniro.com> on 2003/05/26 13:47:36 UTC
Best practise for wml/xhtml site
I'm planning a site, where content is either displayed as wml or xhtml. By using DELI I can get the needed info about clients, so the formatting is done right (meaning that other devices can accept larger pictures etcetc)
Now, what I was thinking is that what would be the best way to actually present the actual content (xml)?
I mean I could have something like:
<page>
<link to="somewhere.org"></link>
</page>
or similar, and then transform that by using the stylesheets to either wml or xhtml.. Or should I perhaps just use xhtml as basis, and then convert that to wml when needed?
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
Re: Best practise for wml/xhtml site
Posted by Torsten Knodt <to...@datas-world.de>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 27 May 2003 13:37, Bruno Dumon wrote:
> Have a look at http://xml.apache.org/forrest/cap.html
Great. What about having this in cocoon, instead of in forrest?
Regards
Torsten
- --
Domain in provider transition, hope for smoothness. Planed date is 1.7.2003.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+02GnvxZktkzSmiwRAj0WAJ0VNuVfnpdMf9xES02szzMWU/0POgCfSE38
1IfvNLid1VBNseyLu5Rb83s=
=7Sq3
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
Re: Best practise for wml/xhtml site
Posted by Bruno Dumon <br...@outerthought.org>.
On Tue, 2003-05-27 at 13:20, Torsten Knodt wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> > I had a similar problem some time ago. Actually, using xhtml as a basis
> > solves most problems.
> > What I found trick, is to find a good way to describe forms. If I recall
> > correctly, in wml the wml-cards and variables have to be used, which is
> > a bit more complicated than html-forms. Thats why I found it easier to
> > construct my own xml markup. If there's a nice way to do this with
> > xhtml, tell me:-) .
> That's what I also do.
> When I have some new form of information to display, I look at my existing
> markup. Sometimes I refactor what I have, sometimes I do something new. I
> think this is the right way of using cocoon and xml. The navigation part and
> others are always the same. Only bad is, that you can't select pipeline
> fragments by the current doctype.
Have a look at http://xml.apache.org/forrest/cap.html
--
Bruno Dumon http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org bruno@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
Re: Best practise for wml/xhtml site
Posted by Torsten Knodt <to...@datas-world.de>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> I had a similar problem some time ago. Actually, using xhtml as a basis
> solves most problems.
> What I found trick, is to find a good way to describe forms. If I recall
> correctly, in wml the wml-cards and variables have to be used, which is
> a bit more complicated than html-forms. Thats why I found it easier to
> construct my own xml markup. If there's a nice way to do this with
> xhtml, tell me:-) .
That's what I also do.
When I have some new form of information to display, I look at my existing
markup. Sometimes I refactor what I have, sometimes I do something new. I
think this is the right way of using cocoon and xml. The navigation part and
others are always the same. Only bad is, that you can't select pipeline
fragments by the current doctype.
Regards
Torsten
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+00n+vxZktkzSmiwRApQ7AKCH0ZKwqDZIJCGZpElKIvDnWQwFpACfUqtd
e5nXbJzlY+qp1tfwOWjaXF0=
=iwku
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
Re: Best practise for wml/xhtml site
Posted by Joel Greenyer <jg...@s-und-n.de>.
Hi Karri,
I had a similar problem some time ago. Actually, using xhtml as a basis
solves most problems.
What I found trick, is to find a good way to describe forms. If I recall
correctly, in wml the wml-cards and variables have to be used, which is
a bit more complicated than html-forms. Thats why I found it easier to
construct my own xml markup. If there's a nice way to do this with
xhtml, tell me:-) .
Joel
Karri Niemelä wrote:
>I'm planning a site, where content is either displayed as wml or xhtml. By using DELI I can get the needed info about clients, so the formatting is done right (meaning that other devices can accept larger pictures etcetc)
>
>Now, what I was thinking is that what would be the best way to actually present the actual content (xml)?
>
>I mean I could have something like:
>
><page>
>
> <link to="somewhere.org"></link>
>
></page>
>
>or similar, and then transform that by using the stylesheets to either wml or xhtml.. Or should I perhaps just use xhtml as basis, and then convert that to wml when needed?
>
>
>
>
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
>For additional commands, e-mail: cocoon-users-help@xml.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
AW: Best practise for wml/xhtml site
Posted by Marco Rolappe <m_...@web.de>.
hi karri,
it depends on the content to be delivered. for special content you might
want to define your own markup.
if it's just about generic page markup you might want to choose something
like xhtml basic. then it should be relatively easy to transform to wml
xhtml mp, xhtml, etc.
> -----Ursprüngliche Nachricht-----
> Von: cocoon-users-return-51082-m_rolappe=web.de@xml.apache.org
> [mailto:cocoon-users-return-51082-m_rolappe=web.de@xml.apache.org]Im
> Auftrag von Karri Niemelä
> Gesendet: Montag, 26. Mai 2003 13:48
> An: cocoon-users@xml.apache.org
> Betreff: Best practise for wml/xhtml site
>
>
> I'm planning a site, where content is either displayed as wml or
> xhtml. By using DELI I can get the needed info about clients, so
> the formatting is done right (meaning that other devices can
> accept larger pictures etcetc)
>
> Now, what I was thinking is that what would be the best way to
> actually present the actual content (xml)?
>
> I mean I could have something like:
>
> <page>
>
> <link to="somewhere.org"></link>
>
> </page>
>
> or similar, and then transform that by using the stylesheets to
> either wml or xhtml.. Or should I perhaps just use xhtml as
> basis, and then convert that to wml when needed?
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org