New help
Hi, I've just read a request for help in the Linux-Announce Digest #758. I'm not sure if I'll be of much help. I'm an accountant by profession, but I'm much inclined towards IT. As such, I understand what both the accountants' and programmers' wants and needs, and constraints. I'm more used to programming high level languages like dBASE but I think I can understand some smathering of C. I'm still not a full fledged Linux user since I still rely on some windows based software for my work, e.g. Photoshop, AutoCAD, etc.. Thus my primary OS is still windows, but I have my pc dual boot into Redhat 9. With regards to availability of time, I have to admit first that I'm busy with work and currently doing my MBA. Hope I can contribute somehow. Regards, Jason Tan Boon Teck This e-mail has been sent via JARING webmail at http://www.jaring.my ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: New help
We can gladly use your help.. How would you LIKE to help? -derek Jason Tan <[EMAIL PROTECTED]> writes: > Hi, > > > I've just read a request for help in the Linux-Announce Digest #758. > > I'm not sure if I'll be of much help. > > I'm an accountant by profession, but I'm much inclined towards IT. As > such, I understand what both the accountants' and programmers' wants and > needs, and constraints. > > I'm more used to programming high level languages like dBASE but I think I > can understand some smathering of C. > > I'm still not a full fledged Linux user since I still rely on some windows > based software for my work, e.g. Photoshop, AutoCAD, etc.. Thus my > primary OS is still windows, but I have my pc dual boot into Redhat 9. > > With regards to availability of time, I have to admit first that I'm busy > with work and currently doing my MBA. > > Hope I can contribute somehow. > > Regards, > > Jason Tan Boon Teck > > > > > This e-mail has been sent via JARING webmail at http://www.jaring.my > ___ > gnucash-devel mailing list > [EMAIL PROTECTED] > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > > -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: New help
On Tue, May 04, 2004 at 07:35:09PM +0800, Jason Tan was heard to remark: > Hi, > > > I've just read a request for help in the Linux-Announce Digest #758. > > I'm not sure if I'll be of much help. > > I'm an accountant by profession, but I'm much inclined towards IT. As > such, I understand what both the accountants' and programmers' wants and > needs, and constraints. > > I'm more used to programming high level languages like dBASE but I think I > can understand some smathering of C. > > I'm still not a full fledged Linux user since I still rely on some windows > based software for my work, e.g. Photoshop, AutoCAD, etc.. Thus my > primary OS is still windows, but I have my pc dual boot into Redhat 9. > > With regards to availability of time, I have to admit first that I'm busy > with work and currently doing my MBA. > > Hope I can contribute somehow. Well, a standard part of running a software business is maintaining a customer support/bug database. GnuCash has one, with hundreds of reports in it (literally). Someone needs to go through them, and figure out if the bug has already been fixed, and if not, if there's enough information in there to reproduce it again, and finally, if its a high or low priority bug. Those that are fixed or cannot be reproduced need to be closed. This is called "triage". Note that most people (including probably yourself) will hate doing this kind of a task. Some people enjoy doing it. Try it, see if you like it. If you hate it, think of it as part of your MBA training: someone in a software company does this on a daily basis. --linas -- pub 1024D/01045933 2001-02-01 Linas Vepstas (Labas!) <[EMAIL PROTECTED]> PGP Key fingerprint = 8305 2521 6000 0B5E 8984 3F54 64A9 9A82 0104 5933 ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [PATCH] GNOME 2: HIGify welcome dialog.
On Sun, May 02, 2004 at 11:57:42PM -0700, David Hampton was heard to remark: > On Sun, 2004-05-02 at 07:31, Christian Neumair wrote: > > The attached patch aims to HIGify the welcome/new user dialog. > > What version of glade are you using to edit these files? There are a > bunch of properties there that my version of glade (2.0.1) doesn't know > about. Since neither debian nor fedora core have glade-2.4 in it, I think Christian could help us by providing instructions on how to get gnome-2.4/2.6 from source. Back in the 2.0 timeframe, there were some simple scripts to do this: you su - root; adduser gnome; su - gnome; run-some-script, and 12 hours and 1GB later you had all of gnome-2 compiled. Hopefully, there's something like this for the current version. --linas -- pub 1024D/01045933 2001-02-01 Linas Vepstas (Labas!) <[EMAIL PROTECTED]> PGP Key fingerprint = 8305 2521 6000 0B5E 8984 3F54 64A9 9A82 0104 5933 ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [PATCH] GNOME 2: HIGify welcome dialog.
[EMAIL PROTECTED] (Linas Vepstas) writes: > Since neither debian nor fedora core have glade-2.4 in it, I think > Christian could help us by providing instructions on how to get > gnome-2.4/2.6 from source. Since neither debian nor fedora core have glade-2.4 I would argue that gnucash SHOULD NOT BE USING IT! Reference the hell our users had when trying to build GnuCash 1.6 because Gnome-1.4 wasn't widely available in public releases. I'll repeat my statement again: We should LAG gnome releases by AT LEAST 6-9 months... Minimum. And indeed we should pick a "base distro" (I'd argue FC1 at this point) and make sure our code works on that distro. If we do not do this, we've done our users a major dis-service. > Back in the 2.0 timeframe, there were some simple scripts to do this: > you su - root; adduser gnome; su - gnome; run-some-script, > and 12 hours and 1GB later you had all of gnome-2 compiled. > Hopefully, there's something like this for the current version. I don't want to do this myself, let alone require our users to do this. GnuCash lost me as a developer for about 6 months during the pre-1.6 development because the tree moved to gnome-1.4 way too quickly. Let's not repeat that mistake. > --linas -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [PATCH] GNOME 2: HIGify welcome dialog.
On Sun, 2004-05-02 at 23:57 -0700, David Hampton wrote: > On Sun, 2004-05-02 at 07:31, Christian Neumair wrote: > > The attached patch aims to HIGify the welcome/new user dialog. > > What version of glade are you using to edit these files? There are a > bunch of properties there that my version of glade (2.0.1) doesn't know > about. These are glade 2.4-specific properties. You can use the attached script to fix those files (fixglade ). Note that you can remove the first regexp if a particular file contains GNOME-dependent widgets. regs, Chris fixglade Description: application/shellscript ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [PATCH] GNOME 2: HIGify welcome dialog.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 04 May 2004 11:09 am, Derek Atkins wrote: > I'll repeat my statement again: We should LAG gnome releases by AT > LEAST 6-9 months... Minimum. And indeed we should pick a "base > distro" (I'd argue FC1 at this point) and make sure our code works on > that distro. If we do not do this, we've done our users a major > dis-service. Well, gnome 2.4 has already been out for eight months now. By the time we release gnucash 2, it will have been out for over a year. I admit gnome 2.6 will be pushing it, but 2.4 (or later) is already part of FC1, Debian testing, Mandrake 10, and Suse 9.1. Then again since I did nothing for the Gnome 2 port, this opinion is worth little more than the electrons used to display it. - -- Benoit Grégoire, http://step.polymtl.ca/~bock/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAl8oFmZ6zzPlLuwMRAldaAKCBSnPbhCpiflI7vaLyUwYfFrijoQCeNeDp Kj8skpyLUpTUqHxSDw6QR1I= =poWE -END PGP SIGNATURE- ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [PATCH] GNOME 2: HIGify welcome dialog.
Benoit Grégoire <[EMAIL PROTECTED]> writes: > Well, gnome 2.4 has already been out for eight months now. By the time we It's only been out about six months, and most distros are only NOW being released with it > release gnucash 2, it will have been out for over a year. I admit gnome 2.6 > will be pushing it, but 2.4 (or later) is already part of FC1, Debian > testing, Mandrake 10, and Suse 9.1. No, 2.4 is NOT part of FC1: ls gtk2* gtk2-2.2.4-5.1.i386.rpm gtk2-devel-2.2.4-5.1.i386.rpm gtk2-engines-2.2.0-3.i386.rpm I think someone else said that FC2 has 2.6, but I haven't verified that myself. OTOH, FC2 hasn't been released, yet, either. So I still think we should focus on Gtk-2.2 > Then again since I did nothing for the Gnome 2 port, this opinion is worth > little more than the electrons used to display it. -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [PATCH] GNOME 2: HIGify welcome dialog.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 04 May 2004 01:00 pm, Derek Atkins wrote: > No, 2.4 is NOT part of FC1: > > ls gtk2* > gtk2-2.2.4-5.1.i386.rpm > gtk2-devel-2.2.4-5.1.i386.rpm > gtk2-engines-2.2.0-3.i386.rpm Err, gtk2-2.2.4 IS part of gnome 2.4, gtk2-2.4.0 was only just released (march 16, see http://www.gtk.org/) How about ls libgnome* ;) - -- Benoit Grégoire, http://step.polymtl.ca/~bock/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAl9FRmZ6zzPlLuwMRAjm1AJ9XL0GRLB/Bxqx/SfOc2OqR8WQJNgCeIAFb /GKjB0Cizrlb682vj2Zoq8M= =nxzr -END PGP SIGNATURE- ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [PATCH] GNOME 2: HIGify welcome dialog.
Just as a side note on this topic: I just installed SuSE 9.1 and tried to compile GnuCash (stable branch first). Almost all packages needed are included in the distribution, but they don't get installed by default. There is an installation option for full gnome and for developement, but apparently this installs gnome2 devel packages only. To compile GnuCash I had to install quite a few gnome devel packages manually. Guppi is not included in SuSE 9.1. There are Guppi DLLs in the GnuCash 1.8.8 package that comes with SuSE 9.1 but no guppi-devel. OK, I compiled this from source like I did in the old 1.6 days ... There was another problem with slib: slib comes as version 3a1 and caused a compilation error. I installed 2d4 and this worked fine. gtk2 on SuSE 9.1 is version 2.2.4. I am a little concerned about the missing guppi. We should have a gnome 2 GnuCash ready when major distibutions drop more of gnome 1 support ... Herbert. Benoit Grégoire schrieb: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tuesday 04 May 2004 11:09 am, Derek Atkins wrote: > > I'll repeat my statement again: We should LAG gnome releases by AT > > LEAST 6-9 months... Minimum. And indeed we should pick a "base > > distro" (I'd argue FC1 at this point) and make sure our code works on > > that distro. If we do not do this, we've done our users a major > > dis-service. > > Well, gnome 2.4 has already been out for eight months now. By the time we > release gnucash 2, it will have been out for over a year. I admit gnome 2.6 > will be pushing it, but 2.4 (or later) is already part of FC1, Debian > testing, Mandrake 10, and Suse 9.1. > > Then again since I did nothing for the Gnome 2 port, this opinion is worth > little more than the electrons used to display it. > > - -- > Benoit Grégoire, http://step.polymtl.ca/~bock/ > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.2.4 (GNU/Linux) > > iD8DBQFAl8oFmZ6zzPlLuwMRAldaAKCBSnPbhCpiflI7vaLyUwYfFrijoQCeNeDp > Kj8skpyLUpTUqHxSDw6QR1I= > =poWE > -END PGP SIGNATURE- > > ___ > gnucash-devel mailing list > [EMAIL PROTECTED] > https://lists.gnucash.org/mailman/listinfo/gnucash-devel -- Herbert Thoma Group Manager Video Multimedia Realtime Systems Department Fraunhofer IIS Am Wolfsmantel 33, 91058 Erlangen, Germany Phone: +49-9131-776-323 Fax: +49-9131-776-399 email: [EMAIL PROTECTED] www: http://www.iis.fhg.de/ ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [PATCH] GNOME 2: HIGify welcome dialog.
Benoit Grégoire <[EMAIL PROTECTED]> writes: > On Tuesday 04 May 2004 01:00 pm, Derek Atkins wrote: >> No, 2.4 is NOT part of FC1: >> >> ls gtk2* >> gtk2-2.2.4-5.1.i386.rpm >> gtk2-devel-2.2.4-5.1.i386.rpm >> gtk2-engines-2.2.0-3.i386.rpm > > Err, gtk2-2.2.4 IS part of gnome 2.4, gtk2-2.4.0 was only just released (march > 16, see http://www.gtk.org/) > > How about ls libgnome* ;) GRR.. I HATE GNOME'S STUPID numbering scheme. WTF does gtk+'s release numbers lag behind the GNOME release numbers??? Yes, libgnome is 2.4... libgnome-2.4.0-1.i386.rpm libgnome-devel-2.4.0-1.i386.rpm libgnomecanvas-2.4.0-1.i386.rpm ... So I guess this means we can depend on Gnome-2.4/Gtk-2.2. > Benoit Grégoire, http://step.polymtl.ca/~bock/ -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [PATCH] GNOME 2: HIGify welcome dialog.
Herbert Thoma <[EMAIL PROTECTED]> writes: > Just as a side note on this topic: > > I just installed SuSE 9.1 and tried to compile GnuCash (stable branch first). > Almost all packages needed are included in the distribution, but they don't > get installed by default. There is an installation option for full gnome and > for developement, but apparently this installs gnome2 devel packages only. That is unfortunate. > To compile GnuCash I had to install quite a few gnome devel packages manually. > Guppi is not included in SuSE 9.1. There are Guppi DLLs in the GnuCash 1.8.8 > package that comes with SuSE 9.1 but no guppi-devel. Yes, SuSE decided to build guppi inside the gnucash package. Don't ask me why. Ask them. > OK, I compiled this >>From source like I did in the old 1.6 days ... There was another problem > with slib: slib comes as version 3a1 and caused a compilation error. I > installed 2d4 and this worked fine. The slib3 issue should be fixed in 1.8.9. > gtk2 on SuSE 9.1 is version 2.2.4. I am a little concerned about the missing > guppi. We should have a gnome 2 GnuCash ready when major distibutions drop > more of gnome 1 support ... Preaching the choir. We're working on the g2 port. We need help. Send patches to help get it completed. > Herbert. -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [PATCH] GNOME 2: HIGify welcome dialog.
On Tue, 2004-05-04 at 10:00, Derek Atkins wrote: > Benoit Grégoire <[EMAIL PROTECTED]> writes: > > release gnucash 2, it will have been out for over a year. I admit gnome 2.6 > > will be pushing it, but 2.4 (or later) is already part of FC1, Debian > > testing, Mandrake 10, and Suse 9.1. Debian testing and unstable both have gtk 2.2.4 and gnome 2.4. Debian experimental has gtk 2.4 and gnome 2.6 > No, 2.4 is NOT part of FC1: > > ls gtk2* > gtk2-2.2.4-5.1.i386.rpm > gtk2-devel-2.2.4-5.1.i386.rpm > gtk2-engines-2.2.0-3.i386.rpm > > I think someone else said that FC2 has 2.6 FC2 has gtk 2.4 and gnome 2.6. > but I haven't verified that > myself. OTOH, FC2 hasn't been released, yet, either. So I still think > we should focus on Gtk-2.2 FC2 is scheduled to release in two weeks. As much as I'd like to use the gtk-2.4 widget set and eliminate the egg directory, I can't quite justify it at this point. I may have a different answer three months from now. David signature.asc Description: This is a digitally signed message part ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [PATCH] GNOME 2: HIGify welcome dialog.
On Tue, 2004-05-04 at 09:15, Christian Neumair wrote: > On Sun, 2004-05-02 at 23:57 -0700, David Hampton wrote: > > On Sun, 2004-05-02 at 07:31, Christian Neumair wrote: > > > The attached patch aims to HIGify the welcome/new user dialog. > > > > What version of glade are you using to edit these files? There are a > > bunch of properties there that my version of glade (2.0.1) doesn't know > > about. > > These are glade 2.4-specific properties. You can use the attached script > to fix those files (fixglade ). Note that you can remove the first > regexp if a particular file contains GNOME-dependent widgets. Running glade-2 locally on the files solves the problem as well. I wanted to make sure I wasn't losing any important information by doing so. David signature.asc Description: This is a digitally signed message part ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
[PATCH] GNOME 2: Make register cursor re-appear
Subject says it all. I don't think we need a PangoRectangle pointer, so
I replaced it by a plain PangoRectangle.
regs,
Chris
Index: src/register/register-gnome/gnucash-item-edit.c
===
RCS file: /home/cvs/cvsroot/gnucash/src/register/register-gnome/gnucash-item-edit.c,v
retrieving revision 1.1.6.6
diff -u -r1.1.6.6 gnucash-item-edit.c
--- src/register/register-gnome/gnucash-item-edit.c 1 Oct 2003 02:29:07 - 1.1.6.6
+++ src/register/register-gnome/gnucash-item-edit.c 4 May 2004 18:41:38 -
@@ -81,7 +81,7 @@
gboolean hatching;
- PangoRectangle *cursor;
+ PangoRectangle cursor;
};
@@ -213,8 +213,8 @@
break;
}
- pango_layout_get_cursor_pos (info->layout, cursor_pos, NULL, &strong_pos);
- info->cursor = &strong_pos;
+ pango_layout_get_cursor_pos (info->layout, cursor_pos, &strong_pos, NULL);
+ info->cursor = strong_pos;
if (info->hatching)
{
@@ -275,8 +275,12 @@
info.text_rect.y + 1,
info.layout);
- gdk_draw_line (drawable, item_edit->gc, info.cursor->x, info.cursor->y,
- info.cursor->x, info.cursor->y + info.cursor->height);
+ gdk_draw_line (drawable,
+ item_edit->gc,
+ info.cursor.x / PANGO_SCALE + CELL_HPADDING,
+ info.cursor.y / PANGO_SCALE + 1,
+ info.cursor.x / PANGO_SCALE + CELL_HPADDING,
+ info.cursor.height / PANGO_SCALE);
gdk_gc_set_clip_rectangle (item_edit->gc, NULL);
___
gnucash-devel mailing list
[EMAIL PROTECTED]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: QOF help!
On Monday 03 May 2004 11:15, Derek Atkins wrote: > Neil Williams <[EMAIL PROTECTED]> writes: > > On Monday 03 May 2004 4:07, you wrote: > >> In theory, the docs should auto build with doxygen > >> I think you need to > >> configure --enable-doxygen or --enable-dot > Uh, did you try "make doc"? Ok, for some reason I thought configure would add doc to the target list. Makefiles are still unfamiliar. Done now. The documentation produced, is there a problem with hosting it somewhere? (If I keep it updated from CVS)? I've got the space to host it, if you'd like, although somewhere on gnucash.org would be more intuitive it would force the update burden onto someone else. > > I'll keep writing some documentation as I go, using docbook. It may turn > > out to be useful for others. > > That's extremely UN-USEFUL. As Linas suggested can you please write > docs in doxygen format in the header files and submit patches to the > headers? The big advantage with doxygen is the links from one typedef to another. I'll include doxygen compatible info in the files, certainly, but most of the docbook stuff is for my own reference and has a different emphasis to the doxygen output. It's not primarily for project use, although it may still turn out to be useful. e.g. if this information had been readily accessible when I started thinking about the merge facility, it would have made my life easier. If it helps anyone else get a start in a large project, especially someone like me whose degree isn't in computer programming/science, I don't see the harm - considering I'll be writing it anyway for my own use. I can be far more expansive in docbook and the docbook itself doesn't have to be packaged with the code. Off to learn about doxygen now, adding to GTK, Glib, QOF, and automake. I may as well say this now, I'm NOT going to be able to learn Scheme as well! I'll need help with the GUI dialogs etc. Plenty of time yet though. :-) -- Neil Williams = http://www.codehelp.co.uk/ http://www.dclug.org.uk/ http://www.isbn.org.uk/ http://sourceforge.net/projects/isbnsearch/ http://www.biglumber.com/x/web?qs=0x8801094A28BCB3E3 pgp0.pgp Description: signature ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Wiki
Actually, I've got experience of setting up and working with Wikis and the gnucash.org site mentions using a Wiki as a possible development aid. What's the feeling about me combining the doxygen output and creating the Wiki - preferably on gnucash.org - I don't mind. I also write search engines for mailing list archives (just something to while away the time while gnucash compiles) and I've got a few stock ones that I can adapt, one in Perl and one in PHP (prefer PHP). So I could help with: http://www.gnucash.org/en/state_of_the_gnucash_project.phtml Make sure the mailing lists are easily searchable Get more people write access to the website Quickly implement a Wiki or similar system I'll be updating the doxygen output anyway, a Wiki doesn't take a lot to set up, particularly one based in PHP and MySQL, and I can probably sort out a search engine in PHP or Perl. The Wiki and the search engine are one-off tasks (with the odd bug-fix from time to time) and not ongoing development, (because they can be made time-aware so that new archives are automatically made available to the search) and doxygen is a required part of the merge facility anyway. Is that useful? -- Neil Williams = http://www.codehelp.co.uk/ http://www.dclug.org.uk/ http://www.isbn.org.uk/ http://sourceforge.net/projects/isbnsearch/ http://www.biglumber.com/x/web?qs=0x8801094A28BCB3E3 pgp0.pgp Description: signature ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Wiki
Hi, Neil Williams <[EMAIL PROTECTED]> writes: > Actually, I've got experience of setting up and working with Wikis and the > gnucash.org site mentions using a Wiki as a possible development aid. > > What's the feeling about me combining the doxygen output and creating the Wiki > - preferably on gnucash.org - I don't mind. We've already got access to a Wiki. We've been using the GnomeSupport Wiki. For example, the FAQ is at: http://gnomesupport.org/wiki/index.php/GnuCashFrequentlyAskedQuestions And we've got a bunch of other GnuCash wiki pages there. > I also write search engines for mailing list archives (just something to while > away the time while gnucash compiles) and I've got a few stock ones that I > can adapt, one in Perl and one in PHP (prefer PHP). This we could do... In particular if you can search pipermail archives directly (so you don't need to keep your own copy of the archives in the search engine). > So I could help with: > > http://www.gnucash.org/en/state_of_the_gnucash_project.phtml > Make sure the mailing lists are easily searchable This is useful. > Get more people write access to the website This is hard for a number of reasons I don't want to get into right now. > Quickly implement a Wiki or similar system This is already there (although not at GnuCash.org). > I'll be updating the doxygen output anyway, a Wiki doesn't take a lot to set > up, particularly one based in PHP and MySQL, and I can probably sort out a > search engine in PHP or Perl. updating doxygen is still useful. > The Wiki and the search engine are one-off tasks (with the odd bug-fix from > time to time) and not ongoing development, (because they can be made > time-aware so that new archives are automatically made available to the > search) and doxygen is a required part of the merge facility anyway. > > Is that useful? Some, definitely! -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: QOF help!
Neil Williams <[EMAIL PROTECTED]> writes: > The documentation produced, is there a problem with hosting it somewhere? (If > I keep it updated from CVS)? I've got the space to host it, if you'd like, > although somewhere on gnucash.org would be more intuitive it would force the > update burden onto someone else. Good question. I could easily host it on cvs.gnucash.org. I could even automate its generation, like a nightly cron job to checkout cvs and build the docs. But that would presume that "cvs.gnucash.org" is the place to put them and not "www.gnucash.org". >> > I'll keep writing some documentation as I go, using docbook. It may turn >> > out to be useful for others. >> >> That's extremely UN-USEFUL. As Linas suggested can you please write >> docs in doxygen format in the header files and submit patches to the >> headers? > > The big advantage with doxygen is the links from one typedef to another. I'll > include doxygen compatible info in the files, certainly, but most of the > docbook stuff is for my own reference and has a different emphasis to the > doxygen output. IMHO doxygen should be the ONLY place for API documentation. However if you want to provide usage examples, or architectural documentation, docbook would definitely be a reasonable thing. > It's not primarily for project use, although it may still > turn out to be useful. e.g. if this information had been readily accessible > when I started thinking about the merge facility, it would have made my life > easier. If it helps anyone else get a start in a large project, especially > someone like me whose degree isn't in computer programming/science, I don't > see the harm - considering I'll be writing it anyway for my own use. I can be > far more expansive in docbook and the docbook itself doesn't have to be > packaged with the code. I guess it depends what you want in said documentation. If it's descriptions of the API calls, IMHO this belongs completely in doxygen. > Off to learn about doxygen now, adding to GTK, Glib, QOF, and automake. I may > as well say this now, I'm NOT going to be able to learn Scheme as well! I'll > need help with the GUI dialogs etc. Plenty of time yet though. > :-) The GUI stuff is easy. Run "glade" and build the GUI. :) As for scheme -- you don't NEED scheme for most things, so don't worry about it. -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: QOF help!
On Tue, 2004-05-04 at 17:41, Derek Atkins wrote: > IMHO doxygen should be the ONLY place for API documentation. > However if you want to provide usage examples, or architectural > documentation, docbook would definitely be a reasonable thing. I'd push for most instances of this type of documentation to be in doxygen, as well... the closer to the code it is, the higher probability that it'll actually get maintained in the face of change... ...jsled -- http://www.asynchronous.org/ - `a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED] # A: Because it breaks the flow of normal conversation. # Q: Why don't we put the response before the request? ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: QOF help!
Josh Sled <[EMAIL PROTECTED]> writes: > On Tue, 2004-05-04 at 17:41, Derek Atkins wrote: > >> IMHO doxygen should be the ONLY place for API documentation. >> However if you want to provide usage examples, or architectural >> documentation, docbook would definitely be a reasonable thing. > > I'd push for most instances of this type of documentation to be in > doxygen, as well... the closer to the code it is, the higher probability > that it'll actually get maintained in the face of change... I'm not sure how to use doxygen for architectural docs... Could you provide an example or pointers to docs that describe it? > ...jsled -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Wiki
On Tuesday 04 May 2004 10:31, Derek Atkins wrote: > Hi, > > I also write search engines for mailing list archives (just something to > > while away the time while gnucash compiles) and I've got a few stock ones > > that I can adapt, one in Perl and one in PHP (prefer PHP). > > This we could do... In particular if you can search pipermail archives > directly (so you don't need to keep your own copy of the archives in > the search engine). The archives are in a sub-domain of gnucash.org but how is that configured? I can definitely search any publicly accessible HTML content from any site with no local cache, it all depends on the speed of access. A simple pattern match on --beginarticle-- and --endarticle-- can be used to limit searches to the relevant content. All pages carry a link to the next message and you don't want the subject line to cause that message to show up in a search for content that relates to the content of the linked message. For an example, take a look at DCLUG: http://www.dclug.org.uk/archive/ This is a MHonArc archive built from a mailing list of similar volume to gnucash-devel where the archive is stored on the local filesystem. Speed is obviously relative to the hardware available and I'd tailor the script to try to make best use of the available performance. The archive script is time-aware so that it automatically generates links as each new archive is created. > We've already got access to a Wiki. We've been using the GnomeSupport > Wiki. For example, the FAQ is at: > > http://gnomesupport.org/wiki/index.php/GnuCashFrequentlyAskedQuestions > > And we've got a bunch of other GnuCash wiki pages there. Is that linked from the www.gnucash.org home page? Should this page be updated? http://www.gnucash.org/en/state_of_the_gnucash_project.phtml > > So I could help with: > > > > http://www.gnucash.org/en/state_of_the_gnucash_project.phtml > > Make sure the mailing lists are easily searchable > > This is useful. I can do this tomorrow. All I need is access - SSH or FTP, I can do the scripts in PHP. If you can let me know how to access the location for the script(s) by tomorrow morning GMT, I'll work on it straight away. (Feel free to encrypt any access instructions). With regard to: http://www.gnucash.org/en/contribute.phtml We even need someone to make sure that the mail archives are running correctly, and that recent mail is getting indexed & is searchable. (webmaster selected) Is that bit about checking the operation of the mail archives still a problem? From only a casual use of the archive, recent messages seem to be added very quickly. The 'searchable' I can solve for you. -- Neil Williams = http://www.codehelp.co.uk/ http://www.dclug.org.uk/ http://www.isbn.org.uk/ http://sourceforge.net/projects/isbnsearch/ http://www.biglumber.com/x/web?qs=0x8801094A28BCB3E3 pgp0.pgp Description: signature ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: QOF help!
On Tuesday 04 May 2004 10:41, Derek Atkins wrote: > Neil Williams <[EMAIL PROTECTED]> writes: > > The documentation produced, is there a problem with hosting it somewhere? > > (If I keep it updated from CVS)? I've got the space to host it, if you'd > > like, although somewhere on gnucash.org would be more intuitive it would > > force the update burden onto someone else. > > Good question. I could easily host it on cvs.gnucash.org. I could > even automate its generation, like a nightly cron job to checkout cvs > and build the docs. But that would presume that "cvs.gnucash.org" is > the place to put them and not "www.gnucash.org". Can't it simply be linked into www.gnucash.org using a symbolic link or NFS etc.? What's the design of the various sub-domains? (off-list if you like - I'll need to know about the list vs www domains for the search engine). BTW. Why DOES list link to a https:// self-signed server? I can't figure out what is gained by encrypting the connection to archived content of a public mailing list. As long as it's clearly linked from the 'Developer Information' list of links on the home page, does it even matter if it's in the cvs subdomain? It might help people who don't know doxygen to realise the link between code and docs. A lot of other sites have static documentation, the idea that doxygen puts the generation date into the pages should reassure new developers that the docs really do relate to the CVS code that they are looking through. The use of the same sub-domain would reinforce that and give a very positive impression of the docs themselves. There is nothing worse than API documentation that is behind the C. (A limitation of docbook of which I am well aware, even though I like docbook.) > > The big advantage with doxygen is the links from one typedef to another. > > I'll include doxygen compatible info in the files, certainly, but most of > > the docbook stuff is for my own reference and has a different emphasis to > > the doxygen output. > > IMHO doxygen should be the ONLY place for API documentation. > However if you want to provide usage examples, or architectural > documentation, docbook would definitely be a reasonable thing. Exactly my plan, even though I had some C listings in the first draft, I knew it would be of limited use compared to the rest of the content. > I guess it depends what you want in said documentation. If it's > descriptions of the API calls, IMHO this belongs completely in doxygen. Yes, from what I've learnt so far, it does this very well. > > Off to learn about doxygen now, adding to GTK, Glib, QOF, and automake. I > > may as well say this now, I'm NOT going to be able to learn Scheme as > > well! I'll need help with the GUI dialogs etc. Plenty of time yet though. > > > > :-) > > The GUI stuff is easy. Run "glade" and build the GUI. :) > As for scheme -- you don't NEED scheme for most things, so don't > worry about it. Phew! :-) -- Neil Williams = http://www.codehelp.co.uk/ http://www.dclug.org.uk/ http://www.isbn.org.uk/ http://sourceforge.net/projects/isbnsearch/ http://www.biglumber.com/x/web?qs=0x8801094A28BCB3E3 pgp0.pgp Description: signature ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Wiki
Neil Williams <[EMAIL PROTECTED]> writes: > The archives are in a sub-domain of gnucash.org but how is that configured? Right now there are two machines that have gnucash.org addresses (there are no subdomains, just hostnames in the gnucash.org domain): machine1 is "gnucash.org", "www.gnucash.org", and "mail.gnucash.org" machine2 is "cvs.gnucash.org" and "lists.gnucash.org" We've got an MX record set up so mail prefers machine1, then machine1 (and then linas' machine). So, mail should go to the list server unless it's down, in which case it'll get queued on one of the other machines and then sent to the list server when it's available. machine1 is in Texas, machine2 is in Massachusetts. There is no special network between them, no VPN, no NFS. So you cannot assume that machine1 can access data on machine2 or machine2 can access data on machine1 except through the same public interfaces that anyone else can use. > I can definitely search any publicly accessible HTML content from any site with > no local cache, it all depends on the speed of access. A simple pattern match > on --beginarticle-- and --endarticle-- can be used to limit searches to the > relevant content. All pages carry a link to the next message and you don't > want the subject line to cause that message to show up in a search for > content that relates to the content of the linked message. Sure, but how does this work with a pipermail archive? How do you index it? Obviously putting it onto the archive server would be the best solution, IMHO, to allow easy indexing. > For an example, take a look at DCLUG: > http://www.dclug.org.uk/archive/ > This is a MHonArc archive built from a mailing list of similar volume to > gnucash-devel where the archive is stored on the local filesystem. Speed is > obviously relative to the hardware available and I'd tailor the script to try > to make best use of the available performance. The archive script is > time-aware so that it automatically generates links as each new archive is > created. We use pipermail archives. We don't have the original mbox archives for most of our data (they were destroyed a year or so ago). Any solution we have needs to deal with pipermail and must index the individual article HTML files. >> We've already got access to a Wiki. We've been using the GnomeSupport >> Wiki. For example, the FAQ is at: >> >> http://gnomesupport.org/wiki/index.php/GnuCashFrequentlyAskedQuestions >> >> And we've got a bunch of other GnuCash wiki pages there. > > Is that linked from the www.gnucash.org home page? Yes. See "FAQ" in the menu. However there is no "wiki" link per se. > Should this page be updated? > http://www.gnucash.org/en/state_of_the_gnucash_project.phtml Oh, probably. >> > So I could help with: >> > >> > http://www.gnucash.org/en/state_of_the_gnucash_project.phtml >> > Make sure the mailing lists are easily searchable >> >> This is useful. > > I can do this tomorrow. All I need is access - SSH or FTP, I can do the > scripts in PHP. If you can let me know how to access the location for the > script(s) by tomorrow morning GMT, I'll work on it straight away. (Feel free > to encrypt any access instructions). You could just email me the scripts and I can install them. Let me know what other information you need. No offence, but right now not even the developers have shell access to the server. > With regard to: > http://www.gnucash.org/en/contribute.phtml > We even need someone to make sure that the mail archives are running > correctly, and that recent mail is getting indexed & is searchable. > (webmaster selected) > > Is that bit about checking the operation of the mail archives still a problem? > From only a casual use of the archive, recent messages seem to be added very > quickly. The 'searchable' I can solve for you. No, it is not a problem any more. The lists are running fine, and the archives are running fine. -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: QOF help!
Neil Williams <[EMAIL PROTECTED]> writes: > Can't it simply be linked into www.gnucash.org using a symbolic link or NFS > etc.? What's the design of the various sub-domains? (off-list if you like - > I'll need to know about the list vs www domains for the search engine). Yes, there could be an HTTP link from www.gnucash.org, but not via NFS (See my previous message). There *IS* an http server on both machines. Machine2 (cvs,lists) hosts cvsweb and mailman/pipermail (the latter being the list archives). Right now machine1 (www) has very limited disk space (at least until Linas upgrades his machine). Machine2 is also SIGNIFICANTLY faster! So, in terms of performance and disk space, using machine2 is the much better option (also, it's the one I maintain ;) However it means it's not at www.gnucash.org. > BTW. Why DOES list link to a https:// self-signed server? I can't figure out > what is gained by encrypting the connection to archived content of a public > mailing list. Because I configured it that way. Personally I'd prefer if *EVERYTHING* were encrypted, but Can only have one SSL config per IP address, and I didn't want to use multiple IP Addresses.. I guess I could have done so, but it would've been more work. FTR, it'll work with either HTTP or HTTPS. It just defaults to HTTPS -- because I like it that way. > As long as it's clearly linked from the 'Developer Information' list of links > on the home page, does it even matter if it's in the cvs subdomain? It might > help people who don't know doxygen to realise the link between code and docs. > A lot of other sites have static documentation, the idea that doxygen puts > the generation date into the pages should reassure new developers that the > docs really do relate to the CVS code that they are looking through. The use > of the same sub-domain would reinforce that and give a very positive > impression of the docs themselves. As I said in my previous email, there are no subdomains. There is one domain (gnucash.org) with multiple hosts (.,www,cvs,lists,mail). As for "does it matter?", well, that was my question. I don't know if it matters, but I do not want to unilaterally make that decision. IMHO it would be "easier" for the docs to be generated on the same machine where the cvs archives are kept. It's a local matter to update the tree, so there's no network usage, and that machine is significantly more powerful. But I agree with you.. Having the docs live at http://cvs.gnucash.org/... is just fine, so long as there's a link off the main gnucash site. Linas may not agree, however, if he wants to keep the "gnucash look at feel" of the docs. But I don't know how hard that would be to get doxygen to use SSI. It might be easier with frames. > There is nothing worse than API documentation that is behind the C. What do you mean by "behind the C"? I assume you mean "documentation that lags the implementation?" If so, then yes, I agree completely. -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
discussion re: libgoffice scheduling
I wanted to relay the following conversation I had, earlier, with Jody f/ Gnumeric regarding the split-out _from_ Gnumeric of what's being called libgoffice. It'll include stuff like toolbar foreground/background-color selection, font-selection, &c... all sorts of standard-office-app "stuff". The most important part for gnucash is, specifically, the GnomeOffice Graphing [GOG] stuff... In summary: it looks like it'll be a while [~weeks] before the relevant code is sufficiently split out of gnumeric to be even copied into the gnucash source tree, and a while after that before the library is released, let alone started to be included in distros; he's targeting a 6/25 "release" of libgoffice. jody: question re: libgoffice/gog. Any 1-line status update on it? And what's the best way to monitor it's progress so I don't need to bug you. s/.$/?/ jsled: progress is being made I've got GODocument and GODocumentControl in my tree now and have ported gnumeric to that that gives me a place to hang to plugins and importers/exporters target is to make the split for 1.4 jsled: it will include show/hide toolbar and fullscreen support to start with jody: followup question about libgoffice. It sounds like there's a bunch of stuff in it that gnucash doesn't care about at the moment. Frankly, we're probably going to copy the gog sources into the gnucash tree for the initial G2 port/release, anyways. jsled: there will be some things in there that it may not care about jsled: I'd ask that you not do that I'm happy to work with you to ensure we release on a schedule that is convenient hmm. you can ask, but we're pretty serious about not depending on stuff that's hasn't been in distributions for 6-9 months. We're currently talking about making FC1 our base/ref. platform. Or _maybe_ making it FC2. regardless, how long before libgoffice is going to be in out in the field? jsled: before june 25 aka guadec Sorry ... a bit of a rhetorical question. The point being that there's no realistic alternative for our needs besides GOG, but we're hoping to get the g2 port out the door before ... 2004.06.25 + 6m => 2004.12.25. Now. I'm not sure that we _will_ do that, but we can only hope for the best. :) * jody scratches head At this point the code is not seperable from gnumeric It still uses the plugins and format/parsing engine both need to move down * jsled nods It is also based on gtk-2.4 * jsled nods * jody apologizes for that but there are not alot of choices Well, so are we at this point... we've moved a good chunk of 2.4 into our source tree as well. :/ we'd already had libegg in there, and I've moved a bit more which has showed up in gtk-2.4.0... You're going to mix 2.4 code with 2.2 libraries ? yes. brave heh. What's your primary concern with copying the gog code into the gnc tree? general in-elegance, or...? Limited developer resources eh? bugs and api requests will definitely occur for what is basicly the first major user of the code outside of gnumeric having those appear against an out of date version hmm. or worse, get fixed there and potentially not get upstreamed ... yes. point well taken; we will take care to find a way to prevent that. Where is your cvs hosted ? cvs.gnucash.org -- private box in MA. If it's on gnome.org you could do a virtual module include svu: I'm nost sure what the question is ? a solution might be for the developers / early testers to actually develop against libgoffice ... but then cut-off a version when we're nearing the end of our dev/release cycle. there will undoubtedly be bugs after that, but we'd be a better position to manage the patches then. In any case, we'll have to deal with that at some point in the future... but will keep it in mind. jody: permission to copy this conversation to the other primary GnuCash developers? jsled: sure, and I'll extend an invitation to get cvs hosted on gnome.org which would simplify importing things easily ...jsled -- http://www.asynchronous.org/ - `a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED] # A: Because it breaks the flow of normal conversation. # Q: Why don't we put the response before the request? ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: QOF help!
On Tue, 2004-05-04 at 17:50, Derek Atkins wrote: > I'm not sure how to use doxygen for architectural docs... Could you > provide an example or pointers to docs that describe it? http://www.stack.nl/~dimitri/doxygen/commands.html Using \defgroup , \addtogroup , \example , \mainpage and \file , and a bit of convention, one could build higher-level structural docs along-side the lower level file/function/variable docs. ...jsled -- http://www.asynchronous.org/ - `a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED] # A: Because it breaks the flow of normal conversation. # Q: Why don't we put the response before the request? ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: discussion re: libgoffice scheduling
My personal feelings: 1) we don't want to use gnome cvs for multiple reasons: - they don't limit developer access to different modules, - we've already got our system set up - we can control our system, cvsweb, etc. 2) I think with regard to GOG that we should snapshot his code into once he's got something we can use, and then we just keep our snapshot up to date from his CVS/releases periodically (and make ABSOLUTELY sure to feed changes we make back up to jody) -derek Josh Sled <[EMAIL PROTECTED]> writes: > I wanted to relay the following conversation I had, earlier, with Jody > f/ Gnumeric regarding the split-out _from_ Gnumeric of what's being > called libgoffice. It'll include stuff like toolbar > foreground/background-color selection, font-selection, &c... all sorts > of standard-office-app "stuff". The most important part for gnucash is, > specifically, the GnomeOffice Graphing [GOG] stuff... > > In summary: it looks like it'll be a while [~weeks] before the relevant > code is sufficiently split out of gnumeric to be even copied into the > gnucash source tree, and a while after that before the library is > released, let alone started to be included in distros; he's targeting a > 6/25 "release" of libgoffice. > > > jody: question re: libgoffice/gog. > Any 1-line status update on it? And what's the best way to monitor it's > progress so I don't need to bug you. > s/.$/?/ > jsled: progress is being made > I've got GODocument and GODocumentControl in my tree now and have ported > gnumeric to that > that gives me a place to hang to plugins and importers/exporters > target is to make the split for 1.4 > jsled: it will include show/hide toolbar and fullscreen support to start with > jody: followup question about libgoffice. It sounds like there's a bunch of > stuff in it that gnucash doesn't care about at the moment. > Frankly, we're probably going to copy the gog sources into the gnucash tree > for the initial G2 port/release, anyways. > jsled: there will be some things in there that it may not care about > jsled: I'd ask that you not do that > I'm happy to work with you to ensure we release on a schedule that is > convenient > hmm. you can ask, but we're pretty serious about not depending on stuff > that's hasn't been in distributions for 6-9 months. > We're currently talking about making FC1 our base/ref. platform. > Or _maybe_ making it FC2. > regardless, how long before libgoffice is going to be in out in the field? > jsled: before june 25 > aka guadec > Sorry ... a bit of a rhetorical question. The point being that there's no > realistic alternative for our needs besides GOG, but we're hoping to get the g2 port > out the door before ... > 2004.06.25 + 6m => 2004.12.25. > Now. I'm not sure that we _will_ do that, but we can only hope for the > best. :) > * jody scratches head > At this point the code is not seperable from gnumeric > It still uses the plugins and format/parsing engine > both need to move down > * jsled nods > It is also based on gtk-2.4 > * jsled nods > * jody apologizes for that but there are not alot of choices > Well, so are we at this point... we've moved a good chunk of 2.4 into our > source tree as well. :/ > we'd already had libegg in there, and I've moved a bit more which has showed > up in gtk-2.4.0... > You're going to mix 2.4 code with 2.2 libraries ? > yes. > brave > heh. > What's your primary concern with copying the gog code into the gnc tree? > general in-elegance, or...? > Limited developer resources > eh? > bugs and api requests will definitely occur for what is basicly the first > major user of the code outside of gnumeric > having those appear against an out of date version > hmm. > or worse, get fixed there and potentially not get upstreamed ... > yes. > point well taken; we will take care to find a way to prevent that. > Where is your cvs hosted ? > cvs.gnucash.org -- private box in MA. > If it's on gnome.org you could do a virtual module include > svu: I'm nost sure what the question is ? > a solution might be for the developers / early testers to actually develop > against libgoffice ... but then cut-off a version when we're nearing the end of our > dev/release cycle. > there will undoubtedly be bugs after that, but we'd be a better position to > manage the patches then. > In any case, we'll have to deal with that at some point in the future... but > will keep it in mind. > jody: permission to copy this conversation to the other primary GnuCash > developers? > jsled: sure, and I'll extend an invitation to get cvs hosted on gnome.org > which would simplify importing things easily > > > ...jsled > > -- > http://www.asynchronous.org/ - `a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED] > # A: Because it breaks the flow of normal conversation. > # Q: Why don't we put the response before the request? > ___ > gnucash-devel
