What do you think if we just "pull in" the actual components for user management / ACL from the current CMS - a "stripped down" administrator ? This way we could concentrate on com_tracker which is what we are interested to get up running.

We could then start to refactor the core extensions. Starting like this it might be nice to backport those changes to the CMS, as a side effect.

I mean, I just feel afraid of the amount of time necessary to implement a complete user management from the scratch.

What do yo think ?

My thought at the beginning was to do just that with com_users. We'd need
to add something to the application to trigger the legacy component handling
for it, otherwise it should work as is. Plus, a lot of the code for user
management is self-contained in the component or a Platform class.

From: Nikolai Plath notifications@github.com
Reply-To: JTracker/jissues
b.com>
Date: Monday, October 8, 2012 3:16 PM
To: JTracker/jissues jissues@noreply.github.com
Cc: Michael Babker mbabker@flbab.com
Subject: Re: [jissues] Administrator Interface (#3)

What do you think if we just "pull in" the actual components for user
management / ACL from the current CMS - a "stripped down" administrator ?
This way we could concentrate on com_tracker which is what we are interested
to get up running.

We could then start to refactor the core extensions. Starting like this it
might be nice to backport those changes to the CMS, as a side effect.

I mean, I just feel afraid of the amount of time necessary to implement a
complete user management from the scratch.

What do yo think ?

‹
Reply to this email directly or view it on GitHub
https://github.com/JTracker/jissues/issues/3#issuecomment-9238705 .

We have admin. Closed.