Hi everyone,I have a big big interest in this project and I hope to get helps from other developers.
Could you please tell me some of your ideas about this one? Something like your requirements of the upgraded media manager. Any advices and resources will be much appreciated.
Thank you very much,
Quan
--
You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-cm...@googlegroups.com.
To post to this group, send an email to joomla-...@googlegroups.com.
Visit this group at http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
For more options, visit https://groups.google.com/groups/opt_out.
--
In Joomla 3.2
- Database-driven media manager. Media is accessed through id in database. Database file include file name, location, author, created date, number of downloads.
- Allow renaming, copying of files. This will be done by query to database so we don’t have change the link after renaming the file.
- Automated creation of thumbnails with configuration for webmasters.
- Support more media types with plugins. Plugin will decide how to treat with file types, the 3pd will have to develop this for their extension. Our media manager will have some basic controller for usual file types.
- Media manipulation using JImage (or external sites such as SplashUp).
- Access control list.
After that, expected in Joomla 3.5:
- Ajax interface, allow drag-and-drop copying and moving file.
- Integration with CDN.
- Support for creation of collections of media.
Hi everyone,I have a big big interest in this project and I hope to get helps from other developers.
Could you please tell me some of your ideas about this one? Something like your requirements of the upgraded media manager. Any advices and resources will be much appreciated.
Thank you very much,
Quan
The implementation of FOF into Joomla was pulled a while ago. Has this topic been revisited?
I don't think it's an issue in this case,
but if it is, it would be FoF's responsibility to fix the bug, since JTable is a core class. The RAD layer has to work with the other components (which use the current core classes).
--
Do people think that types of media should be stored separately (the way a template or /media has css, js, and images folders)? Or does it not matter, since the types can be filtered using the database?
On Monday, March 4, 2013 11:25:32 AM UTC-8, Nguyen Tran Quan wrote:
> Hi everyone,
>
> I have a big big interest in this project and I hope to get helps from other developers.
>
> Could you please tell me some of your ideas about this one? Something like your requirements of the upgraded media manager. Any advices and resources will be much appreciated.
>
> Thank you very much,
> Quan
My ideas for Media Manager are based on examples present in some of the file navigation programs we use in Operating Systems (Linux, Mac OSX, and Windows) everyday. There are also examples we can use from Joomla.
Simple List...
--Multiple Presentation Types (Icon, Tree/List, Column, maybe even a fancy cover-flow view type, a Mac OSX like presentation.)
--Default/Configurable Icon Set For Media Types
--Component Folder Scope Control (Admin might want to specify directory users can look into only for com_content)
--Access Level Control on directory and file level with batch operations.
--Left side pin bar (Filter for specific media types like video, images, or text files. We could have global filters and per component specific filters)
--Table Column Sorting
--Configuration Options to control what is displayed per view type
--Media Manger specific search