On Thu, Aug 17, 2000 at 11:56:18AM -0400, Dan Diephouse wrote:
> There was talk of including a jar that had screens for user
> administration.  What is the status of the user administration pages?

Hi! Okay, I'm back (I've been completely sidetracked for the last month
so I apologise for not having got further with this earlier).

I've just committed code/templates for the admin stuff as well as some
templates that I think can form the basis of the default Turbine install
(i.e. TDK).

The code for the admin stuff is in org.apache.turbine.admin. In order
to prevent name clashes the actual classes end up with slightly
longwinded package names like:

org.apache.turbine.admin.screens.admin.user

I thought this was the best way to keep the classes away from other
stuff.

The templates are in src/templates - feel free to hack away at the look
etc, I mainly based what I did on scarab (from which I nicked the code
and templates for the admin stuff).

Here's what I propose doing next (not until tommorrow now):

1) Alter TR.properties so that its all setup to use the default
templates/admin stuff. This will include making the default session
validator WebMacroSecureSessionValidator which I also committed today.
This is basically WebMacroSiteSessionValidator with the code to enforce
a login uncommented.

2) Alter the war-webmacro target to pick up the templates from
src/templates instead of examples/webmacro

Any objections?

Also as can be seen from my index.wm I want to include the new Turbine
logo on the page. The natural way to do this with Tomcat seems to me to
be to put the GIF in turbine-webapp/images. I don't think we have a
mechanism to reference static content within the current context though
do we? How about I add a setStaticContent() method to DynamicURI which
allows this. The other alternative would be to use the ImageServer but
this seems somewhat like overkill to me...

I've also got a WebMacroSiteError class to add (it's at home so I'll do
that tommorrow) which will allow replacement of the Error screen with a
template (the template's already there - error.wm).

So unless I get negative feedback I'll proceed with my plans tommorrow.
Then we need to work out how to get all this stuff into the TDK as well.

(Note that although at present the admin stuff doesn't build into a
separate jar, I've set it up so it's not visible unless
org.apache.turbine.admin is present in the modules path - easy to
disable).

-- 
Sean Legassick
[EMAIL PROTECTED]
                                  homo sum: humani nihil a me alienum puto



------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?:           [EMAIL PROTECTED]

Reply via email to