>Feel free to work on them. I will give you CVS
>write access if you want.
Jon,
I'll take you up on the write access when I'm a little more comfortable with
CVS ( i'm currently going through your recommended reading).
In the meantime, I've already began to make additions and changes to the
admin stuff. I know you are all very busy, but would you prefer that I
bundle my stuff into an admin folder and send it to the list? That way
anyone that wanted to play with it could just drop the stuff into their
local copy and try it out.
Also, I 've noticed some changes to the admin stuff in between snapshots.
If anyone else out there is currently
working on this stuff. Please let me know so we can collaborate on it and I
don't step on your toes.
Here's what I've added so far:
** Admin main page ( So you can just add a single link from your main
default screen)
** Admin navigation
** Moved some of the database access from a screen to an action.
** Modified the Admin layout
** Started to "pretty up" some of the screens
** Added a SecurityCheck class to the org.apache.turbine.util package.
The SecurityCheck class is intended to hide some of the logic to check roles
and permissions in actions
and screens. So you can use it for any turbine application . Instead of
doing this kinda stuff all the time:
if ( !(
data.acl.hasPermission("system_total_access")
))
{
data.setMessage("ChooseOrFindTurbineUser was attempted without
proper permissions.");
data.setScreen("WrongPermissions");
return;
}
you can just do something like this -
SecurityCheck check = new SecurityCheck(data, mymessage,
wrongpermissionscreen)
if ( !check.isAuthorized(" system_total_access") )
return;
Hopefully it'll help prevent mistakes in doing authorization checks.
I hope to have all the admin stuff up and running in the next week or so.
Then I'll work on updating the
build.
Merry Christmas,
Dave
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
