my issues:
(I'm very interested in your opinion about...)
Why not mixing GOOD software
together to one (see next):
- www.scintilla.org: it's an absolutely free and good
editor with syntax highlighting running well on
windows AND linux. I think it's not a work to
do by classbuilder people to write an OWN editor.
(Scintilla is a lib for reuseabilty, SciTe a example)
- http://www.stack.nl/~dimitri/doxygen: it's really the
best freeware source documenting tool I know.
(running on windows AND linux)
OUTPUT: html, rtf, man, latex
Again, I think it's not a work to do by...
classbuilder people could concentrate on
visual design of class systems because the
"tools" are done well by other...
best regards,
Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have briefly looked at both of but how would you fit these Library/Applications into ClassBuilder. What about wxWindows, if you start putting pieces that use their own seperate GUI's would that not become unmanagable and lead to a large program?
'"tools" are done well by other...' are you saying "why reinvent the wheel"
Craig
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I also could think of some synergy effect with class builder, doxygen and scintilla:
e.g.:
classbuilder could easily use the scintilla control as the function body editor.
more important could be a doxygen export (similar to write source/write html/writel http.
Doxygen is so widely used that it is often required for projects, besides it can produce documentation superior and better portable output (Latex includes etc.)
best regards,
Christian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Even if doxygen isn't directly supported by cb, doxygen is flexible enough to be used in a cb project. The class headers, user sections, function bodies are good places for doxygen integrations (tags). In this content I would be glad to see, if the method/attribute decls could be tagged with some kind of documentations. Then, classbuilder could be used nearly perfect with doxygen.
Regards
Edgar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Doxygen support has been added to release 2.9 PR523 available on the download page.
Scintilla is a different story, it uses the "wrong" base class to allow easy integration into CB. I think that, like me, most people use their own favourite editor/IDE outside of CB to alter the code. If not (meaning hundreds of reactions to please, please integrate Scintilla into CB), I'll have another go at it ;-)
Regards,
John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hi all,
I'm new to the "open discussion".
my issues:
(I'm very interested in your opinion about...)
Why not mixing GOOD software
together to one (see next):
- www.scintilla.org: it's an absolutely free and good
editor with syntax highlighting running well on
windows AND linux. I think it's not a work to
do by classbuilder people to write an OWN editor.
(Scintilla is a lib for reuseabilty, SciTe a example)
- http://www.stack.nl/~dimitri/doxygen: it's really the
best freeware source documenting tool I know.
(running on windows AND linux)
OUTPUT: html, rtf, man, latex
Again, I think it's not a work to do by...
classbuilder people could concentrate on
visual design of class systems because the
"tools" are done well by other...
best regards,
Thomas
I have briefly looked at both of but how would you fit these Library/Applications into ClassBuilder. What about wxWindows, if you start putting pieces that use their own seperate GUI's would that not become unmanagable and lead to a large program?
'"tools" are done well by other...' are you saying "why reinvent the wheel"
Craig
I also could think of some synergy effect with class builder, doxygen and scintilla:
e.g.:
classbuilder could easily use the scintilla control as the function body editor.
more important could be a doxygen export (similar to write source/write html/writel http.
Doxygen is so widely used that it is often required for projects, besides it can produce documentation superior and better portable output (Latex includes etc.)
best regards,
Christian
Hehe ,I think that's not worth to do something! There's something to do and bugs to fix!And has something more important to do!
Even if doxygen isn't directly supported by cb, doxygen is flexible enough to be used in a cb project. The class headers, user sections, function bodies are good places for doxygen integrations (tags). In this content I would be glad to see, if the method/attribute decls could be tagged with some kind of documentations. Then, classbuilder could be used nearly perfect with doxygen.
Regards
Edgar
Support for Doxygen will be added to the next release. In fact, I'm testing it right now ;-)
Make sure you subscribe to https://lists.sourceforge.net/lists/listinfo/classbuilder-news to stay tuned.
Regards,
John
Doxygen support has been added to release 2.9 PR523 available on the download page.
Scintilla is a different story, it uses the "wrong" base class to allow easy integration into CB. I think that, like me, most people use their own favourite editor/IDE outside of CB to alter the code. If not (meaning hundreds of reactions to please, please integrate Scintilla into CB), I'll have another go at it ;-)
Regards,
John