Geert Janssens <janssens-ge...@telenet.be> writes:
> Indeed. I mostly meant to suggest our *engine* should be totally
> multi-platform. The gui should be adapted to the target OS and
> form-factor anyway. I wouldn't want to use a gui similar to current
> GnuCash's one on an Android tablet for example. Having the engine
> available on say Android, that could make Ngewi's work a lot easier:
> instead of importing/exporting, he could plainly open a real gnucash
> datafile and work directly on it. That doesn't mean the GnuCash on
> Android tool should support all the features GnuCash on
> Linux/OSX/Windows does, but it would be able to properly load and save
> the file without any data loss.
I think in the long run it would behoove us to try to migrate more of
the "business logic" into a core platform, too. But I'm not sure
exactly how to do that in a clean way that provides "real-time"
validation of inputs, without it being tied into the GUI.
>> There is one cross-platform UI engine which is well-supported on all
>> platforms (Windows, Linux, Mac, Android, iOS) that I can think of, but
>> utilizing it would require a more major change in the structure of the
>> code: HTML5.
>
> True. And I sometimes get the feeling all GUI work is slowly
> converging on this standard. Gtk has an experimental HTML backend,
> we're seeing ChromeOS, FirefoxOX, even QML is inspired on the same
> declarative concept if I remember well (though it is not HTML in
> itself).
Interesting concept..
-derek
--
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
warl...@mit.edu PGP key available
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
