doxygen-users

RE: [Doxygen-users] MSDN Style

[Freudenberg, T. <tho...@cy...>]

I would like to see this as well. The MSDN style is really cool.

BTW, I am writing a small tool to integrate the help generated
by doxygen into VS.NET. It looks cool, but it is still in development.

Regards
Thomas


> -----Original Message-----
> From: dox...@li... 
> Sent: Thursday, 08 November, 2001 14:37
> To: dox...@li...
> Subject: [Doxygen-users] MSDN Style
> 
> 
> Hello all,
> 
>   Has the MSDN style been merged into the code base in CVS 
> yet? We use that style for all of our auto-generated 
> documentation now, but I would prefer to move to a more 
> recent release than 1.2.6. I have been monitoring the recent 
> change logs, but perhaps I overlooked its mention.
> 
> thank you,
> christian
> 
> PS. For all those who replied to my "Comment Folding" query, 
> whoops! I added the ! token to the comment and it worked like 
> a charm. Thanks very much too all.

RE: [Doxygen-users] MSDN Style

[Prikryl,Petr <PRI...@sk...>]

Hi,

Dimitri wrote:
> On Thu, Nov 08, 2001 at 08:25:21AM -0500, Christian Ratliff wrote:
> > [...]
> >   Has the MSDN style been merged into the code base in CVS yet? We use
that
> > style for all of our auto-generated documentation now, but I would
prefer to
> > move to a more recent release than 1.2.6. I have been monitoring the
recent
> > change logs, but perhaps I overlooked its mention.
> 
> I'm still investigating the impact of Alexandr Chelpanov's patch. 
> It is quite huge, still has rough edges, and introduces a lot of
conditional 
> code (mostly only for html, and even some IE specific stuff), so from a 
> test/maintenance point of view I am not overly enthousiastic yet.

In my opinion, MSDN Style will always be IE specific, and 
it will probably be focused mainly on HTML.  If MSDN Style 
were to be merged into the official doxygen, wouldn't
it be easier to introduce it via another, MSDN-specific 
HTML-generator?  I think that this way it could be separated
from the rest of doxygen, and it could possibly be conditionally 
excluded during compilation for the environment where MSDN Style
does not make sense.  

Microsoft likes to make changes and it does not like to follow
standards, sometimes.  Too tight integration of MSDN Style 
could spoil the doxygen core later.

Regards,
  Petr


-- 
Petr Prikryl, SKIL, spol. s r.o., pri...@sk...

Re: [Doxygen-users] MSDN Style

[<cy...@so...>]

> Microsoft likes to make changes and it does not like to follow
> standards, sometimes.  Too tight integration of MSDN Style
> could spoil the doxygen core later.

What constitutes "MSDN Style" ? Is it copying their internal structure, or
emulating their aspect (which I also find very clean and neat) ?

If the latter, I fail to see what justifies IE-specific hacks, or what would
make doxygen a hostage of MSDN's own evolutions. I, for one, would love to
see an MSDN-looking HTML generator, which would not tie one to CHM
generation (for distributing a released documentation CHM makes sense; but
does it really, for documentation which is updated at every CVS commit ?)

    -- Cyrille

RE: [Doxygen-users] MSDN Style

[Morgenthaler, G. <g.m...@vi...>]

>> Has the MSDN style been merged into the code base in CVS yet?
> I'm still investigating the impact of Alexandr Chelpanov's patch.=20
> It is quite huge, still has rough edges, and introduces a lot=20
> of conditional code (mostly only for html, and even some IE
> specific stuff), so from a test/maintenance point of view I am
> not overly enthousiastic yet.

First I must admit that I haven't seen this MSDN style nor do I know
how the patch looks/works, BUT as long as introducing a new style means
changing the "code base" I would suggest NOT to integrate it.

IMHO styles should be added thru some abstraction layer/interface.
XML based or whatever.

I would suggest that Dimitri concentrates on the "parser engine" and the
"style interface hooks". People that want styles could invest their time
into writing code for that interface instead of writing patches for one
specific style.

Sorry if this spoils the fun for some people and YES I hate Micro$oft
(if that matters ;-)

Regards,

Germar

RE: [Doxygen-users] MSDN Style

[Christian R. <cra...@de...>]

Dimitri,

  What can I do to help get this patch in? If it is through some "style
interface hook" mechanism, which Germar mentions, I am glad to offer
whatever assistance I can.
  As for Germar's political perspective, whatever! We are a Microsoft shop,
and right now I just want to convince people to start auto generating
documentation. The MSDN-style is my best chance to do that, since we are all
familiar with that format.

christian

+-----+
Christian Ratliff <cra...@de...>
Sr. Technology Architect
Core Libraries Group, DeLorme
"This is the very perfection of man, 
  to find out his own imperfections" -  St. Augustine




-----Original Message-----
From: Dimitri van Heesch [mailto:di...@st...] 
Sent: Thursday, November 08, 2001 4:25 PM
To: dox...@li...
Subject: Re: [Doxygen-users] MSDN Style


On Thu, Nov 08, 2001 at 08:25:21AM -0500, Christian Ratliff wrote:
> Hello all,
> 
>   Has the MSDN style been merged into the code base in CVS yet? We use 
> that style for all of our auto-generated documentation now, but I 
> would prefer to move to a more recent release than 1.2.6. I have been 
> monitoring the recent change logs, but perhaps I overlooked its 
> mention.
> 

I'm still investigating the impact of Alexandr Chelpanov's patch. 
It is quite huge, still has rough edges, and introduces a lot of conditional

code (mostly only for html, and even some IE specific stuff), so from a 
test/maintenance point of view I am not overly enthousiastic yet.

From a user point of view I can understand the MSDN style feature is nice 
though.

Regards,
  Dimitri


_______________________________________________
Doxygen-users mailing list
Dox...@li...
https://lists.sourceforge.net/lists/listinfo/doxygen-users

RE: [Doxygen-users] MSDN Style

[Wagner, V. <VW...@se...>]

Poor management decisions on the part of  your company is no reason to risk
breaking what is a GREAT tool for the rest of us.  If you're so proud of
being a "Microsoft shop" ask THEN for THEIR automatic documentation tool.

-----Original Message-----
From: Christian Ratliff [mailto:cra...@de...]
Sent: Friday, 2001 November 09 06:05
To: 'dox...@li...'
Subject: RE: [Doxygen-users] MSDN Style


Dimitri,

  What can I do to help get this patch in? If it is through some "style
interface hook" mechanism, which Germar mentions, I am glad to offer
whatever assistance I can.
  As for Germar's political perspective, whatever! We are a Microsoft shop,
and right now I just want to convince people to start auto generating
documentation. The MSDN-style is my best chance to do that, since we are all
familiar with that format.

christian

+-----+
Christian Ratliff <cra...@de...>
Sr. Technology Architect
Core Libraries Group, DeLorme
"This is the very perfection of man, 
  to find out his own imperfections" -  St. Augustine




-----Original Message-----
From: Dimitri van Heesch [mailto:di...@st...] 
Sent: Thursday, November 08, 2001 4:25 PM
To: dox...@li...
Subject: Re: [Doxygen-users] MSDN Style


On Thu, Nov 08, 2001 at 08:25:21AM -0500, Christian Ratliff wrote:
> Hello all,
> 
>   Has the MSDN style been merged into the code base in CVS yet? We use 
> that style for all of our auto-generated documentation now, but I 
> would prefer to move to a more recent release than 1.2.6. I have been 
> monitoring the recent change logs, but perhaps I overlooked its 
> mention.
> 

I'm still investigating the impact of Alexandr Chelpanov's patch. 
It is quite huge, still has rough edges, and introduces a lot of conditional

code (mostly only for html, and even some IE specific stuff), so from a 
test/maintenance point of view I am not overly enthousiastic yet.

From a user point of view I can understand the MSDN style feature is nice 
though.

Regards,
  Dimitri


_______________________________________________
Doxygen-users mailing list
Dox...@li...
https://lists.sourceforge.net/lists/listinfo/doxygen-users

_______________________________________________
Doxygen-users mailing list
Dox...@li...
https://lists.sourceforge.net/lists/listinfo/doxygen-users

RE: [Doxygen-users] MSDN Style

[Sten D. <sd...@ne...>]

This might be a little out of thread, but I don't think MSDN-look-and-feel
is going to make the difference as to '..to convince people..'.
Since it might look allright - but it isn't a real Micro$oft-tool, hence
they won't trust doxygen anyway.

They either just love it or hate it... no matter what layout is used - just
my humble experince ;-)

Personally I think either layout is nice.

greets

sten

>   As for Germar's political perspective, whatever! We are a
> Microsoft shop,
> and right now I just want to convince people to start auto generating
> documentation. The MSDN-style is my best chance to do that,
> since we are all
> familiar with that format.


> -----Original Message-----
> From: dox...@li...
> [mailto:dox...@li...]On Behalf Of Wagner,
> Victor
> Sent: 09 November 2001 14:48
> To: 'Christian Ratliff'; 'dox...@li...'
> Subject: RE: [Doxygen-users] MSDN Style
>
>
> Poor management decisions on the part of  your company is no
> reason to risk
> breaking what is a GREAT tool for the rest of us.  If you're
> so proud of
> being a "Microsoft shop" ask THEN for THEIR automatic
> documentation tool.
>
> -----Original Message-----
> From: Christian Ratliff [mailto:cra...@de...]
> Sent: Friday, 2001 November 09 06:05
> To: 'dox...@li...'
> Subject: RE: [Doxygen-users] MSDN Style
>
>
> Dimitri,
>
>   What can I do to help get this patch in? If it is through
> some "style
> interface hook" mechanism, which Germar mentions, I am glad to offer
> whatever assistance I can.
>   As for Germar's political perspective, whatever! We are a
> Microsoft shop,
> and right now I just want to convince people to start auto generating
> documentation. The MSDN-style is my best chance to do that,
> since we are all
> familiar with that format.
>
> christian
>
> +-----+
> Christian Ratliff <cra...@de...>
> Sr. Technology Architect
> Core Libraries Group, DeLorme
> "This is the very perfection of man,
>   to find out his own imperfections" -  St. Augustine
>
>
>
>
> -----Original Message-----
> From: Dimitri van Heesch [mailto:di...@st...]
> Sent: Thursday, November 08, 2001 4:25 PM
> To: dox...@li...
> Subject: Re: [Doxygen-users] MSDN Style
>
>
> On Thu, Nov 08, 2001 at 08:25:21AM -0500, Christian Ratliff wrote:
> > Hello all,
> >
> >   Has the MSDN style been merged into the code base in CVS
> yet? We use
> > that style for all of our auto-generated documentation now, but I
> > would prefer to move to a more recent release than 1.2.6. I
> have been
> > monitoring the recent change logs, but perhaps I overlooked its
> > mention.
> >
>
> I'm still investigating the impact of Alexandr Chelpanov's patch.
> It is quite huge, still has rough edges, and introduces a lot
> of conditional
>
> code (mostly only for html, and even some IE specific stuff),
> so from a
> test/maintenance point of view I am not overly enthousiastic yet.
>
> >From a user point of view I can understand the MSDN style
> feature is nice
> though.
>
> Regards,
>   Dimitri
>
>
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

RE: [Doxygen-users] MSDN Style

[Adam T. <ad...@fi...>]

For my two cents, I certainly see value in the MSDN look.  The compnay I
work for has adopted Doxygen as its documentation standard.  It certainly
would be nice if I could convince them to use the DevStudio help integrator:
I'm lazy and F1 on internal classes and functions would be nice.  MSDN look
would go a long way towards that goal.  The main problem I've have with
doxygen and CHM, is that the index doesn't quite seem right.  Maybe its just
me, but in my index, I get: Classname, with a subitem of the destructor, and
it was subitems of the rest of the functions.  Has anyone else seen that?

Adam

> -----Original Message-----
> From:	Sten Darre [SMTP:sd...@ne...]
> Sent:	Friday, November 09, 2001 8:47 AM
> To:	dox...@li...
> Subject:	RE: [Doxygen-users] MSDN Style
> 
> This might be a little out of thread, but I don't think MSDN-look-and-feel
> is going to make the difference as to '..to convince people..'.
> Since it might look allright - but it isn't a real Micro$oft-tool, hence
> they won't trust doxygen anyway.
> 
> They either just love it or hate it... no matter what layout is used -
> just
> my humble experince ;-)
> 
> Personally I think either layout is nice.
> 
> greets
> 
> sten
> 
> >   As for Germar's political perspective, whatever! We are a
> > Microsoft shop,
> > and right now I just want to convince people to start auto generating
> > documentation. The MSDN-style is my best chance to do that,
> > since we are all
> > familiar with that format.
> 
> 
> > -----Original Message-----
> > From: dox...@li...
> > [mailto:dox...@li...]On Behalf Of Wagner,
> > Victor
> > Sent: 09 November 2001 14:48
> > To: 'Christian Ratliff'; 'dox...@li...'
> > Subject: RE: [Doxygen-users] MSDN Style
> >
> >
> > Poor management decisions on the part of  your company is no
> > reason to risk
> > breaking what is a GREAT tool for the rest of us.  If you're
> > so proud of
> > being a "Microsoft shop" ask THEN for THEIR automatic
> > documentation tool.
> >
> > -----Original Message-----
> > From: Christian Ratliff [mailto:cra...@de...]
> > Sent: Friday, 2001 November 09 06:05
> > To: 'dox...@li...'
> > Subject: RE: [Doxygen-users] MSDN Style
> >
> >
> > Dimitri,
> >
> >   What can I do to help get this patch in? If it is through
> > some "style
> > interface hook" mechanism, which Germar mentions, I am glad to offer
> > whatever assistance I can.
> >   As for Germar's political perspective, whatever! We are a
> > Microsoft shop,
> > and right now I just want to convince people to start auto generating
> > documentation. The MSDN-style is my best chance to do that,
> > since we are all
> > familiar with that format.
> >
> > christian
> >
> > +-----+
> > Christian Ratliff <cra...@de...>
> > Sr. Technology Architect
> > Core Libraries Group, DeLorme
> > "This is the very perfection of man,
> >   to find out his own imperfections" -  St. Augustine
> >
> >
> >
> >
> > -----Original Message-----
> > From: Dimitri van Heesch [mailto:di...@st...]
> > Sent: Thursday, November 08, 2001 4:25 PM
> > To: dox...@li...
> > Subject: Re: [Doxygen-users] MSDN Style
> >
> >
> > On Thu, Nov 08, 2001 at 08:25:21AM -0500, Christian Ratliff wrote:
> > > Hello all,
> > >
> > >   Has the MSDN style been merged into the code base in CVS
> > yet? We use
> > > that style for all of our auto-generated documentation now, but I
> > > would prefer to move to a more recent release than 1.2.6. I
> > have been
> > > monitoring the recent change logs, but perhaps I overlooked its
> > > mention.
> > >
> >
> > I'm still investigating the impact of Alexandr Chelpanov's patch.
> > It is quite huge, still has rough edges, and introduces a lot
> > of conditional
> >
> > code (mostly only for html, and even some IE specific stuff),
> > so from a
> > test/maintenance point of view I am not overly enthousiastic yet.
> >
> > >From a user point of view I can understand the MSDN style
> > feature is nice
> > though.
> >
> > Regards,
> >   Dimitri
> >
> >
> > _______________________________________________
> > Doxygen-users mailing list
> > Dox...@li...
> > https://lists.sourceforge.net/lists/listinfo/doxygen-users
> >
> > _______________________________________________
> > Doxygen-users mailing list
> > Dox...@li...
> > https://lists.sourceforge.net/lists/listinfo/doxygen-users
> >
> > _______________________________________________
> > Doxygen-users mailing list
> > Dox...@li...
> > https://lists.sourceforge.net/lists/listinfo/doxygen-users
> >
> 
> 
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

RE: [Doxygen-users] MSDN Style

[Sten D. <sd...@ne...>]

well, ...

> I'm lazy and F1 on internal classes and functions would be nice.

...I'm lazy too, so I've also used MSDNIntegrator to get doxygen generated
docs into MSDN.

> The main problem I've have with
> doxygen and CHM, is that the index doesn't quite seem right.

Mine works fine - and the above illustrates the point or concern: Getting
MSDN looks may spin off 'funny' errors in doxygen, and that does not
convince anybody - it just ruins a good tool, even for those *not* living in
the M$-world.
I *do* program on Windows and live in that world, but I don't need it to
look like Microsoft if it dosn'e serve a distint purpose ?! - likewise we
use make-systems and not 'F7' from DevStudio, because it make us happy, so
if '..to convince..' is the *only* reason for MSDN-looks, I see a buggy
future for doxygen with little to gain otherwise (no new features of
doxygen).

My primary focus is the documentation of the source and one's
develop-environment - *not* the looks of the font-size !! (go on - flame me
;-)

sten

> -----Original Message-----
> From: dox...@li...
> [mailto:dox...@li...]On Behalf Of Adam
> Tegen
> Sent: 09 November 2001 16:25
> To: dox...@li...
> Subject: RE: [Doxygen-users] MSDN Style
>
>
> For my two cents, I certainly see value in the MSDN look.
> The compnay I
> work for has adopted Doxygen as its documentation standard.
> It certainly
> would be nice if I could convince them to use the DevStudio
> help integrator:
> I'm lazy and F1 on internal classes and functions would be
> nice.  MSDN look
> would go a long way towards that goal.  The main problem I've
> have with
> doxygen and CHM, is that the index doesn't quite seem right.
> Maybe its just
> me, but in my index, I get: Classname, with a subitem of the
> destructor, and
> it was subitems of the rest of the functions.  Has anyone
> else seen that?
>
> Adam
>
> > -----Original Message-----
> > From:	Sten Darre [SMTP:sd...@ne...]
> > Sent:	Friday, November 09, 2001 8:47 AM
> > To:	dox...@li...
> > Subject:	RE: [Doxygen-users] MSDN Style
> >
> > This might be a little out of thread, but I don't think
> MSDN-look-and-feel
> > is going to make the difference as to '..to convince people..'.
> > Since it might look allright - but it isn't a real
> Micro$oft-tool, hence
> > they won't trust doxygen anyway.
> >
> > They either just love it or hate it... no matter what
> layout is used -
> > just
> > my humble experince ;-)
> >
> > Personally I think either layout is nice.
> >
> > greets
> >
> > sten
> >
> > >   As for Germar's political perspective, whatever! We are a
> > > Microsoft shop,
> > > and right now I just want to convince people to start
> auto generating
> > > documentation. The MSDN-style is my best chance to do that,
> > > since we are all
> > > familiar with that format.
> >
> >
> > > -----Original Message-----
> > > From: dox...@li...
> > > [mailto:dox...@li...]On
> Behalf Of Wagner,
> > > Victor
> > > Sent: 09 November 2001 14:48
> > > To: 'Christian Ratliff'; 'dox...@li...'
> > > Subject: RE: [Doxygen-users] MSDN Style
> > >
> > >
> > > Poor management decisions on the part of  your company is no
> > > reason to risk
> > > breaking what is a GREAT tool for the rest of us.  If you're
> > > so proud of
> > > being a "Microsoft shop" ask THEN for THEIR automatic
> > > documentation tool.
> > >
> > > -----Original Message-----
> > > From: Christian Ratliff [mailto:cra...@de...]
> > > Sent: Friday, 2001 November 09 06:05
> > > To: 'dox...@li...'
> > > Subject: RE: [Doxygen-users] MSDN Style
> > >
> > >
> > > Dimitri,
> > >
> > >   What can I do to help get this patch in? If it is through
> > > some "style
> > > interface hook" mechanism, which Germar mentions, I am
> glad to offer
> > > whatever assistance I can.
> > >   As for Germar's political perspective, whatever! We are a
> > > Microsoft shop,
> > > and right now I just want to convince people to start
> auto generating
> > > documentation. The MSDN-style is my best chance to do that,
> > > since we are all
> > > familiar with that format.
> > >
> > > christian
> > >
> > > +-----+
> > > Christian Ratliff <cra...@de...>
> > > Sr. Technology Architect
> > > Core Libraries Group, DeLorme
> > > "This is the very perfection of man,
> > >   to find out his own imperfections" -  St. Augustine
> > >
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Dimitri van Heesch [mailto:di...@st...]
> > > Sent: Thursday, November 08, 2001 4:25 PM
> > > To: dox...@li...
> > > Subject: Re: [Doxygen-users] MSDN Style
> > >
> > >
> > > On Thu, Nov 08, 2001 at 08:25:21AM -0500, Christian Ratliff wrote:
> > > > Hello all,
> > > >
> > > >   Has the MSDN style been merged into the code base in CVS
> > > yet? We use
> > > > that style for all of our auto-generated documentation
> now, but I
> > > > would prefer to move to a more recent release than 1.2.6. I
> > > have been
> > > > monitoring the recent change logs, but perhaps I overlooked its
> > > > mention.
> > > >
> > >
> > > I'm still investigating the impact of Alexandr Chelpanov's patch.
> > > It is quite huge, still has rough edges, and introduces a lot
> > > of conditional
> > >
> > > code (mostly only for html, and even some IE specific stuff),
> > > so from a
> > > test/maintenance point of view I am not overly enthousiastic yet.
> > >
> > > >From a user point of view I can understand the MSDN style
> > > feature is nice
> > > though.
> > >
> > > Regards,
> > >   Dimitri
> > >
> > >
> > > _______________________________________________
> > > Doxygen-users mailing list
> > > Dox...@li...
> > > https://lists.sourceforge.net/lists/listinfo/doxygen-users
> > >
> > > _______________________________________________
> > > Doxygen-users mailing list
> > > Dox...@li...
> > > https://lists.sourceforge.net/lists/listinfo/doxygen-users
> > >
> > > _______________________________________________
> > > Doxygen-users mailing list
> > > Dox...@li...
> > > https://lists.sourceforge.net/lists/listinfo/doxygen-users
> > >
> >
> >
> > _______________________________________________
> > Doxygen-users mailing list
> > Dox...@li...
> > https://lists.sourceforge.net/lists/listinfo/doxygen-users
>
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

RE: [Doxygen-users] MSDN Style

[Adam T. <ad...@fi...>]

Again, for my 2 cents, this sounds good.  The trick is the get the HTML
generator fixes after such a split back into the MSDN style code.

Adam

> -----Original Message-----
> From:	Prikryl,Petr [SMTP:PRI...@sk...]
> Sent:	Friday, November 09, 2001 2:33 AM
> To:	dox...@li...
> Subject:	RE: [Doxygen-users] MSDN Style
> 
> Hi,
> 
> Dimitri wrote:
> > On Thu, Nov 08, 2001 at 08:25:21AM -0500, Christian Ratliff wrote:
> > > [...]
> > >   Has the MSDN style been merged into the code base in CVS yet? We use
> that
> > > style for all of our auto-generated documentation now, but I would
> prefer to
> > > move to a more recent release than 1.2.6. I have been monitoring the
> recent
> > > change logs, but perhaps I overlooked its mention.
> > 
> > I'm still investigating the impact of Alexandr Chelpanov's patch. 
> > It is quite huge, still has rough edges, and introduces a lot of
> conditional 
> > code (mostly only for html, and even some IE specific stuff), so from a 
> > test/maintenance point of view I am not overly enthousiastic yet.
> 
> In my opinion, MSDN Style will always be IE specific, and 
> it will probably be focused mainly on HTML.  If MSDN Style 
> were to be merged into the official doxygen, wouldn't
> it be easier to introduce it via another, MSDN-specific 
> HTML-generator?  I think that this way it could be separated
> from the rest of doxygen, and it could possibly be conditionally 
> excluded during compilation for the environment where MSDN Style
> does not make sense.  
> 
> Microsoft likes to make changes and it does not like to follow
> standards, sometimes.  Too tight integration of MSDN Style 
> could spoil the doxygen core later.
> 
> Regards,
>   Petr
> 
> 
> -- 
> Petr Prikryl, SKIL, spol. s r.o., pri...@sk...
> 
> 
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

RE: [Doxygen-users] MSDN Style

[Adam T. <ad...@fi...>]

Oh, come on, lets not get in a flame war here.  Despite all the bad feels
about microsoft, there are a LOT of companies that develop on its platform.
To simply disregard their input at all is silly.  If you stop caring about
the needs of your customers, you end up exactly like M$, don't you?

Adam

> -----Original Message-----
> From:	Wagner, Victor [SMTP:VW...@se...]
> Sent:	Friday, November 09, 2001 7:48 AM
> To:	'Christian Ratliff'; 'dox...@li...'
> Subject:	RE: [Doxygen-users] MSDN Style
> 
> Poor management decisions on the part of  your company is no reason to
> risk
> breaking what is a GREAT tool for the rest of us.  If you're so proud of
> being a "Microsoft shop" ask THEN for THEIR automatic documentation tool.
> 
> -----Original Message-----
> From: Christian Ratliff [mailto:cra...@de...]
> Sent: Friday, 2001 November 09 06:05
> To: 'dox...@li...'
> Subject: RE: [Doxygen-users] MSDN Style
> 
> 
> Dimitri,
> 
>   What can I do to help get this patch in? If it is through some "style
> interface hook" mechanism, which Germar mentions, I am glad to offer
> whatever assistance I can.
>   As for Germar's political perspective, whatever! We are a Microsoft
> shop,
> and right now I just want to convince people to start auto generating
> documentation. The MSDN-style is my best chance to do that, since we are
> all
> familiar with that format.
> 
> christian
> 
> +-----+
> Christian Ratliff <cra...@de...>
> Sr. Technology Architect
> Core Libraries Group, DeLorme
> "This is the very perfection of man, 
>   to find out his own imperfections" -  St. Augustine
> 
> 
> 
> 
> -----Original Message-----
> From: Dimitri van Heesch [mailto:di...@st...] 
> Sent: Thursday, November 08, 2001 4:25 PM
> To: dox...@li...
> Subject: Re: [Doxygen-users] MSDN Style
> 
> 
> On Thu, Nov 08, 2001 at 08:25:21AM -0500, Christian Ratliff wrote:
> > Hello all,
> > 
> >   Has the MSDN style been merged into the code base in CVS yet? We use 
> > that style for all of our auto-generated documentation now, but I 
> > would prefer to move to a more recent release than 1.2.6. I have been 
> > monitoring the recent change logs, but perhaps I overlooked its 
> > mention.
> > 
> 
> I'm still investigating the impact of Alexandr Chelpanov's patch. 
> It is quite huge, still has rough edges, and introduces a lot of
> conditional
> 
> code (mostly only for html, and even some IE specific stuff), so from a 
> test/maintenance point of view I am not overly enthousiastic yet.
> 
> From a user point of view I can understand the MSDN style feature is nice 
> though.
> 
> Regards,
>   Dimitri
> 
> 
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
> 
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
> 
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

RE: [Doxygen-users] MSDN Style

[Christian R. <cra...@de...>]

  At this point I regret having even asked in the first place.

sorry!
christian

+-----+
Christian Ratliff <cra...@de...>
Sr. Technology Architect / Core Libraries Group
DeLorme Publishing Co.
"This is the very perfection of man, 
  to find out his own imperfections" -  St. Augustine

Re: [Doxygen-users] MSDN Style

[Dimitri v. H. <di...@st...>]

On Fri, Nov 09, 2001 at 12:54:02PM -0500, Christian Ratliff wrote:
> 
>   At this point I regret having even asked in the first place.

You shouldn't. I think it is clear now that this is a bit of a
controversial topic ;-)

Anyway as Germar suggested I should better work on the XML output & parser,
so that the HTML output can be generated from that, and than it is
much cleaner to add more diverse look'n'feels in that generator (or 
a different generator if that is less work). Aleksandr has already 
offered to help so that's very kind. And those running a Microsoft shop 
should have more patience and help coding :-)

Regards,
  Dimitri

Re: [Doxygen-users] MSDN Style

[Dimitri v. H. <di...@st...>]

On Sat, Nov 10, 2001 at 03:28:32PM +0300, Aleksandr Vital%evic Celpanov wrote:
> 	I have a some questions.
> 	1. What is target of restructuring doxygen? There are a 2
> different ways, in my opinion.
> a) sources -> doxygen_parser.exe -> xml -> latexgen -> latex
> 							-> htmlgen ->
> html
> 							...
> 			
> b) sources -> doxygen_parser.lib + xmlgen -> xml
> 		-> doxygen_parser.lib + htmlgen -> html

What I'm aiming for is:

sources -> doxygen.exe (incl xmlgen) -> xml -> 
   htmlgen.exe (using doxygen_xmlparser.lib) -> html

How doxygen_xmlparser.lib will evolve can be seen in addon/xmlparse.

> 
> 	2. Will doxygen_parser parse comments (\brief, \param)? 

For \brief there will be (already is in fact) a different section.
\param will be a specific xml command.

For instance 

    /*! \brief A method.
     *
     *  \param b an integer.
     */

will result in:

        <briefdescription>
          <para>
            A method. 
          </para>
        </briefdescription>
        <detaileddescription>
          <para>
            <parameterlist kind="param">
              <parametername>b</parametername>
              <parameterdescription><para>an integer. </para>
              </parameterdescription>
            </parameterlist>
          </para>
        </detaileddescription>

Please look at the current XML output for more details.

> If it
> will, how it can parse
> specific for output tags, like \htmlonly ? 

Commands like \htmlonly will either disappear or turned into some 
internally unformatted tags like <htmlonly>...</htmlonly>. I haven't
decided yet.

> 	3. Will Doxyfile be sharable for parser & latexgen & etc. and
> where it will be.

The idea is that the configuration file parser is separate library,
containing the options for the engine only. Output formats can extend
the config file with specific options. So it is the output generators that
will generate the template configuration file for a specific format, but
doing so will be easy for the programmer and use a common library (part of
the doxygen distribution).

> 	4. Do you want to split current version of doxygen to parser,
> latextgen, htmlgen, etc
> or you stay latex, htmlgen etc. in doxygen and new doxygen struct will
> creating for new output formats only.

For the time being the current output generators will be kept and maintained,
but in the end they will be removed and replaced by separate executables,
all based on the same xml output.

> 	Other questions depends on aforesaid.

I open for questions/suggestions. Things can still change if needed ;-)

Regards,
  Dimitri

RE: [Doxygen-users] MSDN Style

[Henrik N. <He...@no...>]

I would also like to see this feature.

// Henrik N

> 
> I would like to see this as well. The MSDN style is really cool.
> 
> BTW, I am writing a small tool to integrate the help generated
> by doxygen into VS.NET. It looks cool, but it is still in development.
> 
> Regards
> Thomas
> 
> 
> > -----Original Message-----
> > From: dox...@li... 
> > Sent: Thursday, 08 November, 2001 14:37
> > To: dox...@li...
> > Subject: [Doxygen-users] MSDN Style
> > 
> > 
> > Hello all,
> > 
> >   Has the MSDN style been merged into the code base in CVS 
> > yet? We use that style for all of our auto-generated 
> > documentation now, but I would prefer to move to a more 
> > recent release than 1.2.6. I have been monitoring the recent 
> > change logs, but perhaps I overlooked its mention.
> > 
> > thank you,
> > christian
> > 
> > PS. For all those who replied to my "Comment Folding" query, 
> > whoops! I added the ! token to the comment and it worked like 
> > a charm. Thanks very much too all.
>