[TYPO3-v4] Breaking changes with Card layout

[Lorenz Ulrich]

Hi Kay

Thanks for taking care, I really appreciate that!

Problematic user stories:

- The tree has no function, you cannot switch between 
directories/categories/media types

- Also the selectors in the List module are not functioning anymore (+-= 
beside each folder/category/media type)

- The context menu of folders (not files) in the Media / File module 
(the module content, not the tree) is displayed, but the actions aren't 
executed.

- When dam_ttcontent is installed and you reference an asset, e.g. an 
image in a text w/images CE (in the field "Images:", not "Images and 
Captions"), you have a clickmenu for every reference file right beside 
the "Images:" field. In this clickmenu the "Edit" button won't work for 
the same reason as other JS actions don't work:
"c.getComputedStyle(g.firstChild.firstChild, null) is null"

(Funnyly enough the ancient category editor dam_catedit is working.)

You may contact me by Skype if you have any questions or need someone to 
test core patches. I added you recently but you didn't accept the 
request yet.

By the way, from the user perspective I really like the behaviour with 
card layout enabled. From the admin perspective I will like it as soon 
as every module has a refresh button (yes, I know, I can click the 
module again to force reload :-)).

Best regards,

Lorenz

Am 29.09.2011 09:57, schrieb Kay Strobach:
 > Hi Lorenz,
 >
 > Could you please add some problematic user stories - please?
 >
 > I found, that the tree isn't working anymore (Content is loaded in
 > Fallback card   ->  This can be resolved with:
 >
 > http://forge.typo3.org/issues/30409
 >
 > I will do that today - hopefully it finds it's way into the core until RC
 >
 > Regards
 > Kay
 >
 >
 > Am 29.09.2011 09:40, schrieb Kay Strobach:
 >> Hi Lorenz,
 >>
 >> i will take a look, hopefully this afternoon.
 >>
 >> Regards
 >> Kay
 >>
 >> Am 28.09.2011 21:52, schrieb Lorenz Ulrich:
 >>> Hi Kay
 >>>
 >>> I think the problem is more general. E.g. in the DAM List module, 
when I
 >>> click a folder in the tree, I get the JavaScript error:
 >>>
 >>> Fehler: c.getComputedStyle(g.firstChild.firstChild, null) is null
 >>> Quelldatei:
 >>> 
http://www.typo3trunk.dev/typo3temp/compressor/ext-all-45c9f88d61507f45b4675d5e25f4a7e6.js
 >>>
 >>> Zeile: 7
 >>>
 >>> Could you possibly checkout DAM master from Git, install it and go to
 >>> the list? I think from your experience you will quickly have an
 >>> impression what it is about and will be able to point me to the right
 >>> direction.
 >>>
 >>> Thanks and best regards,
 >>>
 >>> Lorenz
 >>>
 >>> Am 28.09.2011 20:14, schrieb Kay Strobach:
 >>>> Hi,
 >>>>
 >>>> perhaps this does the trick for you:
 >>>>
 >>>>> API hints:
 >>>>>
 >>>>> JavaScript
 >>>>> - in old times we used:
 >>>>> TYPO3.Backend.ContentContainer.setUrl(uri);
 >>>>>
 >>>>> Now please use
 >>>>> TYPO3.ModuleMenu.App.openInContentFrame(uri, params);
 >>>>> The "new" function was available before and knows the current
 >>>>> module. This function uses the correct iframe - if it is allowed to
 >>>>> load the module.
 >>>>
 >>>> https://review.typo3.org/#change,3370
 >>>> https://review.typo3.org/#change,4299
 >>>> https://review.typo3.org/#change,3947
 >>>>
 >>>> Perhaps we should change the TYPO3.Backend.ContentContainer as 
well, but
 >>>> this was rather hard, as this is a real iframe object
 >>>>
 >>>> Regards
 >>>> Kay
 >>>>
 >>>>
 >>>>
 >>>> Am 27.09.2011 22:39, schrieb Lorenz Ulrich:
 >>>>> Hi everyone
 >>>>>
 >>>>> Now that we approach the release of TYPO3 4.6, I'm doing some 
testing of
 >>>>> DAM 1.2 with the new version.
 >>>>>
 >>>>> Unfortunately a lot of stuff seems to be broken, and if I got it 
right,
 >>>>> one cause could be the introduction of the Card Layout.
 >>>>>
 >>>>> Does anyone have information if the Card layout will really break 
older
 >>>>> JavaScript stuff? DAM uses custom calls for almost everything in the
 >>>>> backend: Changing folders, mass editing files etc.
 >>>>>
 >>>>> This will cause us some problems because we still should maintain
 >>>>> version 4.5 as it is a long term support release. And with DAM 
2.0 (for
 >>>>> TYPO3 4.7) coming along maintaining three branches (one for 4.5, 
one for
 >>>>> 4.6 and the new one for 4.7) will be quite an time-consuming.
 >>>>>
 >>>>> Thanks for your information and best regards,
 >>>>>
 >>>>> Lorenz
 >>>>
 >>>>
 >>>
 >>
 >>
 >
 >