[TYPO3-dev] Usability of the Columns view

[Tapio Markula]

> page = PAGE
> page.typeNum = 0
> page.10 = USER
> page.10.userFunc = tx_templavoila_pi1->main_page
> Should be enough for detection. If this isn't put there, TV do not work.

that is in some TS-template - but I need it here and I can't use here 
any TS template

class ux_t3lib_tsfeBeUserAuth extends t3lib_tsfeBeUserAuth {

...

function ext_makeToolBar()	{
...

$newContentWizScriptPath = 
TYPO3_mainDir.'sysext/cms/layout/db_new_content_el.php';
			$tmpTSc = 
t3lib_BEfunc::getModTSconfig($this->pageinfo['uid'],'mod.web_list');
			$tmpTSc = $tmpTSc 
['properties']['newContentWiz.']['overrideWithExtension'];
			$newContentWizScriptPath = t3lib_extMgm::isLoaded($tmpTSc) ? 
(t3lib_extMgm::extRelPath($tmpTSc).'mod1/db_new_content_el.php') : 
(TYPO3_mainDir.'sysext/cms/layout/db_new_content_el.php');
			
that needs more conditions

'$tmpTSc' relates with

mod.web_list.newContentWiz.overrideWithExtension=1

BUT that works just for users/user groups, which means that for every 
change from TemplaVoila to standard page module or reverse needs 
changing of this. Not very handy.

I tested mod.web_list.newContentWiz.overrideWithExtension=1
for TS config for page - no effect.


> It's also another way I suppose. Who also I think are simple enough. 
> Make settings in tm_contentaccess who has classic web>page as default 
> (0), and the need for something like

> plugin.tx_tmcontenaccess_p1.enable = 1

That is nonsense because that plugin isn't FE plugin.
And what I would disable in templavoila is not FE-functionalities.
If that works only FE-features, it is useless (note that frontend 
editing belogs to BE-functionalities).

> customer. If the frontend editing isn't suitable, sell it without

I would not do that way - I want to give for them as good frontend 
editing as I can build - with some AJAX-functionality it would be really 
  cool, full 10.
I have tested visual demo - because it didn't save changes it was as 
such useless. It is just a great pleasure to move content element from 
one place to another with AJAX - fast, fun, enjoyable - and you can get 
that BE-functionality today using the standard page module!

> splendid BE configuration instead. I never use the FE-editing. Neither 
> does any of my customer.

If you do that way TemplaVoila works ok.