[TYPO3-dam-devel] RFC #9403,9644: Missing media types

[Dan Osipov]

Ok, I gave it some thought, so here is what I propose should be done:

There needs to be a table, defining an extension, meta type, DAM type 
(image, text, application, etc), and an icon. The table would be 
populated with some defaults, and DAM would have a sub-submodule under 
Tools, that would allow one to add more types, and upload icons (which 
would be managed by the DAM - what an irony)

What do you think? Any problems with this approach?

Dan Osipov
Calkins Media
http://danosipov.com/blog/

Uschi Renziehausen wrote:
> Hi Dan,
> 
> do you have an approximate idea of how many hours might be needed to fix 
> it? We still have three weeks time (documentation and the sql-stuff for 
> selections), so if it can be done for 1.1 we should do it, because this 
> means one more oddity out of the way.
> 
> Uschi
> 
> Uschi
> Dan Osipov wrote:
>> That might be too much work at this point. So should we delay this 
>> until 1.2?
>>
>> Dan Osipov
>> Calkins Media
>> http://danosipov.com/blog/
>>
>> Uschi Renziehausen wrote:
>>> Hi dan :-)
>>> Dan Osipov wrote:
>>>> This is a good point.
>>>>
>>>> The files with the added types have been uploaded as undefined media 
>>>> types. They will remain as such. Any new files will be checked 
>>>> against the new media types.
>>>>
>>>> It would be nice to update all existing files to use the new media 
>>>> types, but I don't think its practical (in other words I don't know 
>>>> an easy solution).
>>>>
>>>
>>> As new filetypes come up every time and again, I think a submodule 
>>> 'Update media types' under tools would come in handy here. As far as 
>>> I can judge, the following tables are affected:
>>> tx_dam.type
>>> tx_dam_metypes_avail.type
>>>
>>> Also, some stored selections might not work anymore.
>>> Maybe also the general sys_refindex comes in as well?
>>>
>>> Uschi
>>>
>>>
>>>
>>>> Dan Osipov
>>>> Calkins Media
>>>> http://danosipov.com/blog/
>>>>
>>>> Uschi Renziehausen wrote:
>>>>> hi *.*
>>>>>
>>>>> while I like to have all those patches in trunk, with this one I am 
>>>>> in doubght about the consequences.
>>>>>
>>>>> media types (not filetypes!) have hardcoded uids as constants. As 
>>>>> soon as the first filetype of media type x is uploaded, we have it 
>>>>> in the database, therefore we need some kind of update script! 
>>>>> Currently the only way to update the database is:
>>>>> delete the files of that mediatype and upload them again.
>>>>> In my eyes this is a blocker!
>>>>>
>>>>> Uschi
>>>>>
>>>>> ben van 't ende [netcreators] wrote:
>>>>>
>>>>>> Uschi Renziehausen wrote:
>>>>>>> Hi ben,
>>>>>>>
>>>>>>> ben van 't ende [netcreators] wrote:
>>>>>>>> Uschi Renziehausen wrote:
>>>>>>>>> Hello Dan,
>>>>>>>>>
>>>>>>>>> can we perhaps have
>>>>>>>>> - the  OO spreadsheet and the new Exel stuff under dataset?
>>>>>>>>> - what belongs to OO impress and the new PowerPoint stuff under 
>>>>>>>>> interactive
>>>>>>>>> - the image stuff (OO draw) under image?
>>>>>>>>
>>>>>>>> OO draw is dataset. No way Image ;-)
>>>>>>>>
>>>>>>>
>>>>>>> Of course it is image, calc is dataset (equivalent for exel), 
>>>>>>> draw stuff is image (as the name implies already)
>>>>>>>
>>>>>>> Prosit, uschi (who feels like counting pees, when it comes to 
>>>>>>> those damned media types and would like to discuss what they are 
>>>>>>> really used for or could be useful for in dam)
>>>>>>>
>>>>>>>> gRTz
>>>>>>>>
>>>>>>>> ben
>>>>>>
>>>>>> +1 by reading. please get this one in. we are trying to wrap stuff 
>>>>>> up. can the guys with commit permissions have a look at what is 
>>>>>> still waiting?
>>>>>>
>>>>>> gRTz
>>>>>>
>>>>>> ben