Dave Peticolas <[EMAIL PROTECTED]> writes:
> How about we make the 'are there events pending' call a part of the
> backend api as well. So the engine/gui would just ask the backend if
> there are events and the backend would clear the flag when they are
> handled. That way, backends which need to
Derek Atkins writes:
> Dave Peticolas <[EMAIL PROTECTED]> writes:
>
> > > If so, then we just need something like:
> > > void gncSetEventFlag (void);
> > >
> > > and the Backend method can be something like:
> > > void (*process_event) (Backend *be);
> >
> > Ok, I will work on adding this t
Dave Peticolas <[EMAIL PROTECTED]> writes:
> > If so, then we just need something like:
> > void gncSetEventFlag (void);
> >
> > and the Backend method can be something like:
> > void (*process_event) (Backend *be);
>
> Ok, I will work on adding this today.
Ok. We should probably also
Derek Atkins writes:
> Dave Peticolas <[EMAIL PROTECTED]> writes:
>
> > Yes, that is the case. As long as the change happens in the normal
> > flow of control, the GUI should handle reparenting gracefully.
>
> Ok, then all we need it a flag that I can set (from another thread)
> that the engine/
Dave Peticolas <[EMAIL PROTECTED]> writes:
> Yes, that is the case. As long as the change happens in the normal
> flow of control, the GUI should handle reparenting gracefully.
Ok, then all we need it a flag that I can set (from another thread)
that the engine/gui loop checks and calls back into
Derek Atkins writes:
> Dave Peticolas <[EMAIL PROTECTED]> writes:
>
> > We must be careful here. Presumably the Backend is going to receive
> > information that the engine needs to be updated by some out-of-band
> > mechanism like a signal. Right now, the Backend must not mess with
> > the engine
Dave Peticolas <[EMAIL PROTECTED]> writes:
> We must be careful here. Presumably the Backend is going to receive
> information that the engine needs to be updated by some out-of-band
> mechanism like a signal. Right now, the Backend must not mess with
> the engine outside of the normal flow of co
<[EMAIL PROTECTED]> writes:
> You probably want to batch as much as possible, otherwise the gui will
> flash and blink every time it tries to refresh itself.
Well, I was only referring to when data changes in the data-store.
But I suppose that data there could be updated en-masse (ala sync())
writes:
> It's been rumoured that Derek Atkins said:
> > > > > 2) There appears to be no way for the backend to trigger an
> > > > >event to the engine/GUI if something happens. For example
> ,
> > > > >I'd like the backend (server) to signal to the engine
> > > > >
It's been rumoured that Derek Atkins said:
>
> <[EMAIL PROTECTED]> writes:
>
> > > Hrm. Then perhaps the best way to 'trigger' an event is to have the
> > > server push the new data to the backend, and the backend can then push
> > > it into the engine and notify the engine that the data has ch
<[EMAIL PROTECTED]> writes:
> > Hrm. Then perhaps the best way to 'trigger' an event is to have the
> > server push the new data to the backend, and the backend can then push
> > it into the engine and notify the engine that the data has changed?
>
> Yes. Although the last step can be skipped:
initial testing with 1.5.3 and it looks very sweet..just wanted to say that
and thanks for alot of hard work on this.:)
latre
lee
-===
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-de
writes:
> It's been rumoured that Derek Atkins said:
> > > > > 2) There appears to be no way for the backend to trigger an
> > > > >event to the engine/GUI if something happens. For example
> ,
> > > > >I'd like the backend (server) to signal to the engine
> > > > >
It's been rumoured that Derek Atkins said:
>
> <[EMAIL PROTECTED]> writes:
>
> > I think I want to retract some of my comments. By default, when the gui
> > calls xaccTransRollback(), it will merely restore the data that was
> > previously cached in the engine. And should mostly be enough: its
It's been rumoured that Derek Atkins said:
> > > > 2) There appears to be no way for the backend to trigger an
> > > >event to the engine/GUI if something happens. For example,
> > > >I'd like the backend (server) to signal to the engine
> > > >(client)
<[EMAIL PROTECTED]> writes:
> I think I want to retract some of my comments. By default, when the gui
> calls xaccTransRollback(), it will merely restore the data that was
> previously cached in the engine. And should mostly be enough: its highly
> unlikely that some other user changed the very
It's been rumoured that Derek Atkins said:
>
> Thanks for the reply. Comment inline...
>
> <[EMAIL PROTECTED]> writes:
>
> > Rollback for transactions in the multi-user case is sort of broken.
> > If the data in the database is newer than whats in the engine, then
> > any proposed updates from
[EMAIL PROTECTED] writes:
> Any prefered API?
> gnc_login(char * username, char * passwd) ?
> This isn't enough for e.g. kerberos authentication, but maybe enough
> for now?
Good question. I don't have a good answer. Assuming this is the
function that the backend calls to ask the user (would
Thanks for the reply. Comment inline...
<[EMAIL PROTECTED]> writes:
> Rollback for transactions in the multi-user case is sort of broken.
> If the data in the database is newer than whats in the engine, then
> any proposed updates from the user must not only be rejected, but the
> newer data fro
It's been rumoured that Dave Peticolas said:
>
>
> I'll answer as best I can. Linas is more familiar with the Backend
> code so he will be able to give more information.
>
>
> Derek Atkins writes:
> > So, I've been working on implementing an RPC backend, but I've
> > got a few questions:
> >
It's been rumoured that Derek Atkins said:
>
> Thanks.
>
> More responses inline...
>
> Dave Peticolas <[EMAIL PROTECTED]> writes:
>
> > The rollback is supposed to undo any changes which have been made
> > since TransBeginEdit and restore the transaction to its original
> > state. Restoring t
Thanks.
More responses inline...
Dave Peticolas <[EMAIL PROTECTED]> writes:
> The rollback is supposed to undo any changes which have been made
> since TransBeginEdit and restore the transaction to its original
> state. Restoring the data is actually done by the engine, so I'm
> presuming that
I'll answer as best I can. Linas is more familiar with the Backend
code so he will be able to give more information.
Derek Atkins writes:
> So, I've been working on implementing an RPC backend, but I've
> got a few questions:
>
> 0) There appears to be no way to allow the backend to call
So, I've been working on implementing an RPC backend, but I've
got a few questions:
0) There appears to be no way to allow the backend to callback
to the client to request a username/password or some other
authentication. I don't like the "hack" of putting the
24 matches
Mail list logo
