Menu
▾
▴
buddy-developers — Participating in BuDDy development
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(4) |
Jul
(53) |
Aug
(5) |
Sep
(2) |
Oct
(1) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(8) |
Feb
(2) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
(9) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(28) |
Aug
(9) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2013 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Haim C. <hai...@us...> - 2007-07-25 11:46:40
|
Looks awesome ! I hope wiki will positively develop. On 7/25/07, Nikos Gkorogiannis <N.G...@cs...> wrote: > Hi Haim, > > I did think about the Wiki when I was reading the documentation on the > web sites. In my personal experience wikis can be good and they can be > bad :) It all depends on the nature of the content and the group of > people involved. In any case, I don't mind us trying it out. > > I've changed the page at > http://buddy.sourceforge.net > to redirect to the wiki. > > And I added a navigation link in the wiki to the reference manual, now > uploaded at http://buddy.sourceforge.net/manual/ I've also added the > basic content I was going to put in the web page to the main wiki page, > have a look. > > Nikos > > On Tue, 2007-07-24 at 21:49 -0400, Haim Cohen wrote: > > Just had a thought - why not to use WIKI instead of traditional web page ? > > I enabled wiki ! Here is the link: > > http://buddy.wiki.sourceforge.net/ > > With wiki, everybody can contribute contents. > > We can can store the doxygen on the web-server and just put a link to > > it from wiki. > > But wiki will be our main page. > > > > What do you think ? > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > Buddy-developers mailing list > > Bud...@li... > > https://lists.sourceforge.net/lists/listinfo/buddy-developers > > -- _______________________________ Haim Cohen (212) 289 5405 |
|
From: Nikos G. <N.G...@cs...> - 2007-07-25 08:47:59
|
Hi Haim, I did think about the Wiki when I was reading the documentation on the web sites. In my personal experience wikis can be good and they can be bad :) It all depends on the nature of the content and the group of people involved. In any case, I don't mind us trying it out. I've changed the page at http://buddy.sourceforge.net to redirect to the wiki. And I added a navigation link in the wiki to the reference manual, now uploaded at http://buddy.sourceforge.net/manual/ I've also added the basic content I was going to put in the web page to the main wiki page, have a look. Nikos On Tue, 2007-07-24 at 21:49 -0400, Haim Cohen wrote: > Just had a thought - why not to use WIKI instead of traditional web page ? > I enabled wiki ! Here is the link: > http://buddy.wiki.sourceforge.net/ > With wiki, everybody can contribute contents. > We can can store the doxygen on the web-server and just put a link to > it from wiki. > But wiki will be our main page. > > What do you think ? > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Buddy-developers mailing list > Bud...@li... > https://lists.sourceforge.net/lists/listinfo/buddy-developers |
|
From: Haim C. <hai...@us...> - 2007-07-25 01:49:58
|
Just had a thought - why not to use WIKI instead of traditional web page ? I enabled wiki ! Here is the link: http://buddy.wiki.sourceforge.net/ With wiki, everybody can contribute contents. We can can store the doxygen on the web-server and just put a link to it from wiki. But wiki will be our main page. What do you think ? |
|
From: Nikos G. <N.G...@cs...> - 2007-07-24 19:56:25
|
Hi Haim, I'm working on a basic web page. The Sourceforge docs require a Sourceforge logo on the project page. The link to such an image is actually a CGI to help with web statistic calculations, and therefore, specific to the project. Only project admins can, apparently, view these links: https://sourceforge.net/docman/display_doc.php?docid=4297&group_id=1#logo Could you post me a/the URL? I should have something basic up soon. Nikos On Tue, 2007-07-24 at 09:13 +0100, Nikos Gkorogiannis wrote: > On Mon, 2007-07-23 at 19:10 -0400, Haim Cohen wrote: > > It's all in the help pages in SF.... The *project* should have a unix > > account where we can put a public_html dir to be accessed by the web > > server. > > You should be warned that my web design skills are poor - all my sites > > look like yahoo at 1990... :-) > > I really appreciate your dedication working on this ! > > After a full time job and family, it's hard to find the time. I will > > do my best to look at your code over the weekend. > > No problem - I think it would be good to get more people on, which would > be helped by things like having a web page for the project, having the > docs online, doing a release, and maybe also having a freshmeat.net > project page. What do you think? > > I'll have a look at making a basic web page and sticking the docs on > it. > > > ps: we also have access to a compilation farm with all kinds of > > architectures - yummy ! > > I need to have another look at this because I never found anything > related in the sourceforge docs. > > Nikos > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Buddy-developers mailing list > Bud...@li... > https://lists.sourceforge.net/lists/listinfo/buddy-developers |
|
From: Nikos G. <N.G...@cs...> - 2007-07-24 08:14:22
|
On Mon, 2007-07-23 at 19:10 -0400, Haim Cohen wrote: > It's all in the help pages in SF.... The *project* should have a unix > account where we can put a public_html dir to be accessed by the web > server. > You should be warned that my web design skills are poor - all my sites > look like yahoo at 1990... :-) > I really appreciate your dedication working on this ! > After a full time job and family, it's hard to find the time. I will > do my best to look at your code over the weekend. No problem - I think it would be good to get more people on, which would be helped by things like having a web page for the project, having the docs online, doing a release, and maybe also having a freshmeat.net project page. What do you think? I'll have a look at making a basic web page and sticking the docs on it. > ps: we also have access to a compilation farm with all kinds of > architectures - yummy ! I need to have another look at this because I never found anything related in the sourceforge docs. Nikos |
|
From: Nikos G. <N.G...@cs...> - 2007-07-23 12:36:30
|
Hi, I've updated the 'make dist' command to build and include the docs in the distribution, and 'make maintainer-clean' to clean them. How do we put the docs up on the sourceforge website? Nikos On Mon, 2007-07-16 at 11:47 +0100, Nikos Gkorogiannis wrote: > > If we don't expect people to have doxygen then I think it's best to > > distribute the docs with the *released* sources (not necessarily the CVS > > ones). Same applies to the possible Latex output. That's also why I > > haven't attempted to change the autoconf stuff to search for doxygen > > (though maybe a warning may be nice to have), nor did I add it in the > > 'all' target (we don't want a spurious build failure if doxygen isn't > > there but the docs are). Again, no strong views on this. > > Upon reflection, I'm saying something contrary to what I did in the > Makefile.am as I added a 'clean' target, so if a user does 'make clean' > at top level, the docs disappear but the user may not be able to > re-generate them. Hmmm. Suggestions welcome! > > Nikos > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Buddy-developers mailing list > Bud...@li... > https://lists.sourceforge.net/lists/listinfo/buddy-developers |
|
From: Nikos G. <ni...@us...> - 2007-07-23 12:33:38
|
Update of /cvsroot/buddy/buddy/src In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv17033/src Modified Files: bdd.h Log Message: More documentation fixes. 'make dist' now builds and includes a copy of the Doxygen docs in doc/html. 'make maintainer-clean' will remove doc/html if present. |
|
From: Nikos G. <ni...@us...> - 2007-07-23 12:33:31
|
Update of /cvsroot/buddy/buddy/doc In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv17033/doc Modified Files: Makefile.am mainpage.h conf.doxyfile Log Message: More documentation fixes. 'make dist' now builds and includes a copy of the Doxygen docs in doc/html. 'make maintainer-clean' will remove doc/html if present. |
|
From: Nikos G. <ni...@us...> - 2007-07-16 13:52:00
|
Update of /cvsroot/buddy/buddy/doc In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv8709/doc Modified Files: conf.doxyfile Log Message: Moved docs in the user-accessible .h files (bdd.h, bvec.h fdd,h). Documented undocumented functions/data types. Various typo fixes. Tweaked again the doxygen conf file. |
|
From: Nikos G. <ni...@us...> - 2007-07-16 13:52:00
|
Update of /cvsroot/buddy/buddy/src In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv8709/src Modified Files: bvec.c bvec.h bddio.c bddop.c reorder.c kernel.c pairs.c fdd.c bdd.h fdd.h Log Message: Moved docs in the user-accessible .h files (bdd.h, bvec.h fdd,h). Documented undocumented functions/data types. Various typo fixes. Tweaked again the doxygen conf file. |
|
From: Nikos G. <N.G...@cs...> - 2007-07-16 10:47:49
|
> If we don't expect people to have doxygen then I think it's best to > distribute the docs with the *released* sources (not necessarily the CVS > ones). Same applies to the possible Latex output. That's also why I > haven't attempted to change the autoconf stuff to search for doxygen > (though maybe a warning may be nice to have), nor did I add it in the > 'all' target (we don't want a spurious build failure if doxygen isn't > there but the docs are). Again, no strong views on this. Upon reflection, I'm saying something contrary to what I did in the Makefile.am as I added a 'clean' target, so if a user does 'make clean' at top level, the docs disappear but the user may not be able to re-generate them. Hmmm. Suggestions welcome! Nikos |
|
From: Nikos G. <N.G...@cs...> - 2007-07-16 10:41:44
|
Hi, an interesting combination of keypresses meant an unfinished sent reply :) > > I recall we also have space for a project website. We can build the > > HTML and deploy it there as well ! > > Definitely! I was thinking of that as soon Yes, I was saying :) I was thinking of doing that as soon as we feel the docs have stabilised, or when a release is made. > > ps:I am updating the AUTHORS file to add *YOU* ! :-) > > Would you like me to put there your sf Email, or your other Email which I have ? Thanks - I guess the sf is better as it can be redirected. Nikos |
|
From: Nikos G. <N.G...@cs...> - 2007-07-16 10:39:14
|
Hi Haim,
> Overall, I think moving to doxygen is great and was much needed for a long time.
> I noticed you created a pseudo soruce file called mainpage.h to put
> olny doxygen comments in.
> Is there a way in doxygen to add additional file, which is not source code ?
> Not a big deal if not possible, but I don't want to confuse people
> with the ".h" extension making them think there is some code there,
> checking that file looking for code...
AFAIK, Doxygen does not care about the file extension, but does expect
the documentation to be in C/javadoc/QT/etc comments. Basically I
used .h so that my editor can auto indent the comments :) I agree that
naming in with a .h is misleading but also that naming it with a .txt
and having C/javadoc comments in it is confusing. I don't mind either so
go ahead and change it if you want.
> Another thing is, that when I run "make" in doc/, it says there is
> nothing to build.
> Shouldn't the documentation be built by default ? ("all" target )
>
> That brings me to the next question:
> Should we distribute the released version with the html files, or let
> the documentation be part of the normal build ?
> Problem is that no everyone has doxygen installed. I found I don't
> have it installed on my mac, and configure didn't warn me about it.
If we don't expect people to have doxygen then I think it's best to
distribute the docs with the *released* sources (not necessarily the CVS
ones). Same applies to the possible Latex output. That's also why I
haven't attempted to change the autoconf stuff to search for doxygen
(though maybe a warning may be nice to have), nor did I add it in the
'all' target (we don't want a spurious build failure if doxygen isn't
there but the docs are). Again, no strong views on this.
> I recall we also have space for a project website. We can build the
> HTML and deploy it there as well !
Definitely! I was thinking of that as soon
>
> Please let me know what do you think.
>
> Thanks,
> Haim
>
> ps:I am updating the AUTHORS file to add *YOU* ! :-)
> Would you like me to put there your sf Email, or your other Email which I have ?
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Buddy-developers mailing list
> Bud...@li...
> https://lists.sourceforge.net/lists/listinfo/buddy-developers
|
|
From: Haim C. <hai...@us...> - 2007-07-16 01:26:20
|
Hello Nikos,
Few comments regarding the changes you made:
Overall, I think moving to doxygen is great and was much needed for a long time.
I noticed you created a pseudo soruce file called mainpage.h to put
olny doxygen comments in.
Is there a way in doxygen to add additional file, which is not source code ?
Not a big deal if not possible, but I don't want to confuse people
with the ".h" extension making them think there is some code there,
checking that file looking for code...
Another thing is, that when I run "make" in doc/, it says there is
nothing to build.
Shouldn't the documentation be built by default ? ("all" target )
That brings me to the next question:
Should we distribute the released version with the html files, or let
the documentation be part of the normal build ?
Problem is that no everyone has doxygen installed. I found I don't
have it installed on my mac, and configure didn't warn me about it.
I recall we also have space for a project website. We can build the
HTML and deploy it there as well !
Please let me know what do you think.
Thanks,
Haim
ps:I am updating the AUTHORS file to add *YOU* ! :-)
Would you like me to put there your sf Email, or your other Email which I have ?
|
|
From: Nikos G. <N.G...@cs...> - 2007-07-15 20:56:32
|
Hi, I've just uploaded a bunch of doc fixes for the doxygen sources, a clean target in the docs directory and more. Also the reorder.c API has been added to the docs. Result can be seen as usual at http://www.cs.ucl.ac.uk/staff/n.gkorogiannis/buddy/ What is still missing is a Latex version and the C++ API. A suggestion is to move all doc-comments to the user-accessible .h files (bdd.h, bvec.h et al) This aligns more with the Doxygen ways, helps with singling out undocumented APIs (which do exist, BTW), separates user (non)-accessible sources more cleanly, and may help with the C++ API. Any objections? Nikos |
|
From: Nikos G. <ni...@us...> - 2007-07-15 20:44:03
|
Update of /cvsroot/buddy/buddy/src In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv9206/src Modified Files: bvec.c bddio.c reorder.c kernel.c fdd.c bddop.c pairs.c bdd.h Log Message: Multiple documentation fixes for doxygen docs. |
|
From: Nikos G. <ni...@us...> - 2007-07-15 20:44:00
|
Update of /cvsroot/buddy/buddy/doc In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv9206/doc Modified Files: Makefile.am conf.doxyfile Added Files: varblock.eps varblock.png mainpage.h Removed Files: mainpage.c Log Message: Multiple documentation fixes for doxygen docs. |
|
From: Nikos G. <ni...@us...> - 2007-07-13 09:39:45
|
Update of /cvsroot/buddy/buddy/examples/fdd In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv6877/examples/fdd Modified Files: .cvsignore Log Message: Documentation conversion to doxygen |
|
From: Nikos G. <ni...@us...> - 2007-07-13 09:39:40
|
Update of /cvsroot/buddy/buddy/src In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv6877/src Modified Files: bvec.c bvec.h bddio.c kernel.c fdd.c bddop.c pairs.c bdd.h Log Message: Documentation conversion to doxygen |
|
From: Nikos G. <ni...@us...> - 2007-07-13 09:39:39
|
Update of /cvsroot/buddy/buddy/tools In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv6877/tools Modified Files: .cvsignore Log Message: Documentation conversion to doxygen |
|
From: Nikos G. <ni...@us...> - 2007-07-13 09:39:38
|
Update of /cvsroot/buddy/buddy In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv6877 Modified Files: .cvsignore Log Message: Documentation conversion to doxygen |
|
From: Nikos G. <ni...@us...> - 2007-07-13 09:39:38
|
Update of /cvsroot/buddy/buddy/doc In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv6877/doc Modified Files: .cvsignore Makefile.am Added Files: conf.doxyfile mainpage.c Log Message: Documentation conversion to doxygen |
|
From: Haim C. <hai...@us...> - 2007-07-13 02:16:18
|
Looks awesome ! On 7/12/07, Nikos Gkorogiannis <N.G...@cs...> wrote: > Hi Haim, > > Several tweaks both in the mangling of the old latex-based syntax, as > well as in the doxygen options. See: > > http://www.cs.ucl.ac.uk/staff/n.gkorogiannis/buddy/ > > I've also made the changes to the makefile.am so that when you run "make > html" you get the html docs. I'll commit the changes as soon as you're > happy with the docs above. > > Nikos > > > -- _______________________________ Haim Cohen (212) 289 5405 |
|
From: Nikos G. <N.G...@cs...> - 2007-07-12 13:35:02
|
Hi Haim, Several tweaks both in the mangling of the old latex-based syntax, as well as in the doxygen options. See: http://www.cs.ucl.ac.uk/staff/n.gkorogiannis/buddy/ I've also made the changes to the makefile.am so that when you run "make html" you get the html docs. I'll commit the changes as soon as you're happy with the docs above. Nikos |
|
From: Nikos G. <N.G...@cs...> - 2007-07-11 10:18:20
|
Hi Haim, > Can we also make it part of the Makefiles, so the docs get generated > (if doxygen is available on the system) when you run make ? Sure, as soon as I work out how to do it with autoconf :) I now see that even the introductory material can be put into doxygen, in the front page stuff, so I'll have a look at that too. By the way, I haven't committed anything back in yet. Nikos |
