Re: Gnome Programming App Development Theory Practice
On Mon, 2004-04-19 at 21:02, Biju Chacko wrote: I don't know if this will help any, but the GNU Enterprise project (www.gnue.org) seem to have achieved something on similar lines to what you are describing. I don't think that they conciously decided to come up with a declaratory language for form descriptions, but nevertheless seem to have devised one. What we are doing is fairly similar. We some what conciously came up with a declaratory language in our GNUe Forms definition. However, it seems to require a fair amount of procedural code to do anything non-trivial. I think your bar is too high then. I consider being able make a master/detail relationship form that allows me to adhoc query select, insert, update and delete without writing a line of code to be non-trivial. Now to add a bunch of rules yes you need procedural code, but I see no real way around that. Linas I believe continues to dismiss GNUe because he doesn't like Python. That is of course my humble opinion. -- Derek Neighbors GNU Enterprise http://www.gnuenterprise.org [EMAIL PROTECTED] Was I helpful? Let others know: http://svcs.affero.net/rm.php?r=dneighbo signature.asc Description: This is a digitally signed message part ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
ALMOST WORKING: quickbooks to iif to qif to gnucash
Hello all: I feel I'm close to having a Quickbooks to GnuCash conversion process completed (I'll post the recipe if I can make it work all the way). Right now I have a python script that is reading IIF format and generating QIF (see attached files). When I import the QIF into GnuCash (1.8.8 debian sarge), in the next druid page after QIF file selection, it says: The QIF file you have loaded appears to have transactions for just one account, but the file does not specify a name for that account. The default choice for the attached files is 'input'. The rest of the import proceeds without incidence. When it is finished I have a file with an 'input' account, when I would have thought I would have a '1st Bank Checking' account. Do I need to separate my big QIF file into separate files for all accounts that occur in the 'L' field? Or do I specify an specific account with a '!Account' record entry in the QIF? Or (most likely) have I missed some important aspect of QIF generation or GNUcash importing? I suspect either of the first two answers are as much work to implement in my python script, I'm just looking for a little direction from the people in the know. TIA PS: please cross-reply to me, as I have not subscribed to the lists (yet). -- Keith Hellman #include disclaimer.h [EMAIL PROTECTED]from disclaimer import standard public key @ www.mcprogramming.com Mod me down, and I will become more powerful than you can possibly imagine. -- Gothmolly http://slashdot.org/comments.pl?sid=103730cid=8837481 !TRNS TRNSID TRNSTYPEDATEACCNT NAMEAMOUNT DOCNUM CLEAR MEMO !SPLSPLID TRNSTYPEDATEACCNT NAMEAMOUNT DOCNUM MEMO PAYMETH INVITEM QNTYPRICE EXTRA !ENDTRNS TRNSDEPOSIT 03/24/2001 1st Bank Checking67.50 MDEP Y SPL DEPOSIT 03/24/2001 Untaxed Income:Jeffco Milage -63.50 SPL DEPOSIT 03/24/2001 Untaxed Income:Refunds -4.00 ENDTRNS !Type:Bank D03/24/2001 T67.50 NMDEP CR L1st Bank Checking SUntaxed Income:Jeffco Milage $-63.50 SUntaxed Income:Refunds $-4.00 ^ pgpjzt4Z5fPpm.pgp Description: PGP signature ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: I'd like to say thanks to the developers
Hi, Of course it's documented. :) I'd like to say that gnucash is one of the most well-documented pieces of open source software. This is more important than many people might think, because it helps new developers, speeding up the development process as well as leading to better quality software, and it helps the user understand. I, for one, would've had a very hard time with gnucash if the documentation (and translation) wasn't so good. Thanks alot. Simon Eilting. ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
M4 macros and newer automake
Greetings, automake 1.8.x is a bit more pedantic about m4 quoting, and issues an underquote warning when parsing the m4 macros installed by gnucash. The following patch fixes the problem. Regards, Luigi *** gnucash.m4 Fri May 14 15:03:25 2004 --- gnucash.m4.new Fri May 14 15:04:14 2004 *** *** 7,11 dnl gthread is specified in MODULES, pass to gnucash-config dnl ! AC_DEFUN(AM_PATH_GNUCASH, [dnl dnl Get the cflags and libraries from the gnucash-config script --- 7,11 dnl gthread is specified in MODULES, pass to gnucash-config dnl ! AC_DEFUN([AM_PATH_GNUCASH], [dnl dnl Get the cflags and libraries from the gnucash-config script ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: compile error on solaris x86
hi derek, thanks for the quick reply. LDFLAGS=-lnsl -lintl -L/usr/ucblib -lucb bash ./configure --disable-static --disable-error-on-warning where can i found the mentioned workarounds? benjamin Derek Atkins [EMAIL PROTECTED] schrieb am 07.05.04 15:21:13: This error tends to imply a libintl problem. What arguments did you provide to configure? FTR, I had to provide a number of workarounds to get it to compile on Solaris 9. -derek ___ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 ___ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Patch to support Indian Mutual Funds
Hi,
I hope this is the right mailing list for sending the patch. The supports
Indian Mutual Funds in GnuCash investment accounts. The latest version of
finance-quote (version 1.08) includes support for this. I've been happily
running gnucash with this patch since version 1.8.2. The patch is against
gnucash 1.8.2 but applies cleanly to 1.8.9. A makepatch version against
1.8.7 is available at http://people.debian.org/~rganesan/indiamutual.patch.
I am not attaching it with this mail because though the patch itself is
small the makepatch version nearly 70K and doesn't make it to the list.
I tried to send this mail to gnucash-patches twice but some how my mail
doesn't seem to make it to the list :-(. I am therefore sending this to
gnucash-devel as well.
Please CC me any responses since I am not subscribed to the
list. Thanks.
Ganesan
--- gnucash-1.8.2.orig/src/app-utils/gnc-ui-util.c
+++ gnucash-1.8.2/src/app-utils/gnc-ui-util.c
@@ -72,6 +72,7 @@
{ TRUE, TRUE, N_((none)), NULL, NULL },
{ FALSE, TRUE, N_(-- Single Sources --), NULL, NULL },
{ FALSE, FALSE, AEX, AEX, aex },
+ { FALSE, FALSE, AMFI India, AMFIINDIA, amfiindia },
{ FALSE, FALSE, ASX, ASX, asx },
{ FALSE, FALSE, DWS, DWS, dwsfunds },
{ FALSE, FALSE, Fidelity Direct, FIDELITY_DIRECT, fidelity_direct },
@@ -96,6 +97,7 @@
{ FALSE, FALSE, Canada Mutual (Fund Library, ...), CANADAMUTUAL, canadamutual
},
{ FALSE, FALSE, Dutch (AEX, ...), DUTCH, dutch },
{ FALSE, FALSE, Europe (Yahoo, ...), EUROPE, europe },
+ { FALSE, FALSE, India Mutual (AMFI, ...), INDIAMUTUAL, indiamutual },
{ FALSE, FALSE, Fidelity (Fidelity, ...), FIDELITY, fidelity },
{ FALSE, FALSE, T. Rowe Price, TRPRICE, troweprice },
{ FALSE, FALSE, U.K. Unit Trusts, UKUNITTRUSTS, uk_unit_trusts },
--- gnucash-1.8.2.orig/src/app-utils/gnc-ui-util.h
+++ gnucash-1.8.2/src/app-utils/gnc-ui-util.h
@@ -124,6 +124,7 @@
SOURCE_NONE = 0,
SPECIFIC_SOURCES,
SOURCE_AEX,
+ SOURCE_AMFIINDIA,
SOURCE_ASX,
SOURCE_DWS,
SOURCE_FIDELITY_DIRECT,
@@ -149,6 +150,7 @@
SOURCE_DUTCH,
SOURCE_EUROPE,
SOURCE_FIDELITY,
+ SOURCE_INDIAMUTUAL,
SOURCE_TROWEPRICE,
SOURCE_UKUNITTRUSTS,
SOURCE_USA,
___
gnucash-devel mailing list
[EMAIL PROTECTED]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: M4 macros and newer automake
Applied -derek Luigi Ballabio [EMAIL PROTECTED] writes: Greetings, automake 1.8.x is a bit more pedantic about m4 quoting, and issues an underquote warning when parsing the m4 macros installed by gnucash. The following patch fixes the problem. Regards, Luigi *** gnucash.m4 Fri May 14 15:03:25 2004 --- gnucash.m4.new Fri May 14 15:04:14 2004 *** *** 7,11 dnl gthread is specified in MODULES, pass to gnucash-config dnl ! AC_DEFUN(AM_PATH_GNUCASH, [dnl dnl Get the cflags and libraries from the gnucash-config script --- 7,11 dnl gthread is specified in MODULES, pass to gnucash-config dnl ! AC_DEFUN([AM_PATH_GNUCASH], [dnl dnl Get the cflags and libraries from the gnucash-config script ___ 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: ALMOST WORKING: quickbooks to iif to qif to gnucash
Hi, Keith Hellman [EMAIL PROTECTED] writes: Hello all: I feel I'm close to having a Quickbooks to GnuCash conversion process completed (I'll post the recipe if I can make it work all the way). Right now I have a python script that is reading IIF format and generating QIF (see attached files). When I import the QIF into GnuCash (1.8.8 debian sarge), in the next druid page after QIF file selection, it says: The QIF file you have loaded appears to have transactions for just one account, but the file does not specify a name for that account. This means that you didn't supply QIF Accounts in the QIF File, so the importer thinks you're importing a single QIF Account data. This is probably not what you want. The default choice for the attached files is 'input'. The rest of the import proceeds without incidence. When it is finished I have a file with an 'input' account, when I would have thought I would have a '1st Bank Checking' account. I bet that's because the file is named input.qif, right? ;) It defaults to filename - qif-account -- but later in the process you can map that qif-account to a gnucash account (assuming you're paying attention during the import process). If you wanted it to be 1st Bank Checking then you need to provide that account name. Do I need to separate my big QIF file into separate files for all accounts that occur in the 'L' field? Or do I specify an specific account with a '!Account' record entry in the QIF? Or (most likely) have I missed some important aspect of QIF generation or GNUcash importing? Either way will work. You could separate out each account into its own file, or you can combine them all into a single QIF file and provide !Account directives to specify the current qif-account. You probably want the latter. I don't think you missed anything about the import process. I suspect either of the first two answers are as much work to implement in my python script, I'm just looking for a little direction from the people in the know. I would suggest the one-file approach and just use the !Account directives. TIA PS: please cross-reply to me, as I have not subscribed to the lists (yet). You should subscribe, otherwise your posts will be held for moderation.. And that happens about once or twice a month, so you could be waiting up to 4 weeks for your post to get through if you are not subscribed. -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
