Calc Macros - lagging behind?

[Michael Meeks]

Hi Christian,

On Sat, 2015-10-03 at 08:44 -0400, Christian Heller wrote:
> I'd love to use LibreOffice more, but I'm spoiled by Excel's VBA.

	=)

> Are there any improvements coming soon?

	The new python stuff may be helpful.

>         eg I love the strict types that get me all the member
>         functions and variables by just typing "." (auto-complete).

	This is a huge scriptability problem that we have. The Excel interfaces
have concrete typing - so you get an "Window" object and all the types
of the members are known, and there are helpful methods to get a
Worksheet property of type WorkSheet etc.

	I guess that the UNO interfaces are far less annotated, and many
properties are hidden by generics; though Stephan has done some nice
work in recent times to make it easier to pass type information through
tricky places, and its possible to type annotated properties ahead of
time. Do you have plans for the IDE in that regard Stephan ? (can we
pass type information about eg. collections through too ? )

>         dim args1(0) as new com.sun.star.beans.PropertyValue
>         args1(0).Name = "Text"
>         args1(0).Value = "Your name"
>         dispatcher.executeDispatch(document, ".uno:InsertText", "", 0,
>         args1())

	This of course is not a great way to insert text either ;-) my hope
would be that we could encourage people to use the UNO APIs through
making them easier to understand and use - perhaps with some less
cumbersome top-level, strongly typed methods to get useful interfaces.

	Either way - I agree its a huge hole, and it'd be lovely to have
someone to care about not only our API - but how we can use stronger
type information to get the IDE into some more usable shape.

	ATB,

		Michael.

-- 
 michael.meeks at collabora.com  <><, Pseudo Engineer, itinerant idiot