Re: the <acronym> tag, time for a title? (livedocs integration)
| From: | Nuno Lopes | Date: | Tue, 27 Jul 2004 20:02:57 +0000 |
| Subject: | Re: the <acronym> tag, time for a title? (livedocs integration) | ||
| References: | 1 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969362267@lists.php.net to get a copy of this message | ||
> > Note that livedocs core developers do accept patches. Have you seen Ilia
> > accepting the patch from Curt to fix the font sizes on the php.net view?
> > It is just that they have a hard time following the traffic on phpdoc.
> > Ilia himself has a trigger on cvs commit messages with "livedocs" in
> > them to get :)
I've sent two patches to Ilia and to Wez and I've received no answers...
One had a performance boost of about 50% in highlighting PHP (based on Goba
function in php.net)
> > Livedocs needs more testers, and more people willing to put time into
> > it. I never found enough time to help out, but I try to direct everybody
> > who is not satisfied with the lack of insite search, lack of timely
> > manual updates, etc. to help in livedocs development as that is clearly
> > the way to go.
Livedocs still has a main problem: the links.
Livedocs isn't also working well with windows. Latest changes by Wez to make
the paths relatives broke livedocs on windows, because of diffences on
slashes (/ versus \) between phpdoc build system and livedoc's. I've already
reported this problem a while ago, along with some solutions/patches to
solve the problem.
> We need docs.php.net online, and docweb on a reliable, working,
> and maintained server; and in PHP CVS. The current situation there
> looks a bit screwy but I've only been an observer there. I do like
> the idea of a core group starting it out, less noise, but is it ready
> for others now or is the server problem still holding things back?
> Maybe we got a little too aggressive with idealistic ideas and should
> just focus on one thing at a time, like livedocs, I don't know.
Yes, the code needs to be in CVS. It will be soon, althought I thought it
was sooner....
We are having problems with the temp server... so, we really need a
definitive server!
I don't know of what now we are waiting for. I thought Nexen offered a
server, but I've never saw it on-line...
> Once ready for testing (now?), docs.php.net can simply be livedocs like
> it used to be (or a shell of docweb) and we won't "advertise" it. People
> will slowly use it this way and the more people start using it the more
> people will complain and more importantly the more people will fix
> problems and add features. If a major problem exists there we can
> redirect users to php.net/manual/ Also, it should add excitement to
> the docweb project, a project few know even exists right now[1].
The docweb project was largely advertised on all doc mailling lists.
Livedocs is in alpha stage. It has a couple of well know bugs. So, first
let's fix them, and then make it public.
Nuno