On Fri, 30 Jul 2004, Philip Olson wrote:
> Here are some questions/concerns about having all PECL docs
> inside of phpdoc:
>
> Builds:
> Will all or just bundled PECL docs be in phpdoc manual builds?
All.
> Meaning, will a separate PECL manual ever exist?
No
> As PECL grows
> the manual will g
Downloads should be smaller somehow like only include bundled
extensions.
What about building two manual versions - one with PECL and one without?
IMHO it's not necessary nowadays as there are only a few PECL extensions
documented but will be more important when the majority of 314
extensions (inst
Philip Olson wrote:
> Downloads should be smaller somehow like only include bundled
> extensions.
What about building two manual versions - one with PECL and one without?
IMHO it's not necessary nowadays as there are only a few PECL extensions
documented but will be more important when the majorit
I can take care of the move and polish the files for phpdoc after we made
a decision how to handle the move.
What should be decided on. What are the questions?
Not really questions. But we/I should inform the pear doc people ( cc'ed) and
maintainers about the move.
apd (last change 2 months, 1 we
I didn't know you were expecting me to handle the win32 installation...
I remember you offered to continue work on the Windows part after you
get back from your deserved holiday :)
Goba
On Sunday 01 August 2004 13:21, Gabor Hojtsy wrote:
> > I just run Hartmuts split script (/scripts/reference-split.php) on PECL
> > extension in peardoc.
> > As Hartmuts script is a bit dated, the structure of the files does not
> > fit in the current phpdoc style (configure.xml, constants.xml etc.
> >>decision how to handle the move.
> >
> > Thanks! I can also help you, but commit the files first :)
> >
> > Nuno
>
> Nuno, Nuno, please work on the windows install stuff first and as soon
> as possible. The other Windows server instructions will be based on the
> general Windows suggestions (Sa
I just run Hartmuts split script (/scripts/reference-split.php) on PECL
extension in peardoc.
As Hartmuts script is a bit dated, the structure of the files does not fit in
the current phpdoc style (configure.xml, constants.xml etc.) and the id's and
filenames are with leading pecl., which proba
decision how to handle the move.
Thanks! I can also help you, but commit the files first :)
Nuno
Nuno, Nuno, please work on the windows install stuff first and as soon
as possible. The other Windows server instructions will be based on the
general Windows suggestions (Sambar server specifically :
> I just run Hartmuts split script (/scripts/reference-split.php) on PECL
> extension in peardoc.
> As Hartmuts script is a bit dated, the structure of the files does not fit
in
> the current phpdoc style (configure.xml, constants.xml etc.) and the id's
and
> filenames are with leading pecl., which
On Friday 30 July 2004 23:14, Gabor Hojtsy wrote:
[...]
>
> > Doc moves:
> > When (or if) will the Hartmut split script be run on all PECL
> > extensions currently in peardoc?
> > Ref: http://marc.theaimsgroup.com/?l=phpdoc&m=107374866303330
>
> Anytime someone sits down and does it :) It is a TO
I'm more referring to the future than today as at somepoint every
PECL extension will have documentation. I'll stop worrying
about it then as I most likely won't be downloading or building
downloads for the PHP manual :)
The upcoming index format looks nice, and intuitive; and will
indeed help
I'm more referring to the future than today as at somepoint every
PECL extension will have documentation. I'll stop worrying
about it then as I most likely won't be downloading or building
downloads for the PHP manual :)
The upcoming index format looks nice, and intuitive; and will
indeed help
There is very limited documentation for PECL extensions currently as far
as I see. So I am not that much worried. We need to implement the
extension categorization system (phpdoc/RFC/manual.xml) either with that
markup or a different one, so the extensions will be easier to locate in
the manual
> > Builds:
> > Will all or just bundled PECL docs be in phpdoc manual builds?
> > Meaning, will a separate PECL manual ever exist? As PECL grows
> > the manual will grow and like we discussed having a separate
> > developers manual this is a *similar* issue. PECL is going to
> > be huge one day
Builds:
Will all or just bundled PECL docs be in phpdoc manual builds?
Meaning, will a separate PECL manual ever exist? As PECL grows
the manual will grow and like we discussed having a separate
developers manual this is a *similar* issue. PECL is going to
be huge one day and contain many special
Here are some questions/concerns about having all PECL docs
inside of phpdoc:
Builds:
Will all or just bundled PECL docs be in phpdoc manual builds?
Meaning, will a separate PECL manual ever exist? As PECL grows
the manual will grow and like we discussed having a separate
developers manual this i
17 matches
Mail list logo
