How to implement a new control for Base.... your missing and to add it would be simple..... you have Draw and word.... combined them under one logic---- HTML 5..... you have export HTML correct.... all dom xml standers correct.... create a control that expose the interface in base..... think about it i could create a complex vector image in draw.... and load it in a base and control it... with a data.... like a chart... or a blue print... this is not a hard control to build you have all the logic.... its just a form handle executing draw as a control...with events and its dom tree see word and drow are the same under HTML5.... their just 2 different tool wizards under the same logic.....with a header file.... so base form with a line and shape control with webkit control will bind all your programs as one in logic.... see now i can make my own controls in the webkit control.... i do this in android.. see your base date form is draw.... all under one inherent logic code....
see now you only upgrade draw as an object... used by all office interface draw is word.... draw is web format draw is base form.. draw is base report draw is base form control builder... like in draw i could insert a control event on mouse click... load the raw file in the base control voila.... i now have what.... a programmable control made in draw that i can attach macro code to... and data.... xml dom forms....
let say i want to build a CNC machine.....i build it in draw...and connect in base to monitor it.... or program the object movements.... you have 3d in draw.... expose the nodes to create moving parts via base but 2D is all you need vectors automation paTHS
SEE in base i dont need all the event in a list.... what i want in the list are the ones i added..... by what draw....so to add new events i load it in draw to add new event or property to the dom that base form will show... this will speed up rendering time..your not loading 1000 properties.. its only listing the current possibilities in base... see the complex event list and properties are in draw.... so when i program i dont need to scroll down the empty entries in base.. i just see the ones i want... so it speeds up load time.... xml HTM5 is like that... you only add what you need...
see this will also speed-up your development time in base.... like why have all these empty fields to see.... when flicking from design views.... load time... if i need a new event i load it in draw and add it... its just nested in the doc that base needs to render.... so now i only see what i want to program when binding data.... see now your only build one program.... draw
when you upgrade draw you just upgraded office.... word is just wizard with template tools off.... draw think about it bug tracking and your fixing made simple off one rendering engine.. rendering engine would read and load objects base on the file being loaded... load time and memory space.... like i don't need a 3d engine if the tags are not in the loaded draw file.... layers and menus.... wow.... i just made a tool bar in draw... that shows up in base.... and any HTML web programmer knows the logic.... document.dom.object(11)visible = true base form event code.... from a macro view... yet its just a draw document
see all this can start with simple ad-don to base.... draw control in a form.... and a template in draw to build... show hide ruler... leave what you have as light controls.... wow... now i get a ruler control in base... like i said everything is in draw and is exposed in base macro via doc.dom simple add on
when you do this you will surpass Microsoft office..... and all your doing is adding a draw control....to base to bind data by code with... on form load.... render control.... now bind data doc.dom.object(12).propertery.fieldvalue = access2base = recordset.field(2).value see all simple codding can apply with very little programming from you... on click event added in draw and is exposed as an event in base.... the load control would recognize the event with and ID passing it to base macro... you have all this logic in draw....for draw to work dont you... your just building a door.....
Please STOP. This is not a forum site and this issue already is TL;DR for any developer. Bugzilla is not a great tool to post new findings every few minutes and having a self-conversation. LibreOffice mailinglist could be a better place to get audience. As LibreOffice is open source project you can get involved and contribute all this simple and little work programming as a patch or add-on...
Make a draft of what you want to describe, work on it and create a new bugtracker when you're ready.