> On May 3, 2016, at 9:16 PM, Don Ireland wrote:
>
> John,
>
> Thanks for the follow up.
>
> "You seem to be a bit confused about task separations, though."
>
> What I was suggesting is that the GUI would display the existing records and
> provide a way for the user to tell the server to
John,
Thanks for the follow up.
"You seem to be a bit confused about task separations, though."
What I was suggesting is that the GUI would display the existing records and
provide a way for the user to tell the server to create new records via API
calls. Other than that, all processing wo
> On May 3, 2016, at 10:16 AM, Don Ireland wrote:
>
> I’ve been using gnuCash for the past 3-4 days and really like what I’ve seen
> so far. I’ve read that the dev team is planning to rewrite the code.
>
> Might I suggest breaking it into a server (with an API) and a client
> (providing the
I am not a developer but I recall seeing on one of the maillists very
recently that the infrastructure changes required to get to a true database
file structure should be completed sometime in 2018 (unless more volunteers
step up to help). Then ideas like yours might be possible.
Davi
Sounds like a progressive idea.
A very similar approach which would be easier and more ‘main stream’ is to use
a browser as the GUI. There are a number of frameworks which can be used to
write the server such as RubyOnRails, Django, etc. These frameworks use MySql,
Postgresql, SQLite in a datab
I’ve been using gnuCash for the past 3-4 days and really like what I’ve seen so
far. I’ve read that the dev team is planning to rewrite the code.
Might I suggest breaking it into a server (with an API) and a client (providing
the GUI)? This would allow for the GUI to be used on any multitude
