Re: [Exist-development] admin panel

[Dmitriy S. <sha...@gm...>]

On Mon, 2010-01-18 at 15:35 +0000, Thomas White wrote:
> Dan,
> 
> > 1) How to package the "web-admin" applications together in a set.
> Have a directory|collection as an entry point for the admin
> application and sub-directories|sub-collections  for all
> sub-applications. This way dealing with the single entry point
> directory we can easily copy, move or delete the whole application.

+1

> > 2) How to share common libraries like Blueprint CSS files and JQuery.
> Sharing libraries across applications is a really bad thing especially
> then these libraries have so many versions.
> Keeping the files as a subdirectory of the the main application entry
> point directory is a easy way to share the code between
> sub-applications.
> With such cheap disk space and small library files this is not an issue.

As opposite solution: application name & version as collection name for
lib's applications.

> > 3) How to make these applications "portable" and db collection location independant
> If you use the approach with a single application entry point
> directory (see my answer at point 1.) then using only relative paths
> will do the job perfectly.

+1 for relative paths

> > 4) How to build install and uninstall scripts
> > 5) How to document the basic functions like the RESTadmin actions so they can be reused in all the applications
> Some time ago I offered a URL schema that is task oriented, it is
> implementation agnostic and it allows to control the access to the
> admin functions to be controlled in details. I still believe is not a
> good idea to put all actions for an object in a single place, because
> there will be no formal way to distinguish how to give partial access
> to a sub sets of the actions.
> 
> I hope this will help.
> Thomas
-- 
Cheers,

Dmitriy Shabanov