[TYPO3-dam] DAM 1.1 beta01 for download - (dam_downloads)

[Franz Koch]

Hi guys,

also add me to the guys developing a DAM frontend - started with a gallery. I tryed to get a team for a general 'gallery' (that would also be a DAM gallery/frontend) on the ECT newsgroup. You can have a look at my post there named 'flexible DAM-frontend : coding team, ideas, contributions'.

I also got a working extension [1] that I currently use on a website [2]. I modified it a little bit (removed dependencies) so that you can test it. Simply install it, add the plugin to a page, add the static template and voila - the gallery is up and running. The extension doesn't use the 1.1 API yet, so I did some tricks for the indexed FE upload of images. If you like - just have a look.

Here two quotes from myself I posted in ECT NG about the current features of my extension:

> ----------------------------------------
> 
>> as much as I know, Volker Graubaum allready developed a full-featured DAM-gallery with FE-lightbox, FE-upload and all that stuff. I wrote him a mail, but didn't get any answer from him. This extension is allready in productive use for a stock-photo site - but I've forgotten the name of the site. He mentioned it in a podcast interview of a german magazin.
>>
>> I myself also need a highly flexible DAM-based gallery. What I've got so far is a flexible extension using DAM-categories, fe-user relations, adding a BE-DAM selection filter for images by fe_users (another extension), common views (single, search, list), a rather flexible sorting-mechanism via flexform and fe-upload with DAM-indexing. FE-uploads are also categorizeable. It's working - but needs further development. I also plan to support stored DAM-selections as "gallerys" (if that works).
>> It can be used as gallery or as simple DAM-frontend, as the output of every filetype is configurable through TS (it's at least planned and could allready work - I'm not shure exactly).
>>
>> It's currently used in combination with an extended tt_rating extension (for MM related ratings for any databasetable, optional user restrictions, rating-log, TS-rendering) on a live website [2]

> ----------------------------------------
> 
>> I can't tell if and how much this will be faster - I'm neither professional coder, nor an expert in this concern, but I can upload one of my extensions so that you can have a look on my wired code ;) in which I try to stay as flexible as possible with (I believe) no hardcoded query and a modified marker-'engine'. If I add a new field (let's say 'category') to my records table in the database (including TCA), I can do the following without having to touch the php:
>> - ###FIELD::CATEGORY### => returns a form-field based on TCA-settings (needs improvements though)
>> - ###VALUE::CATEGORY### => returns the pure unprocessed database value
>> - ###CATEGORY### => returns the processed value where the processing can be define in pure TS
>> - ###LABEL::CATEGORY### => label for the field - fechted by locallang and if not available from TCA
>>
>> I can also simply add a localizeable text placeholder as marker - let's say 'eventtype' by simply writing ###DESC::EVENTTYPE### (should maybe changed to TEXT::) in the template, which fetches the locallang value 'desc.eventtype' that can be freely defined with TS. No need to create multiple templates for special designs/needs. 


The code quality of my extension is not the best - I reused the code for 5 extensions now and there is also some old stuff in it which should be removed (like this 'nextStep' stuff). Just have a look if you like.

[1] http://www.elements-net.de/projects/T3X_user_gallery-0_0_1-z.t3x (not shure if I added english for the BE as I was in a hurry)
[2] http://www.triff-den-papst.de/community/mein-schoenstes-papstbild.html

-- 
Kind regards,
Franz Koch