[TYPO3-dam-devel] RFC: defaults in dam_ttcontent/ext_conf_template.txt

[georg kuehnberger]

Andreas,

Andreas Balzer wrote:
> It's a good idea to put it into the manual but I think it would be 
> better to have that somewhere during installation. As I worked quite a 
> long time in the HCI Team before it was closed down (now it's a 
> one-man-show imho) I recognized that most people don't read manuals ;)
> 
> Therefore I'd still prefer some button during installation. But manual 
> will be fine aswell.

- On which pages (depending on the installation) should "the button" add 
it's TSconfig ?

- Adding the TSconfig on the rootpage will not cater for the cases I 
descripbed below, where you eg. want to have the DAM field on all pages 
except the sysfolders a,b,c, which contain extension with no DAM-compliance;

So in the end we might add some description in the Extension 
Configuration Dialog (referring to the manual ... ;-)

I guess we'd better sort this out while writing the new DAM-Manuals;
regards georg

> Greetings,
> Andreas
> 
> On Dec 29, 2007 11:16 PM, georg kuehnberger < gk at plan2.net 
> <mailto:gk at plan2.net>> wrote:
> 
>     Ahoi Andreas,
> 
>     Andreas Balzer wrote:
>      > Hm.. Ok. What about offering a configuration during the
>     installation of
>      > dam that configures this PageTS?
> 
>     that might be an option;
>     however I feel rather to put this optional configuration as example
>     into
>     the new manual.
> 
>     regards georg
> 
> 
>      > Greetings,
>      > Andreas
>      > On Dec 29, 2007 2:07 AM, georg kuehnberger < gk at plan2.net
>     <mailto:gk at plan2.net>
>      > <mailto:gk at plan2.net <mailto:gk at plan2.net>>> wrote:
>      >
>      >     Peter (Paul & Marry ;-)
>      >
>      >     +/-1, reasoning:
>      >
>      >     a) Consider a well grown Installation with any ammount of images
>      >     connected to tt_content, tt_news, tx_younameit, where you'd
>     like to
>      >     install DAM for usage in NEW Content-Elements. In case the
>     original
>      >     field is not shown anymore, media-files of old records can't
>     be edited
>      >     anymore & and AFAIR won't be shown in the FE ;-(
>      >
>      >     b) Even considering a plain new installation, where you can may
>      >     configure DAM for all different kinds of Content Elements
>     (tt_content,
>      >     news.), I have to disagree, simply because there's still a hughe
>      >     load of
>      >     extensions (FAQ, Glossary, fe_users ...) which dont yet feature
>      >     DAM-compliance, thus the second (classic) field is required;
>      >
>      >
>      >     c)
>      >      > Expected behaviour:
>      >      > I would expect that the original fields are replaced.
>      >
>      >     IMGO, No from an admin point of view, especially as long as
>     not ALL
>      >     major extensions support DAM;
>      >
>      >     However "not showing" the old media-field, but only showning the
>      >     DAM-fields, for certain type of records, or within a certain
>     branch,
>      >     can
>      >      simply be done via PageTS;
>      >
>      >     So I'd leave it the way it is;
>      >     regards georg
>      >
>      >
>      >     Peter Kühn wrote:
>      >      > This is a svn patch request.
>      >      >
>      >      > Type: confusing behaviour
>      >      >
>      >      > Steps to reproduce:
>      >      > - Install dam_ttcontent
>      >      >
>      >      > Observed behaviour:
>      >      > Fields for dam references are added to the form for CType
>     Image
>      >     and Text
>      >      > w/ image
>      >      >
>      >      > Expected behaviour:
>      >      > I would expect that the original fields are replaced. Its
>     usefull to
>      >      > have the option to display both fields fx. if you have to
>     rework
>      >      > existing content but i see this as the option, not the
>     expected
>      >     default
>      >      > behaviour.
>      >      >
>      >      > pls ack
>      >      > grtz
>      >      > pekue
>      >      >
>      >      >
>      >      >
>      >    
>     ------------------------------------------------------------------------
>      >      >
>      >      > _______________________________________________
>      >      > TYPO3-team-dam mailing list
>      >      > TYPO3-team-dam at lists.netfielders.de
>     <mailto:TYPO3-team-dam at lists.netfielders.de>
>      >     <mailto: TYPO3-team-dam at lists.netfielders.de
>     <mailto:TYPO3-team-dam at lists.netfielders.de>>
>      >      >
>     http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-dam
>     <http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-dam>
>      >     _______________________________________________
>      >     TYPO3-team-dam mailing list
>      >     TYPO3-team-dam at lists.netfielders.de
>     <mailto:TYPO3-team-dam at lists.netfielders.de>
>      >     <mailto: TYPO3-team-dam at lists.netfielders.de
>     <mailto:TYPO3-team-dam at lists.netfielders.de>>
>      >    
>     http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-dam
>      >
>      >
>      >
>      >
>     ------------------------------------------------------------------------
>      >
>      > _______________________________________________
>      > TYPO3-team-dam mailing list
>      > TYPO3-team-dam at lists.netfielders.de
>     <mailto:TYPO3-team-dam at lists.netfielders.de>
>      > http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-dam
>     _______________________________________________
>     TYPO3-team-dam mailing list
>     TYPO3-team-dam at lists.netfielders.de
>     <mailto:TYPO3-team-dam at lists.netfielders.de>
>     http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-dam
> 
>