When will the Resource Browser be updated?

Quote from: sottwell at Jan 29, 2013, 03:34 AM

While the existing file browser is actually built-in to the Manager and would probably be very difficult to replace in the Files tab, I don't see why a plugin like that for Rich Text editors could not be used for TVs and RTEs, which is what clients mostly use it for. In fact, I seem to recall mention from somebody that did implement a different resource browser in TinyMCE or CKEdit.

I think about OnDocFormRender plugin to load .js file which should replace MODx.combo.browser or MODx.browser object with a new one containing call to external resource manager. BTW, KCFinder integration in Evo is made in similar way - it replaces 2 files containing MCPuk calls with new ones containing KCFinder calls.

it would be also great to have implementation of online image editor,
something like:

http://pixlr.com/
http://pixlr.com/developer/api/

Quote from: gOmp at Jan 29, 2013, 12:45 PM

it would be also great to have implementation of online image editor,
something like:
http://pixlr.com/
http://pixlr.com/developer/api/

I would not want an external online editor. I prefer those things internal to make sure that the API stuff allways works. I need a reliable system.

The NewsPublisher extra has its own file browser because the Manager file browser didn't work well in the front end. The NP browser is done in ExtJS, believe it or not.

Quote from: BobRay at Jan 29, 2013, 08:27 PM

The NewsPublisher extra has its own file browser because the Manager file browser didn't work well in the front end. The NP browser is done in ExtJS, believe it or not.

Hmm. You mean the browser in TinyMCE? It looks exactly like the regular resources browser.

We had a first community discussion about Add-ons yesterday on a Google Hangout. It was very productive and they will definitely continue—I'll make sure to announce them broadly going forward. I'll also be writing up the overview of the conversation and posting it to the blog. The net net from it is that we really do want much more people in the Community participating in the management of the code, not just for the Add-ons, but also for the core, the manager, xPDO, etc.

The current media browser needs a lot of TLC. I personally also agree it needs to be a part of the core distribution. I suspect it honestly would take a week, maybe much more as Susan suggested due to all the interactions with ACLs et al, to have a fully QA'd and supportable/distributable alternate browser.

I think it should be more loosely coupled, as the RTE is, so that people can make extras out of their favorite file browser/manager apps. No matter which one you embed in the core, a month or a year down the road there will be a better one that everybody is clamoring for.

If it would take only around a week, maybe we could crowdsource fund it ?

Quote from: g5604 at Jan 30, 2013, 08:47 AM

If it would take only around a week, maybe we could crowdsource fund it ?

Count me in for funding. But it will take far longer than a week, unless you're talking strictly about programming time. Who will design it? Who will beta test it? Who will give feedback? Creating a really good user interface for anything takes a good deal of time.

I think the idea is to take a 3rd party file browser and do a proper integration.