Hi Rouslan,
I was just reading your weekly report. I have a question about the
'refreshing of navigation' :
You mention that the state of the navigation (which branches are open)
has to be remembered, when sending it over to the client/browser. Does
this mean that the entire navigation tree is generated server side on
every change to the nav tree (f.e. clicking on a branch to open it, or
when tables/databases are added/deleted/renamed/...)? Or only in case
of a full refresh (or first load)?
Would it make sense to keep the nav tree state stored client side and
let the script repopulate the tree based on data it gets from the
server, after a request initiated by user interaction (navigating the
tree) or when the server sends new/changed/deleted tables when
something is changed by the user in the main panel (triggering
refreshNavigation)?
Or would this overcomplicate things?
--
Kind regards,
Dieter Adriaenssens