[Exist-development] Questions on packaging for new administration applications

[Dan M. <dan...@gm...>]

Hello Wolfgang and eXist developers.

I hope everyone is doing well in the new year.

We have some questions for the team package the new administration tools we
are prototyping and some other new tools like an index adviser we are
working on.

1) Do you think that some or all of these tools should be optional in an
installation?  Do we want to think of them as part of the core eXist system
or are we now entering the more complex world of "applications"?
2) If these new tools will be considered "Applications" how should they be
added or removed from eXist site?  How should we track shared resources that
they depend on?
2) Should we create some configuration file entry to have "admin
applications" be conditionally loaded or not load into a system?  Should we
have an XForms application to manage this configuration file?
3) Some of the tools will use XSLTForms, the Blueprint CSS frame and JQuery
JavaScript libraries.  Is there a central place that these should be
installed?

Let me know if you have any guidance for the team.  Perhaps we should write
up a short term plan and some longer term strategies as we move toward a
full OSGI environment.

Thanks - Dan & the New Admin Client Team