On Wednesday 26 January 2005 12:01 am, Josh Sled wrote:
> > Quite - QSF will never write an invalid XML file, nor accept one for
> > input. I was just waffling, as usual.
>
> Well -- and please correct me if I'm wrong on this -- it sounds like one
> can create a session which only contains only a s
On Wednesday 26 January 2005 1:58 am, Josh Sled wrote:
> I'd prefer to keep the discussion on -devel if you don't mind...?
Oops, it was getting late. It's when the list in CC: rather than To:, the
email ends up in the wrong folder, when I'm tired, I'd miss that.
> So, if I define an object which
On Wednesday 26 January 2005 4:42 am, Derek Atkins wrote:
> Neil Williams <[EMAIL PROTECTED]> writes:
> > If you want that to be:
> > /opt/garfield/gnucash/share/xml/qsf/
> > and
> > /usr/share/gnucash/share/xml/qsf/
> >
> > That's easy. I used qsf/ to distinguish from any other xml formats.
>
> Uh
On Tuesday 25 January 2005 10:45 pm, Neil Williams wrote:
> > > QSF source files are included in src/backend/file and create their own
> > > library, gnucash/libqsf-backend-file.so
> >
> > I think the code should probably go into src/backend/qsf instead of
> > backend/file. Also, the library shoul
Neil Williams <[EMAIL PROTECTED]> writes:
> /usr/share/qof/qsf ?
>
> (/usr/share/xml already exists on my system, something to do with docbook and
> scrollkeeper.)
No.. /usr/share/xml is the File System Standard location to store
DTDs and Schemas. It should be /usr/share/xml/qsf. Yes, you al
Neil Williams <[EMAIL PROTECTED]> writes:
> Which reminds me:
>
> Q. Where should I put user-edited files? In with the reports?
>
> These will be maps that the user edits - e.g. the example map has a default
> for the mileage rate to claim. That obviously needs to be user-editable. The
> modifie
Neil Williams <[EMAIL PROTECTED]> writes:
> Ignore the patch I sent in yesterday, I'll send in a complete replacement
> patch later today.
Done. :)
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
On Wednesday 26 January 2005 3:18 pm, Derek Atkins wrote:
> > Seeing as QOF will have to be installed either within GnuCash or as a
> > library for the others? I'll change QSF_SCHEMA_DIR to
> > ${share_dir}/qof/qsf
QSF_SCHEMA_DIR='${GNC_SHAREDIR}/xml/qsf'
in QOF
QSF_SCHEMA_DIR=`eval echo $datadir`
On Wed, 2005-01-26 at 03:58, Neil Williams wrote:
> All applications using QSF would have their own user editable maps to convert
> data to other applications. The maps are the real inter-operability stuff.
> Application maps come with the installation, user edited maps can go with the
> user e
On Wednesday 26 January 2005 4:52 pm, Josh Sled wrote:
> I don't quite understand the "user edited maps". I can see user-edited
> data values, but the applicationA<->applicationB maps don't seem like
> "user-edited" content per-se...?
>
> But, yeah, you're basically trying to do a [meta-]applicati
On Wed, 2005-01-26 at 13:22, Neil Williams wrote:
> I disagree, I prefer validation because there's no reason to implement a
> sub-set of validation (just checking Doc-Root) when code exists to check the
> whole. After all, you just said to use other existing methods rather than
> implementing
Neil Williams <[EMAIL PROTECTED]> writes:
>> >> Why? You know that a transaction note maps to
>> >>
>
> It'd be because each object uses "kvp" as the
> definition for each of their *_KVP macros - at least so far.
Then how do you differentiate the different kvp types?
> Those will be within t
On Wednesday 26 January 2005 8:02 pm, Derek Atkins wrote:
> Neil Williams <[EMAIL PROTECTED]> writes:
> >> >> Why? You know that a transaction note maps to
> >> >>
> >
> > It'd be because each object uses "kvp" as
> > the definition for each of their *_KVP macros - at least so far.
>
> Then how
Neil Williams <[EMAIL PROTECTED]> writes:
>> Then how do you differentiate the different kvp types?
>
> I'll get back to this next week - I'm planning on using a type="" attribute
> to
> indicate frame, key or value.
Uh, you don't need to indicate frames. Each entry needs a key, a
type, and a
On Wednesday 26 January 2005 9:11 pm, Derek Atkins wrote:
> Neil Williams <[EMAIL PROTECTED]> writes:
> > for QOF_TYPE_INT32, QOF_TYPE_DOUBLE, QOF_TYPE_CHAR and outline support
> > for QOF_TYPE_KVP which will be finalised next week. Every other type is
> > already supported - and tested what's more
On Tue, 2005-01-25 at 23:50, Derek Atkins wrote:
> 2) I'm not sure what mkdtemp is. I don't see that on Solaris,
>so that could be a real problem.
Well, it's not listed in the lib/goffice/*.c files, so it's probably
spurious.
> 3) Solaris also does not have ieee754.h
Hmm. IIRC, a lot of t
16 matches
Mail list logo
