Putting streams stuff into the chapters folder was a mistake in the
first place, since 'chapters' is depreciated, it is not supposed to have
new files, and stuff is moved out of it to more sensible places (eg.
install)...
Is that the only thing we have to decide? If yes, then we need to:
a) mov
On Wed, 13 Oct 2004, Nuno Lopes wrote:
> > What about having sub-chapters for the API docs for each PHP
> > version. For example there are still PHP 3 developer docs in
> > the manual, the Zend API Docs are for PHP 4, and we lack PHP
> > 5 information. This is all different so this is something to
What about having sub-chapters for the API docs for each PHP
version. For example there are still PHP 3 developer docs in
the manual, the Zend API Docs are for PHP 4, and we lack PHP
5 information. This is all different so this is something to
think about.
We first need to know if there are many AP
> >> The chapters folder is silly. There is no such thing in the manual we
> >> call chapters. We can have an en/developers/ folder for example, where we
> >> put the developers docs (zend and streams for now).
> >>
> >> Goba
> >
> > We have at the moment: PHP API: Interfaces for extension writer
The chapters folder is silly. There is no such thing in the manual we
call chapters. We can have an en/developers/ folder for example, where we
put the developers docs (zend and streams for now).
Goba
We have at the moment: PHP API: Interfaces for extension writers
(http://livedocs.homelinux.com
The chapters folder is silly. There is no such thing in the manual we call
chapters. We can have an en/developers/ folder for example, where we put
the developers docs (zend and streams for now).
Goba
We have at the moment: PHP API: Interfaces for extension writers
(http://livedocs.homelinux.com
I propose moving the Zend API docs to phpdoc/en/zendapi, but we need to
make up a good folder structure. We need the XML files, but not simpler
then Extending_Zend_xml, and we also need the figures and source
examples in some sensible folder structure. I also don't know whether it
would be
On Tue, 12 Oct 2004, Aidan Lister wrote:
> > I propose moving the Zend API docs to phpdoc/en/zendapi, but we need to
> > make up a good folder structure. We need the XML files, but not simpler
> > then Extending_Zend_xml, and we also need the figures and source
> > examples in some sensible fo
> I propose moving the Zend API docs to phpdoc/en/zendapi, but we need to
> make up a good folder structure. We need the XML files, but not simpler
> then Extending_Zend_xml, and we also need the figures and source
> examples in some sensible folder structure. I also don't know whether it
>
> > My personal opinion: I think it's great to have these zend docs
> > available at phpdoc. Since the manual is at first glance a manual for
> > users, and already very large (and will grow in future) I hope this
> > will _NOT_ become a part of the manual. Providing it as seperate
> > "developer
Philip Olson wrote:
>
> > I just talked to Hartmut at the phpconf in Frankfurt and there were
> > ideas of moving it to phpdoc and also to make it up2date :-)
> > ...I though don't want talk for anyone. So I'll wait and see what he
> > has to say this "progress" now :-)
>
> Sounds good. Here
> I just talked to Hartmut at the phpconf in Frankfurt and there were
> ideas of moving it to phpdoc and also to make it up2date :-)
> ...I though don't want talk for anyone. So I'll wait and see what he
> has to say this "progress" now :-)
Sounds good. Here are a couple initial options that co
James Cox wrote:
>
> I'm guessing that much could be out of date, however that would be one of
> the core things of getting it into the hands of the phpdoc team. :)
>
> James
I just talked to Hartmut at the phpconf in Frankfurt and there were
ideas of moving it to phpdoc and also to make it u
o: James Cox
> Cc: phpdoc
> Subject: Re: [PHP-DOC] RE: Zend API documentation.
>
>
> James Cox wrote:
> >
> > I spoke to Zeev in IRC shortly, and he has given me permission
> to move the
> > Zend API documentation into the phpdoc tree. I checked it out a
> sho
Hi,
On Wed, 2 Jan 2002 23:39:37 +0100
Friedhelm Betz <[EMAIL PROTECTED]> wrote:
> My personal opinion: I think it's great to have these zend docs
> available at phpdoc. Since the manual is at first glance a manual for
> users, and already very large (and will grow in future) I hope this
> will _NO
?
James
> -Original Message-
> From: Friedhelm Betz [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 02, 2002 10:40 PM
> To: Jan Lehnardt
> Cc: James Cox; [EMAIL PROTECTED]
> Subject: Re: [PHP-DOC] RE: Zend API documentation.
>
>
> Hi
>
> >> I am not goin
Hi
>> I am not going to commit this just yet -- i wanted to get any comments
>> first, since i'm not an old pro at phpdoc yet - so i want to check
>> everything out first.
> I am no "old pro" either, but I think is is great to have the API docs
> accessable for phpdoc people. perhaps they will ge
James Cox wrote:
>
> I spoke to Zeev in IRC shortly, and he has given me permission to move the
> Zend API documentation into the phpdoc tree. I checked it out a short while
> ago, and am going through cleaning it up to phpdoc style.
>
> I am not going to commit this just yet -- i wanted to get
Hi,
On Wed, 2 Jan 2002 22:14:30 -
"James Cox" <[EMAIL PROTECTED]> wrote:
> I am not going to commit this just yet -- i wanted to get any comments
> first, since i'm not an old pro at phpdoc yet - so i want to check
> everything out first.
I am no "old pro" either, but I think is is great to h
I spoke to Zeev in IRC shortly, and he has given me permission to move the
Zend API documentation into the phpdoc tree. I checked it out a short while
ago, and am going through cleaning it up to phpdoc style.
I am not going to commit this just yet -- i wanted to get any comments
first, since i'm
20 matches
Mail list logo
