From: Reini U. <ru...@x-...> - 2005-04-05 05:35:47
|
Hi Lawrence, Lawrence Akka schrieb: > On 4 Apr 2005, at 15:02, Daniel Sutcliffe wrote: ... >> It seems that there's quite a few of us interested in using phpwiki >> within postnuke, and yet all the ports seem pretty abandoned... it >> is good to hear the Reini has done work on making it "native" - I'm >> sure with the obvious interest we can volunteer some time to keep >> this updated with a the current phpwiki once 1.3.11 is stable and >> released. I know I'm willing to give it some time - I ought to at >> least drop my findings into the phpwiki Wiki... > > I am sure that there is scope for making phpwiki amenable to being > incorporated into other software. One thing that I recall thinking > would help a great deal is if the wiki transform engine was more > free-standing so that text could be passed in to a function, wikified, > and returned to the calling application without invoking the whole > phpwiki machinery. This was not to easy last time I looked, which > admittedly was some time ago. I thought about functional interfaces for foreign apps. But in fact phpwiki needs all configs and helpers, so the only entry point is the one we are using now, which is fair enough. Our TransformText() - "the machinery" - depends on most underlying files. The real problem with phpwiki as module is the amount of our global vars and configs which might clash with the other apps. That's why I started to work on phpnuke, postnuke, xoops and gforge modules, to check for possible conflicts. Besides the auth problematic, sharing and overtaking already registered users. So far only $Theme clashed, that's why I renamed it to $WikiTheme. The rest should really go into a global $WikiCfg[] somewhen, but not for 1.3.x, so I thought. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban http://phpwiki.org |