:[EMAIL PROTECTED]
Sent: Friday, June 01, 2007 9:31 PM
To: Gwynne Raskind
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] Documenting the Zend2 extension API
part id=internals2
titleInternals2;/title
internals2.intro;
internals2.buildsys.index; !-- configure options
part id=internals2
titleInternals2;/title
internals2.intro;
internals2.buildsys.index; !-- configure options, ext_skel,
config.m4, config.w32, static vs dynamic builds --
internals2.structure.index; !-- ext_skel, module structure,
globals, lifecycle, tests --
Message-
From: Gwynne Raskind [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 29, 2007 11:51 PM
To: internals@lists.php.net
Subject: Re: [PHP-DEV] Documenting the Zend2 extension API
On May 8, 2007, at 2:59 PM, Philip Olson wrote:
Hi all, just wanted to give you a heads-up that I'm still
We use doxygen for the developer portions of our customer facing
manual. The trick is to have it output xml and then massage that to
fit into docbook.
--Wez.
On 4/25/07, Antony Dovgal [EMAIL PROTECTED] wrote:
Doxygen (which seems to be uses by the majority of F/OSS projects) generates
On May 8, 2007, at 2:59 PM, Philip Olson wrote:
Hi all, just wanted to give you a heads-up that I'm still working
on this project; it took me awhile to get the tools properly set
up, but I'm plugging away at DocBook XML now, and I'll have a few
patches to send in soon, I think. Thanks for
On May 5, 2007, at 6:47 PM, Gwynne Raskind wrote:
On Apr 25, 2007, at 6:51 PM, Antony Dovgal wrote:
I've been plugging around writing extensions long enough to have
some idea of the internals; more than once I've answered a
question by digging through the Zend sources for the internals
On Apr 25, 2007, at 6:51 PM, Antony Dovgal wrote:
I've been plugging around writing extensions long enough to have
some idea of the internals; more than once I've answered a
question by digging through the Zend sources for the internals of
some API.
Great!
I'm willing to at least take a
Doxygen (which seems to be uses by the majority of F/OSS projects)
generates completely unreadable docs.
Every time I look into ICU docs (generated by Doxygen) I get lost for 10
minutes trying to find a function _by name_.
Well, in ICU there are two sets of docs - the automatic docs (e.g.
On Thu, 26 Apr 2007, Marcus Boerger wrote:
Hello Antony,
Thursday, April 26, 2007, 12:05:07 AM, you wrote:
On 04/26/2007 01:45 AM, Gwynne Raskind wrote:
Hmm... For some reason I missed that in my searches. That being
said, the existence of one doesn't preclude the writing of another
Hello Antony,
Thursday, April 26, 2007, 12:25:30 AM, you wrote:
On 04/26/2007 02:12 AM, Marcus Boerger wrote:
Doxygen (which seems to be uses by the majority of F/OSS projects)
generates completely unreadable docs.
Every time I look into ICU docs (generated by Doxygen) I get lost for 10
On 04/26/2007 09:47 PM, Marcus Boerger wrote:
Hello Antony,
Thursday, April 26, 2007, 12:25:30 AM, you wrote:
On 04/26/2007 02:12 AM, Marcus Boerger wrote:
Doxygen (which seems to be uses by the majority of F/OSS projects)
generates completely unreadable docs.
Every time I look into ICU docs
Given the recent discussion of the lack of real documentation for the
Zend API, and the endless links provided to various sources of
usually incomplete information, I thought it might be a good idea if
someone wrote an actual book on the subject. I'm interested in taking
that project upon
On Wed, 25 Apr 2007, Gwynne Raskind wrote:
Given the recent discussion of the lack of real documentation for the Zend
API, and the endless links provided to various sources of usually incomplete
information, I thought it might be a good idea if someone wrote an actual book
on the subject. I'm
On Apr 25, 2007, at 3:33 PM, Derick Rethans wrote:
Given the recent discussion of the lack of real documentation for
the Zend
API, and the endless links provided to various sources of usually
incomplete
information, I thought it might be a good idea if someone wrote an
actual book
on the
On 04/26/2007 01:45 AM, Gwynne Raskind wrote:
Hmm... For some reason I missed that in my searches. That being said,
the existence of one doesn't preclude the writing of another :).
Also, it seems the official documentation in the PHP manual could use
some serious updating, which I would
Hello Antony,
Thursday, April 26, 2007, 12:05:07 AM, you wrote:
On 04/26/2007 01:45 AM, Gwynne Raskind wrote:
Hmm... For some reason I missed that in my searches. That being said,
the existence of one doesn't preclude the writing of another :).
Also, it seems the official documentation
On 04/26/2007 02:12 AM, Marcus Boerger wrote:
Doxygen (which seems to be uses by the majority of F/OSS projects)
generates completely unreadable docs.
Every time I look into ICU docs (generated by Doxygen) I get lost for 10
minutes trying to find a function _by name_.
In the same time, other
On Apr 25, 2007, at 6:05 PM, Antony Dovgal wrote:
Hmm... For some reason I missed that in my searches. That being
said, the existence of one doesn't preclude the writing of
another :). Also, it seems the official documentation in the PHP
manual could use some serious updating, which I
On 04/26/2007 02:32 AM, Gwynne Raskind wrote:
I've been plugging around writing extensions long enough to have some
idea of the internals; more than once I've answered a question by
digging through the Zend sources for the internals of some API.
Great!
I'm willing to at least take a
Subject: Re: [PHP-DEV] Documenting the Zend2 extension API
On Apr 25, 2007, at 3:33 PM, Derick Rethans wrote:
Given the recent discussion of the lack of real documentation for the
Zend
API, and the endless links provided to various sources of usually
incomplete
information, I thought it might
] Documenting the Zend2 extension API
On 04/26/2007 02:32 AM, Gwynne Raskind wrote:
I've been plugging around writing extensions long enough to have some
idea of the internals; more than once I've answered a question by
digging through the Zend sources for the internals of some API.
Great!
I'm
21 matches
Mail list logo
