Hi.
Recently I analysed application startup code and I'm upset of two things:
1) Although there is afterSetup hook method, there is no beforeSetup hook.
Because we may need code to be run before setup (see wizard
generated application),
we have to override setup method code. This is not a problem of course,
but it breaks before-after hook chain. We don't need afterSetup
method as well.
2) dApp class has startupForms method and this code is in fact
duplicated in wizard
generated example in main application module and we can call this
method
before app.start() instead.
Wait a minute. But what if we have SecurityManager and first need to
login?
Then default form with his data will be visible before user
successfuly logon.
Of course we may call it in afterLoginSuccess method but we have to
duplicate
this code in case we decide to turn SecurityManager off.
I think, if I have at my disposal method called after
SecurityManager call
and before MainLoop begins, everything will work more smoothly and
will be more consistent.
You may say that's birdseed but I think I'm right a little bit.
--
Regards
Jacek Kałucki
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/[email protected]
