Macro language development

[Robynsveil]

In the recent past, I asked this question:

Converting vba to python

I have a number of Excel 2003 (and earlier) VBA utilities I would love to move to LibreOffice, since I’m spending more and more time in Mint and Calc, and less and less in Windows and Excel. It seems macro development in LO is largely dependent on OO’s progress in that regard. My question, really, is this (and it is two-fold): is there a VBA-replacement pathway amongst the LibreOffice development team? if so, is some flavour of Basic still being supported or (as I fervently hope and wish) is …

with regard to macro development in LibreOffice. I read on Charles Schultz’s blog a recent entry that suggested LibreOffice doesn’t have an actual development team (as in: hired developers) to move LO forward:

“At this point, it should be clear that at least in the case of the Document Foundation, we don’t hire developers to work on LibreOffice. But we feel there’s a difference between being a non profit entity distributing t-shirts and an entity actually supporting and growing the project. As such, we have overcome the lack of skills and time to develop an Android client by dedicating resources to this development, enabling talented developers to work on this project during a fixed period of time and funded by the foundation. Clearly, if such a development had been so easy we would already have an Android version.”

– mind you, I may have misunderstood the remark, of course. In any event, is any development currently being done on the programming interface (the VBA-ish end of things) or is that still in Oracle’s camp? And if this aspect of LO is currently under development, where can I get updates or possibly even contribute?

[oweng]

Charles Schultz’s blog a recent entry that suggested LibreOffice doesn’t have an actual development team (as in: hired developers)

The reference was to The Document Foundation (TDF) rather than LO. The are paid developers working for various companies that develop/support features for the clients of those companies. This is not to be confused with supporting requests from public individuals.

As my prior answer indicates, API access is not a priority b/c it creates far more problems than in solves and the various requested functionalities demand a considerable amount of work (that is best paid for by a large corporate entity).