Hmm, would it make sense to try my generic druid builder? The idea
was to abstract out the GUI from the processing.. That way you could
implement the backend processing once and just put the appropriate
frontend glue to display the druid pages? This should reduce the
work from "double" to something that's less work to maintain.
But I understand that there's nobody around who wants to implement
that.
-derek
Quoting Christian Stimming <[EMAIL PROTECTED]>:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martin Preuss schrieb:
On Thursday 18 May 2006 16:18, Derek Atkins wrote:
Martin Preuss <[EMAIL PROTECTED]> writes:
As for frontends: You don't need additional frontends to run Gnucash. As
a matter of fact Gnucash does not even use my GTK2 frontend, so you don't
need that, either.
The only frontend Gnucash relies on is qbanking, because the QT frontend
provides the setup wizard which is called by Gnucash.
Do you have a Gtk2 equivalent of qbanking for setup?
It seems rather "silly" for gnucash to require kde/qt in order to
configure HBCI. ;)
[...]
No, we don't, and yes, it does :-)
I was about to write exactly the same reply as Martin.
Again, the HBCI setup is an extremely complex process. HBCI comes with
three completely different security modes (Chipcard, RSA-Keyfile, or
PIN/TAN), and each one (!) requires about 5-15 wizard pages for setup.
Plus testing each single one of the setup modes. And by definition
during day-to-day work we don't use the setup wizards at all.
- From the past experience we've seen how easily we miss a special case or
the other during testing, and the users will of course complain about
that. If we were maintaining not one setup wizard (the qt3 one) but two
of them (qt3 and gtk2), then we would have double the cases to test.
Given that nobody else except Martin and (a little bit) myself are
actively working on development, testing and bugfixing here, it would be
insane to increase the probability of programming error only because "it
seems silly to require qt". That's why we stick to this, and we will do
this until some active gtk2 developer will show up in aqbanking and
develop and maintain a gtk2-based setup wizard. That's how it is, currently.
Christian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQCVAwUBRGySFWXAi+BfhivFAQL7TQP+L60y48aWb2kzpN0e8yVWAZZUGEg3H0bW
5nEtvq5gTu4iLO6pl0MDa40imXj/eBkcDPi8G+8zcx8CtD8NuhqkIqB+auvKJdJO
jeyFw2a+LUA3k+3iHEqW50IhUUKeb9GAMqaSoTkb5jDHjQv8Xyaqof7aReCcrKZN
IRASVGbXj0E=
=tD2v
-----END PGP SIGNATURE-----
_______________________________________________
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
_______________________________________________
gnucash-devel mailing list
[email protected]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
