On 3 July 2012 18:06, Daniel Espinosa <[email protected]> wrote: > Some weeks away I've freeze Vala Extensions for new features. I've tried > to get Unit Tests working and with a few time left, I've tried to use them > in Python, but found a serious problems with Vala's Gee: it can't be used > as public API in non Vala applications like on GObject Introspection. > > After considering that I'm planning to do the following: > > a) Move away from Gee for some properties in Vala Extensions API > b) Re-implement the code to use GLib structures > c) Rename name space from GdaData (gda_data in C) to some thing else like > GdaDbo, Gdao, (suggestions?) >
I understand a) and b), but I don't see why you need to change the namespace as I assume this means people using the extension would then need to heavily modify their code. > But I need to know your comments in order to proceed and don't stop any > 5.2 release. > I believe this is for version 5.4, you can create a branch for that topic and we'll merge it after 5.2 is out. As for the 5.2 version, I still need to correct a problem I found in the GdaMetaStore update mechanism (I hope to correct the bug and make it faster at the same time). As I'm on holidays soon, I hope I get some more time to work on this. > Exists a bug report to port GDA to Vala's m4 macros, now that they > deprecate its bindings and prioritize GDA's autogenerated ones. May I can > try to fix that, but requires some time, is this possible before 5.2 > release? > I believe 5.2 won't be out for at least another month now, so I'd say you have some time to correct this bug. Thanks, Vivien
_______________________________________________ gnome-db-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/gnome-db-list
