phpwiki-talk

[Phpwiki-talk] Long-term ideas

[Matti A. <ma...@ik...>]

Has there been any discussion whether PhpWiki should be converted to use 
internally an XML-based page format and to render the pages on-screen 
using XSL transforms? That would be great in the sense that after that 
it would be awfully easy to interface PhpWiki with other tools 
(outputting pages in Docbook/LaTeX/WAP/XHTML basic/whatever, parsing the 
pages easily with external tools etc.). I suppose it would also make 
things such as optional Java applet -based wysiwyg editors easier to 
implement.

Apache::AxKit wiki, while very simplistic, has taken this approach. Of 
course, the drawback would be increased reliance on complex external 
libraries, and it would probably require a more or less complete rewrite 
of PhpWiki.

Do you think I'm just blinded by fancy acronyms, or would it make sense?

m.

Re: [Phpwiki-talk] Long-term ideas

[Reini U. <ru...@x-...>]

Matti Airas schrieb:
> Has there been any discussion whether PhpWiki should be converted to use 
> internally an XML-based page format and to render the pages on-screen 
> using XSL transforms? That would be great in the sense that after that 
> it would be awfully easy to interface PhpWiki with other tools 
> (outputting pages in Docbook/LaTeX/WAP/XHTML basic/whatever, parsing the 
> pages easily with external tools etc.). I suppose it would also make 
> things such as optional Java applet -based wysiwyg editors easier to 
> implement.

easier. we use internally the wiki-format, during the output step we use 
jeff's XmlElement library which is able to dump as valid XML or HTML.

e.g. you can save as HTML or XML and convert to other formats externally.


BTW: I recently rewrote jeff's HtmlElement library in a simple and 
reusable manner. just functions, no classes, in a syntax similar to 
perl's CGI (not HTML::Element)

http://xarch.tu-graz.ac.at/home/rurban/software/html-lib.phps
http://xarch.tu-graz.ac.at/home/rurban/software/html-lib.php.gz

for example:
   echo html_tr(html_td(array(colspan=>$colspan),NBSP));
   echo html_tr(array(valign=>"top"),
			 html_td(array(align => "right"),
  html_img(array(src=>"img/icon_ampel_rot.gif",alt => "Fehler", width => 
"20", height => "20")), NBSP, NBSP),
			 html_td(array(colspan => $colspan-1), html_div(array('class' => 
$arr['type']),$msg)));

Re: [Phpwiki-talk] Long-term ideas

[Tony L. <la...@is...>]

On Mon, 16 Dec 2002, Reini Urban wrote:

> easier. we use internally the wiki-format, during the output step we use 
> jeff's XmlElement library which is able to dump as valid XML or HTML.

I hope you put WikiBlog among the long-term ideas. 
Or, if it has already been established, just clearer 
documentation would be sufficient. 

I have been here: 
http://phpwiki.sourceforge.net/demo/en/WikiBlog
and added lib/plugin/Wikiblog and that bit of code in /lib/WikiDB.php .
But I couldn't figure out what else is needed to get that effect. 
Other SubPages code, perhaps? 

Thanks!


-- 
Tony Laszlo
http://www.issho.org/laszlo.html

Re: [Phpwiki-talk] Long-term ideas

[Matti A. <ma...@ik...>]

Reini Urban wrote:

> easier. we use internally the wiki-format, during the output step we use 
> jeff's XmlElement library which is able to dump as valid XML or HTML.
> 
> e.g. you can save as HTML or XML and convert to other formats externally.

Hmm... Is there an XML output format already defined (and implemented)? 
If so, it indeed might be simple enough to access those pages via 
XML-RPC and make a proxy for the portable output formats (I might be 
interested in implementing a WAP or XHTML basic interface so that 
PhpWiki sites could be accessed via new mobile phones)...

m.

Re: [Phpwiki-talk] Long-term ideas

[<la...@us...>]

Openwiki (http://www.openwiki.com/) generates pages in XML and uses XSLT for 
display purposes.

I think there is something to be said for storing pages in a semi-rendered 
format, which could be XML.  That way, a lot of the parsing work is done when 
the page is stored, not when it is retrieved, which would result in faster 
rendering times.


Quoting Matti Airas <ma...@ik...>:

> Has there been any discussion whether PhpWiki should be converted to use
> 
> internally an XML-based page format and to render the pages on-screen 
> using XSL transforms? That would be great in the sense that after that 
> it would be awfully easy to interface PhpWiki with other tools 
> (outputting pages in Docbook/LaTeX/WAP/XHTML basic/whatever, parsing the
> 
> pages easily with external tools etc.). I suppose it would also make 
> things such as optional Java applet -based wysiwyg editors easier to 
> implement.
> 
> Apache::AxKit wiki, while very simplistic, has taken this approach. Of 
> course, the drawback would be increased reliance on complex external 
> libraries, and it would probably require a more or less complete rewrite
> 
> of PhpWiki.
> 
> Do you think I'm just blinded by fancy acronyms, or would it make sense?
> 
> m.
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:
> With Great Power, Comes Great Responsibility 
> Learn to use your power at OSDN's High Performance Computing Channel
> http://hpc.devchannel.org/
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
> 

Re: [Phpwiki-talk] Long-term ideas

[<la...@us...>]

I just found a link that I was looking for -  see http://www.usemod.com/cgi-
bin/mb.pl?WikiXmlDtd

Quoting Matti Airas <ma...@ik...>:

> Has there been any discussion whether PhpWiki should be converted to use
> 
> internally an XML-based page format and to render the pages on-screen 
> using XSL transforms? That would be great in the sense that after that 
> it would be awfully easy to interface PhpWiki with other tools 
> (outputting pages in Docbook/LaTeX/WAP/XHTML basic/whatever, parsing the
> 
> pages easily with external tools etc.). I suppose it would also make 
> things such as optional Java applet -based wysiwyg editors easier to 
> implement.
> 
> Apache::AxKit wiki, while very simplistic, has taken this approach. Of 
> course, the drawback would be increased reliance on complex external 
> libraries, and it would probably require a more or less complete rewrite
> 
> of PhpWiki.
> 
> Do you think I'm just blinded by fancy acronyms, or would it make sense?
> 
> m.
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:
> With Great Power, Comes Great Responsibility 
> Learn to use your power at OSDN's High Performance Computing Channel
> http://hpc.devchannel.org/
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>