"Mehdi Achour" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > I'm 100% with Gabor here. We should only focus on the rendering part > now. The build system will remain the same for the moment. > > Moshe, can you please wait for an answer before commiting ? Next time, > please propose the patch *before* commiting it, it will avoid us to > commit, revert, re-commit and it will be more easy to keep an eyes on > livedocs sources :) > sorry for the wrong commit. the reason i'm not removing the files is just to let someone with filesystem access do the removal on the filesystyem level for not spam the attic.
anyway what you opinion about adding i18n.php file with array that will hold languages charset and direction? > Thank you a lot for you efforts :) > > didou > > > Gabor Hojtsy wrote: > >> Are you planing to use on the old build system forever? Shouldn't livdocs > >> replace completely the old system sometime? > > > > > > Livedocs is currently not aimed at replacing the complete build system. > > Livedocs itself needs command line tools to build the index and > > configure the system. It does not know that much about the built > > documentation, and it does not need to know that much. Livedocs was > > planned to be available for not only phpdoc but for other projects as > > well (smarty, peardoc and php-gtk are the next target beyond phpdoc). > > > > We are not planning to use the current build system forever, we don't > > have plans for the infinite future. Since we are not in a position to > > require PHP 5 to run livedocs (it needs to run on all PHP.net mirror > > sites and client machines as well), we cannot eliminate the need to use > > libxml2 and some command line tools to glue these together. > > > > The configure and make tools in the phpdoc build system do a lot to > > ensure that partial results are cached, and reused as possible. If we > > would employ a dumb PHP based build system, these advantages would be > > lost. There is no PHP based build system yet running with PHP 4.x.x AFAIK. > > > >> also if the answers to those two questions are yes and no, Imho, the > >> multi > >> languages support on the old build is realy creak part (specially in the > >> aspect of not duplication the code and files-structure) and and we sould > >> reduce the old build system relay as much as possible. It's just looks > >> to me > >> stupid giving the new build system the pleasure to extract some bash or > >> whatever old definitions and build new per language php file (keep in > >> mind > >> we need those definitions on runtime, not on configure time) when we > >> can put > >> it in ready to use php file. > > > > > > There is no new build system. The livedocs build system will not work > > without the phpdoc (~ smarty, peardoc, etc) build system behind. It will > > not be able to find the files, generate the entities, etc. > > > > There are really only a few small problems with the build system (if > > any). We have a lot more problems with the presentation and distribution > > system, and livedocs is aimed at solving that. If we concentrate our > > efforts on rewriting the build system from the ground up, then the > > presentation problems will be solved a lot later. Users are not > > interested in how the documentation is built, they are interested in > > using the most up to date and best presentation format available. > > Livedocs is the help to make that possible. > > > > PHPdoc authors are interested in how the build system works, and they > > are interested in using the most developer-friendly system as possible. > > Copy-pasting is not the best known developer-friendly method. > > > > Goba
