That depends. If I have your XML code, and my own custom widgets, do I have to do anything extra to get my widget supported in XML and in your design tool?
If nothing extra is required, then a metadata API is being used, and my custom widget is automatically registered with it. That same metadata API should be available to allow any other DSL to do the same. But I hope that you don’t disrespect the user community so deeply as to have this capability locked up in private?
If this still hasn’t been implemented, I am sad, after all the discussion we had about it. It’s enormously helpful to have a single API that just works for all standard widgets and any custom ones. This is what I was hoping would happen when I opened the original issue.
Well, that’s certainly one way to do it. It’s very odd to mix up syntax with semantics in that way. I assume that all the “XML parsers” for the standard widgets are now part of the closed-source XML API? So in fact they do implement the long-requested metadata layer, and you do plan to keep it private.
I hope your users don’t punish you for treating our input that way.
Sorry, but since you attacked us with no valid reason (that is not doing even the most basic research before claiming we made legal misuse) I don’t like to go into technical discussion with you.
I am still waiting for evidence that you did not. But it seems that you have settled for something much less capable and more annoying to use than we were asking for anyway. So LVGL remains the wrong solution for many valuable applications I had hoped you would want to enable. Your loss, as well as mine. I’m sorry that it ended this way. Let me know if you decide to revisit those poor decisions.