New Quickcast: Manager plugin - QuickManagerNav

Update: Articles support is completed. download latest version at github.

Regards,

pepebe

Sounds good. i'll keep an eye on this.

Very nice. I was a little puzzled as to what use this would be, but once I've used it a bit I find it very useful. No need to keep switching in and out of the Tree tabs, not to mention opening and closing folders and scrolling around in the Resources tab.

Hm. The "Continue Editing", "Add Another" and "Close" buttons are missing. Is it supposed to do that?

Ok, I see in the first post that this is intended. Since I only occasionally use the "Close" button, never having used the others, I suppose it's just as easy to click on something else (like the Dashboard) if I need to intentionally close a resource so that it's not locked any more.

I like that the Add New button creates the new resource in the same location as the open one. If I don't want it there, it's easy enough to drag it elsewhere. That's a lot easier than scrolling around opening/closing folders and right-clicking to specify where to create a new resource if it's not in the root.

Quote from: sottwell at Apr 13, 2014, 12:00 AM

Ok, I see in the first post that this is intended. Since I only occasionally use the "Close" button, never having used the others, I suppose it's just as easy to click on something else (like the Dashboard) if I need to intentionally close a resource so that it's not locked any more.

The plugin automatically closes your resource it you move over to another one or you create a new one.

It triggers:

MODx.releaseLock(MODx.request.id);

before you leave the resource. Something that, as far as I know, still doesn't happen if you click on an item in the tree.

Edit: Your post got me thinking and I realized there are use cases where the original "close" / "cancel" buttons make sense. Have to ponder about it for a while. Thanks for pointing this out.

Quote from: sottwell at Apr 13, 2014, 12:00 AM

I like that the Add New button creates the new resource in the same location as the open one. If I don't want it there, it's easy enough to drag it elsewhere. That's a lot easier than scrolling around opening/closing folders and right-clicking to specify where to create a new resource if it's not in the root.

That's the idea. I wrote it for working we resources with a lot of children. It saves tons of time while creating the basic content of a new project or while editing a lot of resources in a row.

Cheers,

pepebe [ed. note: pepebe last edited this post 12 years, 5 months ago.]

I'm working on the presentation I'll be giving in September, and I think I might add this to my basic workflow - the list of a handful of useful add-ons that I always install right away to make life easier (Ace, pdoTools, cssSweet, ClientConfig, FormIt, etc).

I'm happy you find it useful.

In the future this will become a package so anyone can download and install it over the repository or include it as a dependency. Don't know how long this will take as this will be my first extra and I have to learn how packages are prepared.

Regards,

pepebe

@pepebe, I had a quick look at the updated version and it works very well in the Article container. I haven't tested it with a child article just yet.

But this is a great tool indeed.

Quote from: pepebe at Apr 13, 2014, 04:21 AM

In the future this will become a package so anyone can download and install it over the repository or include it as a dependency. Don't know how long this will take as this will be my first extra and I have to learn how packages are prepared.

Regards,

pepebe

Take a look at MyComponent http://bobsguides.com/mycomponent-tutorial.html.

You may have to modify the dirctory structure and possibly some filenames, but it will make adding language strings much easier and future releases will be a piece of cake.

I can probably help with the config file if necessary.