install.exe Under Windows Vista
Hi All, I am attempting to run gnucash under Microsoft Vista. The binary install installs OK but does not run. I am now attempting to download the gnucash build enviroment. Each time c:/soft/msys/bin/install.exe run from install.shell Vista ask if I will allow this program to run. How can I configure install.exe to run without user intervention? Or maybe I should go back a step. What should I be doing to get gnucash to run under Microsoft Vista? Yours Sincerely stephen Grant Brown _ Roast a Rock Star: watch video interviews with hot music acts http://ninemsn.com.au/share/redir/adTrack.asp?mode=clickclientID=809referral=hotmailtaglineURL=http://music.ninemsn.com.au/roastarockstar ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: RW access for german account charts
Christian Stimming wrote: It would be fine to have more people with write access to gnucash/trunk/accounts/de_DE/ . OK, so what is the next step? In case you guys go with Chris' suggestion of a separate branch, I'd only ask you not to name it mob. As a contributor, I think I and anyone else deserves to be treated with respect and mob does not quite express that to me. I am sure it was not meant offensively, but the wording is not so super, I'd say. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: RW access for german account charts
On Mon, Sep 03, 2007 at 04:03:13PM +0200, Rolf Leggewie wrote: Christian Stimming wrote: It would be fine to have more people with write access to gnucash/trunk/accounts/de_DE/ . OK, so what is the next step? In case you guys go with Chris' suggestion of a separate branch, I'd only ask you not to name it mob. As a contributor, I think I and anyone else deserves to be treated with respect and mob does not quite express that to me. I am sure it was not meant offensively, but the wording is not so super, I'd say. hehe. I can see your point. While the actual branch name is not important, the designation as a mob branch is actually a term of art. The term is a reference to an essay [1], and it's a term I've seen used by several different projects. Admittedly, it's probably not widely used outside of communities that use a distributed SCM, so I should have explained the term. Nevertheless, I don't think we have any say over the definition of that term. It's certainly not a derogatory term, so I expect it will eventually lose any intial negative connotations people have with it. As to the point at hand, it doesn't seem like anyone is too interested in figuring out how to implement this with svn, so it's probably easiest just to give you access to the directory. So, send Derek or Josh your public key, and see what happens. :) -chris [1] http://www.dreamsongs.com/MobSoftware.html ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Fwd: [gnome-db] Libgda/Libgnomedb version 3.1.1 available
I hope this is interesting, if not, please tell me to avoid forwarding. -- Forwarded message -- From: Vivien Malerba [EMAIL PROTECTED] Date: 02-sep-2007 2:58 Subject: [gnome-db] Libgda/Libgnomedb version 3.1.1 available To: gnome-db list [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] I'm pleased to annouce that the first beta version of libgda/libgnomedb (version 3.1.1) have been released, which is the first version of the unstable 3.1.x series. libgda/libgnomedb are a complete framewok for developing database-oriented applications, and actually allow access to PostgreSQL, MySQL, Oracle, Sybase, SQLite, FireBird/Interbase, IBM DB2, mSQL and MS SQL server, as well as MS Access and xBase files and ODBC data sources. libgda/libgnomedb are part of the GNOME Office application suite, providing database access for many features in both Gnumeric and Abiword. Changes from version 3.0.x include: For Libgda: - Require inltool 0.35.5 when building from svn (Murray Cumming) - SQLite now version 3.4.2 (Vivien Malerba) - Added support for cursor-only access for data models returned by the PostgreSQL provider (Vivien Malerba) - WIN32 port functionnal (needs testing, Vivien Malerba) - Installation is relocatable (Vivien Malerba) - New virtual connection feature, which allows to run SQL commands on data models (Vivien Malerba) - Reworked the BDB provider to use virtual connections (Vivien Malerba) - Embedd the libcsv library (http://sourceforge.net/projects/libcsv/) for CSV parsing - Reworked the documentation - Many small corrections and improvements - New code examples (BDB usage, virtual connections) - New command line tool (similar to psql) - Reworked reports engine (breaks API -- the previous implemention did not work) - Bug fixes: #432798, #432798, #433687, #316698, #449725, #450043, #454896, #467273 (Armin Burgmeier, Marc-Andre Lureau, Piotr Pokora, Vivien Malerba) - Translations: - ar (Djihed Afifi) - zh_HK (Chao-Hsiung Liao) - zh_TW (Chao-Hsiung Liao) - es (Jorge Gonzalez) - vi (Clytie Siddall) - fi (Ilkka Tuohela) - eu (Inaki Larranaga Murgoitio) For Libgnomedb: - Use libgcrypt instead of openssl (Gustavo R. Montesino) - New (experimental) graph widget based on the GooCanvas library (Vivien Malerba) - Support automatic graph layout if the GraphViz library is present (Vivien Malerba) - WIN32 port functionnal (needs testing, Vivien Malerba) - Installation is relocatable (Vivien Malerba) - Glade 3.3.x support (Vivien Malerba) - New grid-based plugin (Carlos Savoretti) - New demos in gnome-db-demo (Vivien Malerba) - Many small corrections and improvements - Bug fixes: #437212, #426007, #448359 (Claude Paroz, Gustavo R. Montesino, Vivien Malerba) - Translations: - ar (Djihed Afifi) - zh_HK (Chao-Hsiung Liao) - zh_TW (Chao-Hsiung Liao) - es (Jorge Gonzalez) - vi (Clytie Siddall) - eu (Inaki Larranaga Murgoitio) Tarballs are available (or should soon be) at ftp://ftp.gnome.org/pub/GNOME/sources/libgda/3.1/ and ftp://ftp.gnome.org/pub/GNOME/sources/libgnomedb/3.1/ To install this new version, you'll need: * libgda: glib, libxml2, libxslt * libgnomedb: libgda and dependencies, Gtk+ = 2.6.0, libgnomeui, libglade, gtksourceview You can find more information at the projects' homepage (http://www.gnome-db.org), or you can ask any question/propose anything you want in the GNOME-DB mailing list, which is available at http://mail.gnome.org/mailman/listinfo/gnome-db-list. ___ gnome-db-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/gnome-db-list -- Trabajar, la mejor arma para tu superación de grano en grano, se hace la arena (R) (entrámite, pero para los cuates: LIBRE) ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: RW access for german account charts
Chris Shoemaker wrote: So, send Derek or Josh your public key, and see what happens. :) Done. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: External App connection to a GnuCash file
2007/9/2, Christian Stimming [EMAIL PROTECTED]: Am Mittwoch, 29. August 2007 21:52 schrieb Josh Sled: Daniel Espinosa [EMAIL PROTECTED] writes: I found a macro in /macros/legacy_macros.m4 witch test for sscanf to support %lld (long long decimal integer) if so defines HAVE_SCANF_LLD. I think this is supported in recent gcc versions, then I can safetly define it in configure.in or remove this test in /lib/libqof/qof/qofutil.h. I'm not 100% sure about the provenance of that code, but I'm pretty sure it should not be removed. Josh is correct. The macro from legacy_macros.m4 turned out to be not legacy at all, but it is in fact needed a lot. To be more precise, the gcc/libc environment on Windows/mingw needs a different scanf() format character for LLD than what gcc needs on Linux. The test in legacy_macros.m4 checks exactly that. Hence, you need to copy the respective macro into your own application as well. Thanks I've copied this macros in my project and it now compiles. On the other hand, the resulting format character itself is probably only needed inside the gnucash/gncqof implementation and doesn't have to be exposed to outside applications. Hence, in the long term this test probably should have to be done by your external application, and in gnucash this #ifdef check should be moved to an internal header file. Well, that's a long-term goal. Scanf is used in file backend and other places inside GnuCash, then this tests, I think, could be hide at the eyes of other applications and just expose the usefull API for other applications. Why is a long-term goal? Is it represent too much work? When will GC clean up this issues to make easy other applications to use its data, may be to 2.4 or 3.0? -- Trabajar, la mejor arma para tu superación de grano en grano, se hace la arena (R) (entrámite, pero para los cuates: LIBRE) ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Welcome to the GnuCash Developer gene pool
Welcome to svn.gnucash.org. You now have an account, rolf, which you can use to access the SVN sources. You can now access the sources by: $ svn checkout svn+ssh://svn.gnucash.org/repo/gnucash/trunk src-trunk [or maybe: $ svn checkout svn+ssh://[EMAIL PROTECTED]/repo/gnucash/trunk src-trunk if your username is different.] You will also have mail forward automatically. Good Luck, The GnuCash Server Maintainers ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
developer account created rolf
This is an automated e-mail via the add-new-developer script ($Revision: 1.7 $). Developer account Rolf Leggewie has been created: [EMAIL PROTECTED]. Admins (root) should update CVS access for this user. Welcome to the team. -- (script run by root). ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: External App connection to a GnuCash file
Am Montag, 3. September 2007 20:16 schrieb Daniel Espinosa: On the other hand, the resulting format character itself is probably only needed inside the gnucash/gncqof implementation and doesn't have to be exposed to outside applications. Hence, in the long term this test probably should have to be done by your external application, and in gnucash this #ifdef check should be moved to an internal header file. Well, that's a long-term goal. Scanf is used in file backend and other places inside GnuCash, then this tests, I think, could be hide at the eyes of other applications and just expose the usefull API for other applications. Yes. Derek and I already agreed on this. Why is a long-term goal? Because it's not important for *gnucash*, hence it isn't a short-term goal *for gnucash*. Is it represent too much work? Yes. Unless you send in a patch - feel free to do so. When will GC clean up this issues to make easy other applications to use its data, may be to 2.4 or 3.0? No idea. Christian ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Questions about gnuCash backend access
Daniel Espinosa [EMAIL PROTECTED] writes: QOF headers has a lot of coments pointing potencial bugs or even actual bugs Can I add this as bugs in bugzilla? I'm not sure what the advantage would be to having them either in two places (the comment and bugzilla) or one place (bugzilla) which is separate from the code. If you want to submit a patch that addresses a bug, it might be good to create a bugzilla entry as a place to attach the patch ... but mailing it to gnucash-devel is probably just as good. -- ...jsled http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED] pgpRg6fI0oKZZ.pgp Description: PGP signature ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Dogtail UI Harness Status
ahmad sayed [EMAIL PROTECTED] writes: In this phase of SOC the following updates done to the Dogtail UI Harness project, the status as usual is mix of bad and good news. Ahmad... Congrats on a modestly successful Summer of Code project. I'm sure that there's good and bad parts, but that's always the case. :) However, it looks like we have both a framework for running dogtail-based tests, and a whole suite of code for interacting with GnuCash and exercising parts of the user interface. :) If I wanted to add a test for the Scheduled Transaction subsystem ... let's say consisting of: 1/ creating a new Scheduled Transaction with given parameters. 2/ running the Since Last Run dialog. 3/ inspecting a value in the tree view/model. 4/ manipulating the tree view; closing the dialog. 5/ re-opening the Since Last Run dialog. 6/ inspecting a value in the tree view/model. ... how would I go about it? What would I want to add or extend, and in what files. How to invoke just that test to try it out? I guess I'm looking for a bit of high-level documentation. I'm sure I can figure it out if I spend enough time with the code, but something short that points me in the right direction would be great. -- ...jsled http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED] pgpGAvmQYJPzH.pgp Description: PGP signature ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: CSV Importer
Benjamin Sperisen [EMAIL PROTECTED] writes: Anyway, most of what I've done has been to address the shortcomings discussed earlier. Benjamin, congrats on a pretty successful Summer of Code project. The importer is looking (and working) pretty well. First, I've reworked the internal error handling code so that, if there are errors, a new column to the right is created listing the errors on each particular row. For example, if a row has abc in its Deposit column, it will put Deposit column could not be understood in the Errors column for that row. I noticed that in my test file, the only regular line in error was a heading line. It'd be nice to have an option of the form ignore file's header line. (Even better, it'd be good to do default column-type assignments based on the contents of that header line. ;) Secondarily, it'd be nice – in the error handling page – to be able to ignore a line in error, easily. It'd be nice to support both the transaction and post date in the importer, since the engine/model does support both, even if the register UI doesn't, right now. Also, I notice the first stage after the file parsing – perhaps part of the Generic Importer, though – is an account tree/selection dialog labeled: Please select or create an apropriate GnuCash account for: ... obviously, it'd be nice if the thought was finished about what account I'm supposed to be selecting for. Second, fixed-width files are now supported. The interface is actually virtually identical to Gnumeric's, as I merged their code into mine, particularly for the context menu for column merging. I couldn't figure this out at all... I couldn't see how to mark the boundaries of columns for a fixed-width file. As well, the lines in my fixed-width file were pretty long, which made the dialog open way too wide... 1.5 screens wide, in fact. :( Were there some test data files that you were using? Are those checked in anywhere? I'll see if I can add mine, after I clean them up, as well. During the fall, I would like to keep working on the importer, even though I won't be able to work quite as much because of school. The next feature I'd like to implement is actual editing within the dialog of data (so that users don't have to go back and manually edit it in a spreadsheet, save and reimport). Nifty. I hope you're able to find the time to continue to work on this... I would also like to thank you, Josh and Christian, as well as the rest of the GnuCash community, for all of your help and guidance over the summer! This was definitely a great learning experience in many practical aspects of open source and software development in general. I have really enjoyed working with all of you and hope to continue in the future. I'm glad you found it worthwhile. Thank you for sticking with it, and getting a nice new feature added to GnuCash! :) -- ...jsled http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED] pgpzwZFwyv0Od.pgp Description: PGP signature ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Dogtail UI Harness Status
Hi Josh, Thank you very much for your positive feedback,honestly I have a stomach lately like the one I used to have before receiving my exams results:), that what keep me silent. Josh Said: If I wanted to add a test for the Scheduled Transaction subsystem ... let's say consisting of: 1/ creating a new Scheduled Transaction with given parameters. 2/ running the Since Last Run dialog. 3/ inspecting a value in the tree view/model. 4/ manipulating the tree view; closing the dialog. 5/ re-opening the Since Last Run dialog. 6/ inspecting a value in the tree view/model. I guess I'm looking for a bit of high-level documentation. I'm sure I can figure it out if I spend enough time with the code, but something short that points me in the right direction would be great. I'm going to write a tutorial to be uploaded to common place (e.g. to gnucash wiki), your suggested testcase will be my start point, i'll start it tomorrow as it is now 2 AM in my country :). I plan to finish documenting all the testsuite related technical details before the school start, also i would like to keep working on the testsuite there is still a lot of work todo, 1 - adding more testcases, 2 - figure out how to speed it up 3 - link the testsuite to the makefile. 4 - add more dialogs and custom widget wrappers. 5 - Solving issues with with the register, and account Trees. 6 - more Testing to the testsuite ፡). Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. http://sims.yahoo.com/ ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
