[TYPO3-dev] Usability of the Columns view

[Tapio Markula]

Erik Svendsen wrote:

> And you activate TV on site basis, and every user has to use it. As I 
> understand, but haven't read all documentation.

>> class ux_t3lib_tsfeBeUserAuth extends t3lib_tsfeBeUserAuth {
>>
>> ...
>>
>> function ext_makeToolBar()    {
...
>> that needs more conditions

> If you somehow can get the value of page.10.userFunc = 
> tx_templavoila_pi1->main_page, don't know how it looks, but it has to be 
> used a lot of places to render the page

It can be set as global variable. But what I need is something, which is 
stored in $GLOBALS array.
The class, which I have XCLASSed doesn't handle other HTML-rendering
than making some specific issues, which don't relate in any
way TS templates. If the TS Config for the root page is stored
in the $GLOBALS array, it can be used for contolling if the value 
concerns the whole site structure (and not only the root page).

*This* could be reasonable to the core files too because it could solve 
content wizard problem. If there could be a reasonable solution, this is 
even worth of a bug report with a patch proposal.

>>> It's also another way I suppose. Who also I think are simple enough.
>>> Make settings in tm_contentaccess 

settings, which I have added works only in TS Config for users/user groups

> AJAX is cool, but I never give editors the ability to move around 
> content element (or very restricted ability). And I advice my customer 
> not to do it. My experience with fancy functionality aren't very good, 
> it tend to ruin the layout of pages and somehow the sorting of content 
> change in a way the main editor don't want.

certainly - it is for many users *too* easy to move around content 
elements because it give feeling "This is cool, this must be tested"

But in the other hadn it it is good if editors uses short content 
elements, which they can reorder easily afterward.
AJAX be_dragndrop is an enable option in tm_contentaccess.