[Aplaws-devel] [aplaws - Developing on APLAWS+] RE: ccm.home and r1919

[Aplaws D. L. <apl...@li...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=7407641
By: pboy

Hi Brett,

it would be very very helpful if you could contribute your experiences and provide
a patch. Your patch regarding ResourceParameter  was the "breakthrough" to get
the problem resolved.

Regarding rewriting of xsl files: I had (rather) a short look into some files
and found a huge amount of references to other xsl files (includes) which contain
the ROOT directory as a fix part of the path. So I suppose we have to have a
look into every file (or let grep do that) to check for absolute path
specifications.

My idea is: if we have to look into nearly every xsl file, we should use that
occasion to thorougly clean up the web directory structure as well. Currently
it's really a mess. Files a spread all over the directory, functional identical
files are stored at different locations, some files are doubled at different
locations, theme files are mixed with logic files, etc.

It is nearly impossible to maintain such a code structure. But in order to improve
APLAWS's usability, we must lay emphasis on themes / easy themability. That
involves a lot of maintenance work.

A possible structure of the web dir might be:

- themes
- themes/internal (assembles all the files of the current build-in "theme")
- themes/mandalay (the new, modularized and easy configurable theme developed
in Bremen)
- themes/public (maintained by ccm-themesmanager aka ccm-ldn-themes)
- themes/devel  (maintained by ccm-themesmanager aka ccm-ldn-themes)
- themes/default  (maintained by ccm-themesmanager aka ccm-ldn-themes)
- themes/aplaws (current default theme)

- scriptlib
- scriptlib/xinha
- scriptlib/fckeditor
- scriptlib/other Javascript

- templates (jsp per module)

- WEB-INF

I suppose you concentrated on the web.xml file and the dispatcher configuration.
So we could split the work.


Peter



______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=368401