Re: [GD-DEVEL] 2.1.0 final

[email protected] (Pierre Joye) Mon, 24 Jun 2013 08:33:57 +0200
Newsgroups php.gd.devel
Message-ID <CAEZPtU7+gVOLpGLUMFQyAhjABg_aPgcUZPwUiXYLNuRNADGN1w@mail.gmail.com>
http://jessevdk.github.io/cldoc/ looks nice and very similar to cxref,
small but functional.

On Mon, Jun 24, 2013 at 8:28 AM, Pierre Joye <[email protected]> wrote:
> hi!
>
> On Mon, Jun 24, 2013 at 6:43 AM, Chris Barker - NOAA Federal
> <[email protected]> wrote:
>> On Sat, Jun 22, 2013 at 9:11 AM, Mike Frysinger <[email protected]> wrote:
>>> On Friday 21 June 2013 17:33:03 Chris Barker - NOAA Federal wrote:
>>>> It would be nice to have the docs in with the source -- I've only been
>>>> able to find an old copy on boutell.com
>>>
>>> which docs ?  the gd repo atm doesn't really contain any at all.
>>
>> exactly.
>>
>>>  do you mean
>>> the index.html that's in the 2.0.35 tarball ?
>>
>> If that's more or less what I find here:
>>
>> http://www.boutell.com/gd/manual2.0.33.html
>>
>> then yes.
>>
>> They could use some cleaning up, but they ar pretty useful none the less.
>
> Having updated documentation is the next top priority. The open
> question is about the tool we could use.
>
> I really don't want to use doxygen, had suffered too much with it on
> other projects ;-). I've played with CxRef
> (http://www.gedanken.demon.co.uk/cxref/) and was quite happy with it.
> However it does not seem to be actively maintained anymore.
>
> Docurium (https://github.com/libgit2/docurium) looks really nice and
> works well with git.
>
> Any other alternatives or suggestions? I can imagine having gd 2.1.1
> with full documentations available if we can agree on which tool to
> use :)
>
> Contributors and helpers welcome!
>
> Cheers,
> --
> Pierre
>
> @pierrejoye |  http://www.libgd.org



-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org