Yah, but you might want to test #6 anyway since you are technically never guaranteed to be able to read from the gconf database. Techically programs should work with their default values even if gconf decides to fail on every lookup.
2008/2/26, Charles Day <[EMAIL PROTECTED]>: > > On Sun, Feb 24, 2008 at 9:10 AM, Derek Atkins <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > Quoting Charles Day <[EMAIL PROTECTED]>: > > > > > On Sat, Feb 23, 2008 at 9:32 AM, Derek Atkins <[EMAIL PROTECTED]> wrote: > > > > > >> Yeah, I thought they should be shown by default.. Are you sure > > >> that you're picking up the default schema settings? > > >> > > > > > > > > The option to turn on/off QIF doc pages doesn't seem to be part of the > > > default schema settings. I guess I should put together one of those > > > "schemas" directories for the QIF importer, right? Alternatively, we > > could > > > just change the sense of the setting to "Hide documentation" rather > > than > > > "Show documentation" so that doc pages are on by default, even if you > > blow > > > away your .gconf settings. > > > > I've gone the schema route, and although I know nothing about gconf or > automake except what I skimmed today, by some miracle it seems to have > worked. Here's what I did, so tell me if this sounds right: > 1. Created a new "schemas" directory under qif-import (I copied the one in > import-generic) > 2. Rename "apps_gnucash_import_generic_matcher.schemas.in" to > "apps_gnucash_import_qif.schemas.in" and adjust its content. > 3. Edit Makefile.am in the new schemas directory and replace > "apps_gnucash_import_generic_matcher.schemas.in" with > "apps_gnucash_import_qif.schemas.in" > 4. Edit Makefile.am in the qif-import directory and add "schemas" as a > subdirectory (SUBDIRS). > 5. Edit configure.in and add a line for > "src/import-export/qif-import/schemas/Makefile" > 6. Add error checking to druid-qif-import.c so that doc pages are turned > on by default if the gconf lookup fails. > 7. Build and test gnucash from scratch. > > Does the above sound like everything I need to do? It seems to work - and > not by getting defaulted from #6. > > I notice that the Makefile.in files got rebuilt at some point... but "svn > status" doesn't reflect that. Is SVN ignoring Makefile.in differences on > purpose? Would I need to include the new Makefile.in in the new schemas > directory as part of my "svn commit"? > > Cheers, > Charles > > > > > > > > Any opinion? > > > > That would work... > > > > > -Charles > > > > -derek > > > > > > > >> -derek > > >> > > >> "Ian Lewis" <[EMAIL PROTECTED]> writes: > > >> > > >> > Charles, > > >> > > > >> > Oh shoot. I was under the impression that they were shown by > > default. I > > >> > definitely agree with this. There is no point if they are not shown > > by > > >> > default. On a side note, perhaps we should have a check box in the > > druid > > >> > that allows users to turn them off from the druid itself (like on > > the > > >> apply > > >> > page)? The check box is in the preferences and I might not have > > known > > >> about > > >> > it if I hadn't done development on the QIF druid. > > >> > > > >> > As far as how to do it, I would imagine you would have to do > > something > > >> along > > >> > the lines of editing a default schema somewhere in the source tree > > but I > > >> > couldn't tell you for sure as the code isn't in front of me atm. > > >> > > > >> > Ian > > >> > > > >> > 2008/2/23, Charles Day <[EMAIL PROTECTED]>: > > >> >> > > >> >> The QIF importer druid has "doc pages" that benefit new users by > > >> >> explaining > > >> >> the import process a step at a time, as the user makes his way > > through > > >> the > > >> >> druid. I think that new users would really benefit if these pages > > were > > >> >> shown > > >> >> by default (I certainly would have). However, GnuCash currently > > hides > > >> >> these > > >> >> pages by default. > > >> >> > > >> >> Do you agree that these pages should be shown by default, and if > > so, > > >> how > > >> >> do > > >> >> I make this happen? The setting is controlled via gconf, so would > > I > > >> have > > >> >> to > > >> >> add one of those gconf schemas perhaps? > > >> >> > > >> >> Cheers, > > >> >> Charles > > >> >> _______________________________________________ > > >> >> gnucash-devel mailing list > > >> >> [email protected] > > >> >> https://lists.gnucash.org/mailman/listinfo/gnucash-devel > > >> >> > > >> > _______________________________________________ > > >> > 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 > > >> > > > > > > > > > > > -- > > 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
