externalize entries and operations from <LPMX><OPER>
Author: firstname.lastname@example.org (fmoritz)
in the <LPMX> and <OPER> it's very difficult to manage / look at what's really in them even the ude editor tempt to show the developper the entry and operation lists
if entries / operations would be declared undependant of these triggers it'd be easier to manage them.
example: put some tags for every changes in a comment field for each entry / operation etc...
Why do not create an operation and entry table (uxoper and uxentry like uxregs...) for components ?
when we are fixing our application's release, restauring previous version , so we could better manage the source code and when different developper are working onto the same component for different raisons.