Hi Fabrizio This sounds great... but I don't know if we should just dump the dms in favor of the media module repo: - The media module repo only allows certain file types - What about the future development iterations of the dms? - Etc. etc.
So again: What is the reason for you _not_ to use the DMS to store internal files? I mean you can extend dms nodes to whatever extent you like (e.g. to store preview images). -will On 22.06.2010, at 11:44, Fabrizio Giustina wrote: > > Hi Will, > well, it depends on the usage, but for handling pdfs (or also other > docs) you may choose to store them in the media module too... > Since the release 4.2 there is also the media type "pdf" added by > default, with some additional goodies compared to the dms like preview > generation, parsing of meta data (number of pages and similar...) that > you can use. Also configuring other specific media types for other > formats is easy... > > At the moment the main difference is the lack of the document history > and no webdav interface, but if there is interest in it we may think > to add them in future. > > fabrizio > > > > > On Tue, Jun 22, 2010 at 9:50 AM, Will Scheidegger > <[email protected]> wrote: >> >> Great news, Fabrizio, thanks. >> >> We've looked at the module more recently and especially like the specialized >> user interface. The only thing that kept us from using the module is the >> fact, that it keeps its files in a separate repository. We don't want to >> have to explain our users why they should place some type of files in the >> media module and some in the dms. And more important: We would like our >> users to be able to benefit from future development of the dms module, i.e. >> a webdav interface etc. >> >> Wouldn't it be possible to use the dms to store the internal resources in >> the dms and have the module scan the dms for available media files? >> >> Best regards and thanks for the good work! >> -will >> >> On 22.06.2010, at 09:28, Fabrizio Giustina wrote: >> >>> >>> Dear Magnolians, >>> we are pleased to announce the release of the Simplemedia module >>> version 4.2.1 for Magnolia CMS. >>> >>> The Simplemedia module makes the management of images, videos and >>> other assets easier both for users and for developers. It offers a >>> centralized repository for digital assets with a specialized user >>> interface, usable for internal resources or for externally linked >>> ones. Version 4.2.1 works with Magnolia 4.0 and up. >>> >>> 4.2.1 is a minor release, mainly containing bug fixes and small but >>> useful enhancements. Among those: >>> * improvements to the playlist management interface (batch selection) >>> * XSPF (XML Shareable Playlist Format) support >>> * more image type supported (some subset of jpeg files with >>> particular color profiles, and ico files!) >>> >>> >>> All the details are available at: >>> http://www.openmindlab.com/lab/products/media.html >>> >>> ... or you can skip to this page for a direct download: >>> http://sourceforge.net/projects/openutils/files/ >>> >>> >>> Have fun >>> - the openmindLAB team >>> >>> ---------------------------------------------------------------- >>> For list details see >>> http://www.magnolia-cms.com/home/community/mailing-lists.html >>> To unsubscribe, E-mail to: <[email protected]> >>> ---------------------------------------------------------------- >>> >> >> >> ---------------------------------------------------------------- >> For list details see >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> To unsubscribe, E-mail to: <[email protected]> >> ---------------------------------------------------------------- >> >> > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
