Hi Thomas,
On February 16, 2011 02:36:22 pm T. Modes wrote:
> > - The Wiki for developers documentation that is not inside the code, e.g.
> > architecture / design documents; file system layout description, etc.
>
> Here I don't agree.
OK, I understand and won't proceed. I suspect we will have
Hi Thomas
>> - The Wiki for developers documentation that is not inside the code, e.g.
>> architecture / design documents; file system layout description, etc.
>>
> Here I don't agree. The developer documents often refer to classes or
> function. This links are automatically created by doxygen. Bu
Hi Yuv,
> Thank you. I suggest that we adopt a policy of using the following tools in
> the following cases:
> - Doxygen for everything that is *inside" the code, i.e. API documentation.
> - The Hugin website for policy documents (i.e. those that change very seldom).
Agree.
> - The Wiki for dev
On February 15, 2011 12:44:10 pm T. Modes wrote:
> Ok, convinced by majority.
Thank you. I suggest that we adopt a policy of using the following tools in
the following cases:
- Doxygen for everything that is *inside" the code, i.e. API documentation.
- The Hugin website for policy documents (i.e
On 15 Feb., 00:07, Yuval Levy wrote:
> Hi Thomas,
>
> On February 14, 2011 11:37:03 am T. Modes wrote:
>
> > Why did you not extended the existing version?
>
> Short answer: because Doxygen is the wrong place for this kind of document.
>
> I know of very few projects that keep this kind of docum
> Agree. And I vote for the one on the website.
I vote for the one the website too and remove it from Doxygen. I think
that the doxygen inside the source code should contain only code
documentation.
--
You received this message because you are subscribed to the Google Groups
"Hugin and other f
Hi Thomas,
On February 14, 2011 11:37:03 am T. Modes wrote:
> Why did you not extended the existing version?
Short answer: because Doxygen is the wrong place for this kind of document.
I know of very few projects that keep this kind of document in doxygen.
> There should only be one version.
Hi Yuv,
On 14 Feb., 06:23, Yuval Levy wrote:
> Hi Hugin developers,
>
> back in August 2009 we had a discussion about coding style consistency. The
> result of that discussion have been a needle in a haystack on my hard disk.
>
> today I found it, polished it, and published it on the Hugin websi
