> To clear things up once and for all :) Wez started livedocs on his own > machine without any revision control, and then some curious people > peaked in (Derick Ilia and myself).
And me, actually.. I was able to convince Wez lately that livedocs > should be moved to cvs.php.net, now we are waiting to Wez to provide a > tgz of the module, so someone from the system guys can import it into > cvs.php.net Ah, okay, this was the missing information. those who would like to > contribute code will get access (keeping in mind that we would like to > keep it a general tool to be useable for all the PHP subprojects and > others too). Hooray :) cos I got tired of adapting it w/o cvs karma.. it meant re-writing locally every time there was a change in the core version. That's why I lost interest. > Livedocs is still in development, it is very true. But unless we put > effort into development and testing it will not become better. I would > not like to propose it to be used without more advancement and testing... I'm very glad to hear it. <snip> > Hm, I am sure the phpdoc build system would not work with the > configure.in file outside of cygwin, even if the tools are available as > native windows .exe files, since the configure system is tailored for > unix tools... No, we still need cygwin, it's just that xsltproc is available as a cygwin package and I put the stylesheets into cvs.php.net now. Incidentally, cygwin's improved massively over the last couple of years - go for a minimum install, fire up a build and see what's missing, download it, try again & etc. Even over dialup, it doesn't take too long to set this up now, maybe an hour or so. PHP is the only executable we need to add to /bin because we use it for part of the processing (PHP4, but 5 works fine too). > >>Since livedocs will hopefully make most of the current make targets > >>obsolote, the build system will be much smaller, and easier to port to > >>another environment (eg. Phing). We don't have too many 'make' targets here either at present, that's not a big consideration. The bigger issue's whether to keep company with the mothership, and to what extent. > Actually I would not like to wait more, but put effort into making it > working... Since I also work at the PHP websites, and I get more and > more frustrated because of the missing onsite search, I've stopped working on php-gtk-web altogether until our systems difficulties are sorted out. Hopefully with imajes back on the scene this won't take many more weeks. But yes, I know what you're saying. and the ugly HTML > produced by the DSSSL sheets no comment ;) I would like to make livedocs work for the > PHP sites ASAP (with public beta testing before it could replace the > current docs :). ASAP means "in the coming months" :)) Wez, do your stuff! ;) > > Goba > - Steph
