<x-flowed>At 22:36 29-11-2000 +0100, you wrote:
>Hello Pedro, Mike
> > I like the idea about separation data and style, but why XML? why use xml
> > when the final client (browser) will see html, and besides, editing a
> how-to
> > in xml?!?! we'd had to have either a standart for ourselves and an editor,
> > or edit the text trought the xml tags.
> >
> > it's static content we are talking about here right?
> >
>Yes, in this case. We only will have the opportunity to use it
>statical i assume.
>
> > please explain that part of the apache cocoon, what is it?
>Cocoon is an "engine that transform xml pages with the help of a
>stylesheet to another format, and can present them.
that's brilliant! how come I never hear of this before?
> It works in
>cooperation with apache or an other server.
>I used it dynamical for a medical informatic project but i proposed
>to use it only to create the html pages local and them put the
>statical created html sites on the web.
>It is however possible to easily create different views on the same
>Data. For example if you have your data for FAQ's in the form
><faq>
><question>what is LEAF </question>
><short_answer>Linux embedded application
>firewall</short_answer>
><detailed_answer> blah blah for 3 pages </detailed_answer>
></faq>
>you can then generate for example the first page with all faqs
>for adding a faq you need only generate another faq in this format,
>it will be automaticall put on the page.
>At the next page you could forexample generate faq + short_answer
>and over a link detailed answer.
>all pages could look the same from design, but you only have to
>generate the design one time.
>Or you can generate a lynx version, a wap version and a "big"
>browser version.
I'm delighted!!!!!! :))))))))))
I have some experience with xml, xsl and xslt, so I'll help anyway I can. I
guess now's the perfect time to lear php3!
since this is a document intensive site and the cocoon engine does all the
xml transformation, we could have a database system that can store all
those xml strings, how about that?
with xml, we can have a page with multiple layouts/xsl!
I can write a win32 program to compose the xml docs, some kind of editor.
by the way I have a redhat server (one without a power transformer!) and a
cable connection, I can host some test site or whatever site, I'm sure
other can too, but I'm just offering mine.
>It was just an idea, i am very enthusiastic about, but the usefullnes
>of this depends heavily on the fact how often you change your page.
>If it is very static, it won't bring much profit.
static or not if you sum all the *different* documents on linuxrouter.org,
rick's, charles's, david's, ray's sites (hope I'm not forgetting anyone
sorry if I am) I think a relational database engine is the answer! as I
believe, this project has a long life time, so it might be a good time to
start centralizing and accounting the available information.
>I like both design you brought. :)
>
>Yes mike that's the one i talked about.
> > does lynx support xml? I doubt it supports xsl.
>it is like this (i hope my ascii grafics are ok
>
>xml info \
> \ HTML version 1
> Cocoon -> HTML version 2 or wml
>xsl stylesheet/
>
>
>Greetings
>
>Eric Wolzak
>
>P.S.
>Pedro , the weather at lissabon is even worse as it is here ;)
it might look so in the weather chart, but I wear a t-shirt all morning and
afternoon :)
pedro
ps: if any time you don't understand my English, misspelled or simple bad
gramar, please correct me.
>_______________________________________________
>Leaf-devel mailing list
>[EMAIL PROTECTED]
>http://lists.sourceforge.net/mailman/listinfo/leaf-devel
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/leaf-devel
</x-flowed>
