J. Alex Aycinena schrieb:
I get the following error when compiling r18419:
...
cc1: warnings being treated as errors
dialog-tax-info.c: In function ‘identity_edit_clicked_cb’:
dialog-tax-info.c:1083: error: implicit declaration of function
‘gtk_dialog_get_content_area’
John Ralls jra...@ceridwen.us writes:
On Nov 18, 2009, at 9:32 AM, Derek Atkins wrote:
John,
How about if you put it into the installer itself so that it pops up
when they attempt to install it?
There is no installer. You download the dmg (which is a disk image, like an
iso), mount
On Nov 19, 2009, at 5:31 AM, Derek Atkins wrote:
Fair enough. I'm just trying to think of how to make it available in a
way that's NOT a link off to a SF page. Maybe a link to the wiki?
I thought that Geert had set it up to be a hosted file (he mentioned
osx_readme.phtml being missing
On Thursday 19 November 2009, John Ralls wrote:
On Nov 19, 2009, at 5:31 AM, Derek Atkins wrote:
Fair enough. I'm just trying to think of how to make it available in a
way that's NOT a link off to a SF page. Maybe a link to the wiki?
I thought that Geert had set it up to be a hosted file
On Nov 19, 2009, at 8:04 AM, Geert Janssens wrote:
On Thursday 19 November 2009, John Ralls wrote:
On Nov 19, 2009, at 5:31 AM, Derek Atkins wrote:
Fair enough. I'm just trying to think of how to make it available in a
way that's NOT a link off to a SF page. Maybe a link to the wiki?
I
On Thursday 19 November 2009, John Ralls wrote:
The wiki page would become the primary; converting it to html is easily
done by opening it in the browser and saving it (or downloading it via
curl). Not a significant change in effort, really. It has the advantage
that it could be easily
Currently, transactions/splits are not loaded from an sqlite3/mysql/postgres
db at startup in the 2.3.X series. I think I need to change this so that it
does load all transactions/splits. As has been pointed out many times,
gnucash is *not* a database app. When it acts more like a database
On Nov 19, 2009, at 1:53 PM, Geert Janssens wrote:
Personally I think it would be better in the long run if the files were
referring to the release they are written for, so for example:
MacOSX/Readme/2.2.9
and
MacOSX/Readme/2.3.7
I don't have experience with the SF file manager (I setup
