[TYPO3-dev] Backend ajax: mID approach

Tapio Markula tapio.markula at atwebteam.com
Fri Feb 9 01:27:05 CET 2007


Maximo Cuadros kirjoitti:
> Hi,
> 
> As i told to Ingmar, the actual alt_doc_ajax.php (4.1-dev), have a
> limited support to add more ajax calls, this file is created just for
> Inline-Relational-Record-Editing (IRRE), but i think it that can be a
> good make the rest of the ajax calls need it by be.

alt_doc.php has also some other issues, which could be developed and I
hope that you could take account these too.

1) for record type 'pages' there could be tabs, at least these
* generic features
* advanced features (no distinction between normal/advanced pages but tabs )
* shortcut and external urls


Using Typo3 it is extremely annoying that when you have edited
a content record you don't have link to related page properties
and link to *back* to the same content.

I evaluated for page modules tab system, which links between
* page module
* alt_doc.php - handles editing tt_content,pages and page language 
overlay records
* preview - modified Web > View

When you open a page module it has tabs
* contents (page module)
* properties (tab to alt_doc.php editing table 'pages')
* propeties (lang) (lang is the current language - link to alt_doc.php 
editing page overlay record if the current language is other than '0')
* link to first content on the page/ link to last opened content element 
(if content exists)
* preview

Now when you click the link 'first content' you go to alt_doc.php and
the tab changes to 'last opened content', you have tab to related page 
propties. When you have looked page propeties, you have return tab to 
the content, which you have last time edited in tab 'to last content'.
Now you can *easily* switch between selecting content elements to edit, 
editing content content elements and page properties.

It is *extremely* annoying first close content editing, then open page
properties, close page properties, open again last editing content 
element. I have alway hated that very deeply. That is example of very
bad usability. That issue would be nice to solve together with AJAX
issues.




More information about the TYPO3-dev mailing list