[Kde-bindings] Re: Documenting PyKDE4's bindings generation

[Luca Beltrame]

(please add me to the CC, as I'm not subscribed to kde-bindings -yet-)

> If this is happening then the design/implementation of pyuic4 needs to be
> changed. What does pykdeuic4 do that can't be done with pyuic4's existing
> plugin mechanism?

I'm not familiar on how pyuic4 works (is there some documentation, even 
docstrings?). I know that pykdeuic4, as shown here:

https://projects.kde.org/projects/kde/kdebindings/pykde4/repository/revisions/master/entry/tools/pykdeuic4/pykdeuic4.py

subclasses qtproxies.i18n_string to use KDE's own i18n rather than Qt's tr(). 

This is usually the part that breaks (I fixed it twice in the past months). Do 
you have any suggestions on how to implement this properly?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-bindings/attachments/20110427/9593dca2/attachment.sig>