May be, rename to getDebugName() would make ppl understand it is not to be used as a base to implement, but only eventually in debug.
Composition like in:
panel.getControl(GuiControl.class).setComponent("text",...), mmm… that’s good indeed. I will see if I can change some things to use it instead.
Oh yes, more exposed things are good, but I guess they will require extra testing time to grant they were exposed properly too.
The ConditionalState allowed me to be less precise when and where initializing such state dependencies. I just skipped frames until objects were ready, even fully initialized and “stabilized” in cases, to let the ConditionalState start its proper/granted/safe initialization.
So I only created a configure() (for really basic/simple settings) and postponed the initialization based on custom conditions, so my ConditionalStateManager (that is a JME AppState) was created to make the ConditionalStates wait.
After that was fully implanted here, things started initializing very smooth, it spares me a lot of time concerning finding out (have it been documented or not) what has to be setup/configure/initialized before what else.
[blabering/thinking about my own projects]
Protected or private (or composite)?
I really like private (concerning less trouble),
but protected is tempting (like we throw the responsibility on our library users)…,
Extensible composite sounds best indeed. But every tweak a user may want to do may require another thing to be exposed.
Ex. If I create a set() for every field, that could work I guess (but I don’t see how that would result in something much different than protected in terms of creating troubles).
Basically everything that is exposed may cause trouble, and to prevent that we need test time.
And, by not exposing untested fields may make the library more reliable, what I think is best on the long run… but may throw creative ppl away hehe…
Mmm… weighting: small team + reliable + long run + life time + less trouble VS creativity requests/interest + more trouble. The former wins indeed, and a fork is always possible for creative ppl.
I dont like it but I think I will go private too, that will make me more tranquil on the long run hehe… thx!