Alexandro Colorado wrote:
> Quoting Mathias Bauer <[EMAIL PROTECTED]>:
>
>> Alexandro Colorado wrote:
>>
>>> Also is not the language syntaxis is more about the framework of UNO
>>> which add
>>> some complexity. However another place to look is
>>> http://ext.openoffice.org.nz
>>> which is a wiki to PUSH the development of macros and add-ons.
>>
>> To avoid rumours ;-): it's not UNO that adds the complexity, UNO itself
>> is not more complex than COM (the comparable technology that is used in
>> VBA). Please find more about this in my reply to Ians mail.
>
> True I guess I should have specify syntax complexity since it uses long
> 'namespaces?!?' to invoque components.
The namespaces make the code look unusual for the average macro
developer, but this is a disadvantage of the OOoBasic only at a first
glance: VBA uses ClassIDs to instantiate objects instead - IMHO this is
even worse than our namespaces. Code using ClassIDs will always lool
horroble, but you can get used to our namespaces!
You don't see this weakness of VBA so often because VBA makes many
objects accessible through explicit methods, not through an object
construction where you need a ClassID ("Application.Something"). But
going this way would force the developers to provide new API methods
(and thus new interfaces) for every new object they want to provide.
You should also see that a lot of things where you need "long namespace"
names in OOo aren't available at all in VBA, so you can't really compare
this.
Nevertheless I'm thinking about using the namespace "com.sun.star" as an
implicit one so that the interpreter automatically finds it if necessary
(the compiled byte code would be the same then if you write the name
with or without namespace).
But wether that creates too much potential problems must be considered
carefully. We could also use the same "trick" as C++ developers use by
declaring "using namespace com.sun.star" so that the macro developer can
make his work easier at the cost of a higher risk of getting ambiguities
in his code that force the interpreter to complain about a syntax error.
Besides that we know some more things we could improve in OOo Basic to
make writing macros easier and we are working on this. Maybe we can
present some possible improvements in the near future (not in 2.0,
that's too late). But I disagree that we have a fundamental problem here.
Best regards,
Mathias
--
Mathias Bauer - OpenOffice.org Application Framework Project Lead
Please reply to the list only, [EMAIL PROTECTED] is a spam sink.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
