DocManager Revolution Conversion

I’ve raised this ticket for the DocManger evo to revo conversion : http://svn.modxcms.com/jira/browse/ADDON-35

This is the initial release of the Doc Manager Revolution conversion. It is a faithful copy of the
Doc Manager module from Evolution with the following exceptions :-

1. There is no Sort tree function, revo doesn’t need this, you can drag and drop resources around
directly in the tree view.

2. You can’t select document id’s from the tree at the mo, you have to use the manual document entry
method a la evolution. I need to implement a drop target on my windows somehow here, this will be
done in an upgrade.

Other than that it’s functionally complete.

Build and install as normal.

The ticket contains more nitty-gritty coding level stuff probably only of use to the core devs.

Interested parties can also get it here :- http://bitez.hobby-site.com/index.php?id=63 under projects/revolution/components for now. Note this won’t be maintained once its gone into the component repo’s.

Nice work shamblett!! I’ll be sure to check this out in the next few days

Kudos and thanks.

You up for your next assignment yet?

ou up for your next assignment yet?

Yes no probs, you guys best know what needs doing next, just point me in the right direction.

OK guys, I’ve turned the presentation into a tabbed pane accessible from the Components menu, this is much spiffier and cures a few little other probs I had. I’ve got this in my own repo at the mo, I’ll check this in to components when the new directory layout issues are solved, see the last entry here http://svn.modxcms.com/jira/browse/ADDON-35 if you haven’t already seen this and hopefully sort this as well.

Quote from: shamblett at Mar 13, 2009, 10:12 AM

OK guys, I’ve turned the presentation into a tabbed pane accessible from the Components menu, this is much spiffier and cures a few little other probs I had. I’ve got this in my own repo at the mo, I’ll check this in to components when the new directory layout issues are solved, see the last entry here http://svn.modxcms.com/jira/browse/ADDON-35 if you haven’t already seen this and hopefully sort this as well.

shamblett:
I might have to make some changes to the structure of the component; we’ve decided to move the targets of where things are installed recently, to allow for more core/assets separation. In other words - files you dont need to be web-accessible will go in core/components/docmanager/, and web-accessible files to assets/components/docmanager.

I’ll be committing a revised TinyMCE 3PC to modx-components later today that will illustrate this structure change. I know the tutorials are a bit out of date now.

Is it okay if I go ahead and make some changes and cleanups to the DocManager 3PC?

Thanks for all your work.

Yes no probs, was only really concerned about the hard coded path I mentioned in the ticket. Do your stuff then I’ll do mine over the top, we’ll get there in the end.

More of a general question, can we/will be able to gray out menu entries dependent on role/privilege? I ask because maybe not all manager users should be able to access the docmanager component for instance. This is best done by graying out the entry on the component menu and not letting the user invoke the function at all, this is pretty much standard practice in GUI implementations.

Admittedly I’ve not looked at this in depth but from my current understanding we can’t do this, correct?

Thats a great move shamblett! Keep up the great work.

Note this won’t be maintained once its gone into the component repo’s.

What that means?

Hi Zi, all that means is that I won’t be updating the zip file on my site, the best place to get the latest and greatest from is the component repository.