Quote:
geit wrote:
OpenSource only causes incompatible and uncontrollable forks. And we already have that with MUI.
Of all the OS components nothing is nowhere near as horrible as MUI for creating compatible reimplementations because the autodocs and dev docs are nowhere near good enough. Some things are not documented at all (TAG_IGNORE, special treatment/filtering/... of attributes/methods in certain classes, ...). Some things are documented wrongly (attributes which know OM_GET).
The "real/true" MUI "owners" often give the impression that given a specific API and (auto)docs there is only exactly one possible way to create a reimplementation that "matches" the docs/API. So just follow the docs/API headers and you end up with compatible code. Not so with MUI. From one and the same MUI doc/API you can create countless variations which all may result in slightly or hugely different behaviour, even if all of them follow 100 % the info from the doc and the API.
There are also some buggy things in MUI itself. Like MUIA_ShowMe. To be compatible you are not even allowed to make a non-buggy version of this. You would need to reproduce the exact same buggy behaviour to be really compatible. Great ...
And btw, didn't MUI4 introduce it's own share of incompatibilities with MUI38? (list class?)
