Hi Marcus
that's nothing more than our manual besides a different layout. I'd
like to document how studd is being integrated, how stuff works together
and how inheritance trees look like. You saw the gtk tree, wow, cool if
there is only one real tree like inheritance graph. But unfortunatley
Hello Steph,
Saturday, June 10, 2006, 12:58:30 PM, you wrote:
Hi Marcus
that's nothing more than our manual besides a different layout. I'd
like to document how studd is being integrated, how stuff works together
and how inheritance trees look like. You saw the gtk tree, wow, cool if
On Thu, 8 Jun 2006, Andi Gutmans wrote:
Any chance we can get the SPL docs integrated into the PHP manual? I
get questions about it here and there and think that as it's in the
default PHP distro it makes sense to have that as part of the official
PHP manual.
There is no way we can do
Derick Rethans mailto:[EMAIL PROTECTED] wrote on Friday, June 09, 2006
8:25 AM:
On Thu, 8 Jun 2006, Andi Gutmans wrote:
Any chance we can get the SPL docs integrated into the PHP manual? I
get questions about it here and there and think that as it's in the
default PHP distro it makes sense
Hello Andi,
the problem is the non existing OO support in docbook. I had the idea
of eventually using doxygen's xml output and putting that somehow in the
manual. But that's is probably something for livedocs. So lets have
livedocs first. Apart from that nobody hinders the doc team from copying
Yep, it not clear how to document such OO beast in docbook. Also we have few
active persons working in the documentation, that aren't enough to catch up
all the new features, BC breaks, etc.. We probably would need someone to
exclusively work on SPL, which we can't afford ATM.
Nuno
-
Maybe we can get a volunteer to improve the docbook?
At 11:25 PM 6/8/2006, Derick Rethans wrote:
On Thu, 8 Jun 2006, Andi Gutmans wrote:
Any chance we can get the SPL docs integrated into the PHP manual? I
get questions about it here and there and think that as it's in the
default PHP
This is a docbook limitation? Couldn't we still find some standard
way to write it? most of it is manual stuff ala
http://framework.zend.com/manual/en/zend.html?
No?
Andi
At 12:24 AM 6/9/2006, Marcus Boerger wrote:
Hello Andi,
the problem is the non existing OO support in docbook. I had
On 6/9/06, Andi Gutmans [EMAIL PROTECTED] wrote:
Maybe we can get a volunteer to improve the docbook?
We have, http://code.google.com/soc/php/appinfo.html?csaid=1D6D429391DFBA6F
-Hannes
At 11:25 PM 6/8/2006, Derick Rethans wrote:
On Thu, 8 Jun 2006, Andi Gutmans wrote:
Any chance we can
PHP-GTK has been using modified docbook for its stuff...
http://gtk.php.net/manual/en/classtree.php
-Andrei
On Jun 9, 2006, at 6:55 AM, Andi Gutmans wrote:
Maybe we can get a volunteer to improve the docbook?
At 11:25 PM 6/8/2006, Derick Rethans wrote:
On Thu, 8 Jun 2006, Andi Gutmans
The problem is always maintenance.. I've have some knowledge about DSSSL but
none about XSL. In phpdoc we use both, that need to be kept in sync, so
that's always complicated to make changes.
The best option would be to create a work-group to study with docbook
creators the best approaches to
I think that doesn't look too bad. It might not be the Doxygen
output, etc.. but for the PHP manual I think it's quite adequate.
At 09:43 AM 6/9/2006, Andrei Zmievski wrote:
PHP-GTK has been using modified docbook for its stuff...
http://gtk.php.net/manual/en/classtree.php
-Andrei
On Jun 9,
@lists.php.net
Sent: Friday, June 09, 2006 9:51 PM
Subject: Re: [PHP-DEV] SPL docs
The problem is always maintenance.. I've have some knowledge about DSSSL
but none about XSL. In phpdoc we use both, that need to be kept in sync,
so that's always complicated to make changes.
The best option would
]
Cc: [EMAIL PROTECTED]; Derick Rethans [EMAIL PROTECTED];
internals@lists.php.net
Sent: Friday, June 09, 2006 9:51 PM
Subject: Re: [PHP-DEV] SPL docs
The problem is always maintenance.. I've have some knowledge about
DSSSL but none about XSL. In phpdoc we use both, that need to be
kept in sync
Yeah API docs is useful, but still we should have the end-user docs
in the PHP manual. I don't think once comes instead of the other. The
end-user docs is especially useful as people in the community can
give comments, etc...
At 02:52 PM 6/9/2006, Lukas Smith wrote:
Andi Gutmans wrote:
Hey,
Andi Gutmans wrote:
Yeah API docs is useful, but still we should have the end-user docs in
the PHP manual. I don't think once comes instead of the other. The
end-user docs is especially useful as people in the community can give
comments, etc...
Err, you misunderstood what I was trying to
Hello Andi,
that's nothing more than our manual besides a different layout. I'd
like to document how studd is being integrated, how stuff works together
and how inheritance trees look like. You saw the gtk tree, wow, cool if
there is only one real tree like inheritance graph. But unfortunatley
I find the Doxygen-generated SPL docs maze-like and pretty much
impossible to navigate. There is nothing stopping you from maintaining
that separate document, but I'd love to see the useful bits integrated
into the PHP docs. Losing the inheritance graphs doesn't bother me a bit.
-Rasmus
I agree with Rasmus here, there should be at least some level of the docs in
the PHP manual. Its always been considered the one stop shop for reference
for all the beginning coders that I've seen, and is one of the draws for the
language.
Having a seperate set of docs for the more advanced
19 matches
Mail list logo
