For me, at least, not having eguile reports and a CSS-compatible
renderer are show-stoppers. I've seen that the vast majority of time in
reporting is due to the current HTML-render. 20-30 seconds to render a
budget report just isn't acceptable for us. Between that and that it
strips out CSS so you can't even create a decent report to render
externally, these, for me are beyond critical.
I'm working on patching up the budget code (which is presently blind to
the UI sign-reversal selections) and would like to try to get them in,
but I don't know how long it will take to resolve the Scheme/C issues
related to variables and initialization (for example, the patch in
<http://svn.gnucash.org/trac/browser/gnucash/trunk/src/libqof/qof/qofbookslots.h?rev=18464>
doesn't look to be localizable), even if the problem with kvp not being
compatible across different locales (the key generally changes when your
locale does). While I would like to get this in so that the change in
budgets is at a major release, I don't want to hold things up.
Jeff
Christian Stimming wrote:
Am Samstag, 6. März 2010 schrieb John Ralls:
On Mar 5, 2010, at 2:59 PM, Phil Longstaff wrote:
Do we want to release a stable 2.4.0? What do we need to finish to do
that. There are lots of things happening in trunk, all of which will be
useful at some point, but many of which are destabilizing things.
My feeling from the users list says they want the dbi backend and the new
reporting made possible by WebKit, and that they'd like it soon. Maybe we
should ask them what they want.
That's my understanding as well.
However, dbi already comes with several variants: sqlite3 file, mysql
bindings, postgresql bindings. Which one of those should work? All three?
So we need to make up lists of features new in 2.4 which need to be verified
to work correctly:
- webkit reporting
- dbi backend with sqlite3 file
- dbi backend with mysql bindings
- dbi backend with postgresql bindings
There are additional new features, which might still have problems, so we can
decide whether to disable them for 2.4 or test and fix them:
- eguile reports
- CSV importer (or was this active in 2.2.9 already?)
- QSF export (or was this active in 2.2.9 already?)
- Check printing features (but I think those work without problems)
(As you might have guessed, I need none of those features mentioned above. So
I neither test them nor care about whether they are included in 2.4.0. But
that's just my personal motivation here.)
Regards,
Christian
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
