2005/11/23, Joerg Budischewski <[EMAIL PROTECTED]>:
Hi,

>     Main reason for  not supporting this attributes is actually my lack of
>     knowledge of these python internas. Which attributes should be supported
>     from your point of view ?
>
>
> IMO, every UNO object exported in Python should have every method and
> property explicitely exported and visible as attributes. That's what my
> current hack is doing in Python.
> Not sure if it worth doing this at C level. Maybe a solution like the
> one I have done would be sufficient (but need to be done cleanly. I am
> thinking to a quite elegant solution using metaclasses).
it should be done at the C level, and I think, it shouldn't be too
difficult once one knows, which properties to support to achieve this.

OK, I'll have a look at this ASAP, if you wis ;-)

>
> I'll think a little depper about this.
> For now, what I have done is to declare every method (through the
> interface's definition decalred by the objet) and properties (idem) in a
> fake wrapper class.
>
>
>     Similar things hold for structs and exception (see
>     pyuno/source/module/pyuno_except.cxx).
>
>
> I have already run my eyes over the C++ code, but not very deeply.
> I'll try to investigate the issue you mention (47270) as soon as I have
> solved my issues with pythonscript.py .
I already have a fix for this issue, just wanted to let you know ...

Is it available on the CVS repository or somewhere else (I have not checked yet) ?

One remark. I am not sure the use of "smart-pyref" is really a helpful tool. I think this brings more confusion than help in the code. I have no time to develop this now, but I can do it later if you think I am wrong.


Bye,

Joerg

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Bye,  David

Reply via email to