Menu
▾
▴
corelinux-develop
|
From: Frank V. C. <fr...@co...> - 2000-08-12 16:33:34
|
I check-in all of the abstract framework stuff. I am going to try to start capturing the "how to" in the developers guide before the build. Any issues/questions/etc? Oh, yeah, Christophe: The update.makefile.pl in /src/testdrivers is not meant to be run by hand for anyreason is it? -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux http://PythPat.sourceforge.net Pythons Pattern Package |
|
From: Christophe Prud'h. <pru...@MI...> - 2000-08-12 19:40:49
|
> Any issues/questions/etc? None on my side I just made a little change on debian side for the building process and the packages are done. I 'll check the installation and a few other things is everything ok with rpm? I'll be there tomorrow so we can tackle the last problems, issues and documentation requirements on the doc side - how to make deb packages - how to make redhat package - how to generate the reference manual (BTW doxygen is working well, with the pdf patch and there is a qt graphical interface that comes with it by passing --with-doxywizard or something like that to configure) - how to make reference manual nicer with doxygen put a few comments about how to document classes comments? > > Oh, yeah, Christophe: The update.makefile.pl in /src/testdrivers is not > meant to be run by hand for anyreason is it? this script allowed me to update all the makefile with the -lcl++ it can be helpful in the future but you can remove it if you want -- Christophe Prud'homme | MIT, 77, Mass Ave, Rm 3-243 | The Second Law of Thermodynamics: Cambridge MA 02139 | If you think things are in a mess Tel (Office) : (00 1) (617) 253 0229 | now, just wait! Fax (Office) : (00 1) (617) 258 8559 | -- Jim Warner http://augustine.mit.edu/~prudhomm | Following the hacker spirit |
|
From: Frank V. C. <fr...@co...> - 2000-08-12 20:21:11
|
Christophe Prud'homme wrote: > > > Any issues/questions/etc? > None on my side I just made a little change on debian side for the building > process > and the packages are done. > I 'll check the installation and a few other things > > is everything ok with rpm? Yep, I haven't found any problems other than the ones you fixed. > I'll be there tomorrow so we can tackle the last problems, issues > and documentation requirements > > on the doc side > - how to make deb packages > - how to make redhat package > - how to generate the reference manual (BTW doxygen is working well, with the > pdf patch and there is a qt graphical interface that comes with it by > passing --with-doxywizard or something like that to configure) Yes, the reference package is something you may want to generate along with the debian pacakges until I get the doxygen updates. > - how to make reference manual nicer with doxygen > put a few comments about how to document classes Am I doing it wrong using the JavaDoc tags? > > comments? > > > > > Oh, yeah, Christophe: The update.makefile.pl in /src/testdrivers is not > > meant to be run by hand for anyreason is it? > this script allowed me to update all the makefile with the -lcl++ > it can be helpful in the future but you can remove it if you want We may want to start a cvs branch of utilities and scripts? -- Frank V. Castellucci |
|
From: Christophe Prud'h. <pru...@MI...> - 2000-08-12 20:30:49
|
> Yep, I haven't found any problems other than the ones you fixed. good > Yes, the reference package is something you may want to generate along > with the debian pacakges until I get the doxygen updates. but what abount the rpm? the ref manual is also generated for rpm for the corelinux-doc > > > - how to make reference manual nicer with doxygen > > put a few comments about how to document classes > > Am I doing it wrong using the JavaDoc tags? yes but you can have much much more - todo list - warning - bug list - include examples - better formatting - inclusion of images (like the use cases amnd classes diagrams) that would be just great I'll work on that for the next version if you agree > We may want to start a cvs branch of utilities and scripts? why not what do you propose as a module name? -- Christophe Prud'homme | MIT, 77, Mass Ave, Rm 3-243 | The first thing we do, let's kill Cambridge MA 02139 | all the lawyers. Tel (Office) : (00 1) (617) 253 0229 | -- Wm. Shakespeare, Fax (Office) : (00 1) (617) 258 8559 | "Henry VI", Part IV http://augustine.mit.edu/~prudhomm | Following the hacker spirit |
|
From: Christophe Prud'h. <pru...@MI...> - 2000-08-12 20:41:11
|
> > Am I doing it wrong using the JavaDoc tags? > > yes but you can have much much more I meant no but we can have something even better, sorry :) -- Christophe Prud'homme | MIT, 77, Mass Ave, Rm 3-243 | C'est de la buche? Cambridge MA 02139 | Non c'est kloug! Tel (Office) : (00 1) (617) 253 0229 | C'est colmatti avec du schpountz... Fax (Office) : (00 1) (617) 258 8559 | -- Le Pere Noel est une ordure http://augustine.mit.edu/~prudhomm | Following the hacker spirit |
|
From: Frank V. C. <fr...@co...> - 2000-08-12 21:11:44
|
Christophe Prud'homme wrote: > > > Yep, I haven't found any problems other than the ones you fixed. > good > > > Yes, the reference package is something you may want to generate along > > with the debian pacakges until I get the doxygen updates. > > but what abount the rpm? > the ref manual is also generated for rpm for the corelinux-doc Yes, I have a problem generating that, although you may have forgotten. I need to apply the update as I am running doxygen 1.1.2. I will check their site to see if they have a rpm for the latest release, otherwise I will get the source and build. > > > - how to make reference manual nicer with doxygen > > > put a few comments about how to document classes > > > > Am I doing it wrong using the JavaDoc tags? > yes but you can have much much more > > - todo list > - warning > - bug list > - include examples > - better formatting > - inclusion of images (like the use cases amnd classes diagrams) > that would be just great > I'll work on that for the next version if you agree I will spend some time with the doxygen specific tags. BUT, as you appear to be enamored with things that make presentation wonderful, when the next better mousetrap comes along how will we deal with tools specific tagging? What I would prefer is a universal tagging option (JavaDoc?) that doesn't tie us down and yet still provides quality output. I would prefer we start thinking about a more complete developers guide which would have all the requirements, analysis, and design documentation. But that would be HUGE. For now, I would skip putting the use-case/class diagrams in the class reference. > > > We may want to start a cvs branch of utilities and scripts? > why not > what do you propose as a module name? devscripts? buildtools? projtools? Frank |
|
From: Hans D. <dul...@eg...> - 2000-08-14 05:25:05
|
"Frank V. Castellucci" wrote: > > Christophe Prud'homme wrote: > > > > > Yep, I haven't found any problems other than the ones you fixed. > > good > > > > > Yes, the reference package is something you may want to generate along > > > with the debian pacakges until I get the doxygen updates. > > > > but what abount the rpm? > > the ref manual is also generated for rpm for the corelinux-doc > > Yes, I have a problem generating that, although you may have forgotten. > I need to apply the update as I am running doxygen 1.1.2. I will check > their site to see if they have a rpm for the latest release, otherwise I > will get the source and build. > > > > > - how to make reference manual nicer with doxygen > > > > put a few comments about how to document classes > > > > > > Am I doing it wrong using the JavaDoc tags? > > yes but you can have much much more > > > > - todo list > > - warning > > - bug list > > - include examples > > - better formatting > > - inclusion of images (like the use cases amnd classes diagrams) > > that would be just great > > I'll work on that for the next version if you agree > > I will spend some time with the doxygen specific tags. BUT, as you > appear to be enamored with things that make presentation wonderful, when > the next better mousetrap comes along how will we deal with tools > specific tagging? What I would prefer is a universal tagging option > (JavaDoc?) that doesn't tie us down and yet still provides quality > output. > > I would prefer we start thinking about a more complete developers guide > which would have all the requirements, analysis, and design > documentation. But that would be HUGE. For now, I would skip putting the > use-case/class diagrams in the class reference. > > > > > > We may want to start a cvs branch of utilities and scripts? > > why not > > what do you propose as a module name? > > devscripts? buildtools? projtools? I think "buildtools" fits well. > > Frank > > _______________________________________________ > Corelinux-develop mailing list > Cor...@li... > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop -- Hans Dulimarta, Ph.D. dul...@co... P: 517-432-7589 http://www.egr.msu.edu/~dulimart F: 760-281-7691 http://corelinux.sourceforge.net Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824 |
|
From: Frank V. C. <fr...@co...> - 2000-08-15 01:30:39
|
Hans Dulimarta wrote: > > "Frank V. Castellucci" wrote: > > > > Christophe Prud'homme wrote: > > > > > > > Yep, I haven't found any problems other than the ones you fixed. > > > good > > > > > > > Yes, the reference package is something you may want to generate along > > > > with the debian pacakges until I get the doxygen updates. > > > > > > but what abount the rpm? > > > the ref manual is also generated for rpm for the corelinux-doc > > > > Yes, I have a problem generating that, although you may have forgotten. > > I need to apply the update as I am running doxygen 1.1.2. I will check > > their site to see if they have a rpm for the latest release, otherwise I > > will get the source and build. > > > > > > > - how to make reference manual nicer with doxygen > > > > > put a few comments about how to document classes > > > > > > > > Am I doing it wrong using the JavaDoc tags? > > > yes but you can have much much more > > > > > > - todo list > > > - warning > > > - bug list > > > - include examples > > > - better formatting > > > - inclusion of images (like the use cases amnd classes diagrams) > > > that would be just great > > > I'll work on that for the next version if you agree > > > > I will spend some time with the doxygen specific tags. BUT, as you > > appear to be enamored with things that make presentation wonderful, when > > the next better mousetrap comes along how will we deal with tools > > specific tagging? What I would prefer is a universal tagging option > > (JavaDoc?) that doesn't tie us down and yet still provides quality > > output. > > > > I would prefer we start thinking about a more complete developers guide > > which would have all the requirements, analysis, and design > > documentation. But that would be HUGE. For now, I would skip putting the > > use-case/class diagrams in the class reference. > > > > > > > > > We may want to start a cvs branch of utilities and scripts? > > > why not > > > what do you propose as a module name? > > > > devscripts? buildtools? projtools? > > I think "buildtools" fits well. :) Thats a majority vote! The only thing I have to put in at the moment is a script which pulls the PDF, DVI, and TeX out from htdocs and tar.gz's them up. That will change. -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux http://PythPat.sourceforge.net Pythons Pattern Package |
|
From: Hans D. <dul...@eg...> - 2000-08-14 05:21:48
|
"Frank V. Castellucci" wrote: > > Christophe Prud'homme wrote: > > > > > Any issues/questions/etc? > > None on my side I just made a little change on debian side for the building > > process > > and the packages are done. > > I 'll check the installation and a few other things > > > > is everything ok with rpm? > > Yep, I haven't found any problems other than the ones you fixed. > > > I'll be there tomorrow so we can tackle the last problems, issues > > and documentation requirements > > > > on the doc side > > - how to make deb packages > > - how to make redhat package > > - how to generate the reference manual (BTW doxygen is working well, with the > > pdf patch and there is a qt graphical interface that comes with it by > > passing --with-doxywizard or something like that to configure) > > Yes, the reference package is something you may want to generate along > with the debian pacakges until I get the doxygen updates. > > > - how to make reference manual nicer with doxygen > > put a few comments about how to document classes > > Am I doing it wrong using the JavaDoc tags? > > > > > comments? > > > > > > > > Oh, yeah, Christophe: The update.makefile.pl in /src/testdrivers is not > > > meant to be run by hand for anyreason is it? > > this script allowed me to update all the makefile with the -lcl++ > > it can be helpful in the future but you can remove it if you want > > We may want to start a cvs branch of utilities and scripts? Agree on this. I think eventually the scripts and utilities will grow bigger. > > -- > Frank V. Castellucci > > _______________________________________________ > Corelinux-develop mailing list > Cor...@li... > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop -- Hans Dulimarta, Ph.D. dul...@co... P: 517-432-7589 http://www.egr.msu.edu/~dulimart F: 760-281-7691 http://corelinux.sourceforge.net Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824 |
