I like the javadoc approach, where all the methods [fields,
constructors] of a class are listed alphabetically in the overview
section, but in textual order in the detailed list that follows the
overview.
That's a good idea to follow.
Michael
--
Michael Hoennig [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Hoennig wrote:
|I like the javadoc approach, where all the methods [fields,
|constructors] of a class are listed alphabetically in the overview
|section, but in textual order in the detailed list that follows the
|overview.
|
|
| That's a good
Stephan Bergmann wrote:
I like the javadoc approach, where all the methods [fields,
constructors] of a class are listed alphabetically in the overview
section, but in textual order in the detailed list that follows the
overview.
Sounds good to me!
Make a task from it?
Nikolai
Hi Thomas,
How is the IDL created?
For my case, using vim ;-)
Maybe we could switch to output format to XML
and then do the same the codesnippet page does?
XML = HTML
* once sorted alphabetically
* once grouped like it is now
Oh, you meant how the HTML is generated from the IDL. Ok,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nikolai Pretzell wrote:
| Hi Thomas,
|
[...]
| Actually creating XML ouput is planned to be realised already anyway.
|
Having XML would be enough form my point of view because one can do
sorting, ... with XSLT.
| Adding alphabetical lists like in one
Hi Tom,
I suppose that the IDL-Reference Properties are ordered at the moment
using the occurrence of the properties in the IDL-File. The good point
about this is that you can group together things like RightMargin and
LeftMargin but for someone who is looking for a property it would be
Hi,
How is the IDL created? Maybe we could switch to output format to XML and
then do the same the codesnippet page does?
XML = HTML
* once sorted alphabetically
* once grouped like it is now
According to the what the user desires? We could even create other output
formats from this point on
