Improve model browsing performance

Currently if the user expands the model in Model Browser in Architect or when e.g. menu is being loaded when starting ORIGAM Server, all Menu related XML files have to be loaded and model instances cached. This takes too much time. Another example: Expanding entity list does not only load the folder names but also underlying entity names with everything else (entities, fields, row-level security rules etc.).

It would be better if there would be a lightweight API that allows retrieving a simple list with limited information (Id, Name, number of children) that would be just enough to support model browsing and let the whole deserialisation happen only after the item has to be fully loaded (e.g. edited).

I fully support this idea.

So make sure you vote it up :slight_smile:

My vote has been cast.