libreccm-legacy/ccm-themedirector/doc/theme-standalone
pb eaaf561d73 Umbenennen von ccm-ldn-theme in ccm-themedirector.
Gleichzeitig Einführen einer neuen Infrastruktur für themes:
Es gibt nun ein Verzeichnis ~/themes/ in das alle theme bezogene Daten
migriert werden sollen. Das sollte im ersten Schritt mit den Applicationen
erfolgen, die ihre Dateien in ~/__ccm__/apps ablegen. ccm-themedirector nutzt 
bereits diese Infrastruktur.  Die alte Infrastruktur mit ~/packages und
~/templates und ~/static bleibt übergangsweise in core und cms  erhalten.

Das gibt uns die Möglichkeit, Mandalay als neues / alternatives Standard Theme
in die Standard Distribution einzubauen.  

Update Script erforderlich: 
ccm-themedirector from-version=6.6.0 to-version=6.6.1


git-svn-id: https://svn.libreccm.org/ccm/trunk@800 8810af33-2d31-482b-a856-94f89814c4df
2011-03-27 11:27:05 +00:00
..
README Umbenennen von ccm-ldn-theme in ccm-themedirector. 2011-03-27 11:27:05 +00:00
bebop-define.tld Umbenennen von ccm-ldn-theme in ccm-themedirector. 2011-03-27 11:27:05 +00:00
bebop-show.tld Umbenennen von ccm-ldn-theme in ccm-themedirector. 2011-03-27 11:27:05 +00:00
web.xml Umbenennen von ccm-ldn-theme in ccm-themedirector. 2011-03-27 11:27:05 +00:00

README

As of CCM version 6.6.1 package ccm-ldn-themes became a generic package and
has been renamed to ccm-themedirector.
All names below and anywhere in the files should be adopted accordingly.

Up to APLAWS version 1.0.4 theme had been installed into its own
application context: [webapps]/ccm-ldn-theme.

Now it is installed inside the main APLAWS application context along
with all other applications.

If shortcuts should be installed as its own web context again following
modifications are necessary:
1.  remove webapp="xxx" from application.xml
2.  move the files in this dir to WEB-INF/
3.  change src/com/ad/london/theme/ThemeApplication.java 
    method getServletContext() as back to "/files"
4.  edit __ccm__/.../xsl/index.xsl according the comment
5.  edit in ccm-ldn-aplaws /web/__ccm__/themes/aplaws/theme.xml
    according to the comment


Running it in its own webapplication context nevertheless is not suggestive.
It needs several xsl files of the main application (esp. core) for basic
operations, which hac been directly mapped from the main applications directory
tree into its own directory tree. So no module separation is possible, no
security context useable etc.