[TYPO3-dev] Page and List Ajaxed

[Martin Kutschker]

Andreas Balzer schrieb:
> Martin Kutschker schrieb:
> 
>> Basically I agree, but ... We went along til now not even bothering 
>> about older versions of standard browser (eg IE 5.5).
> Yes that's true. But we might should think about them again too. As long 
> as it's shipped with (Windows 98), Windows ME, Windows 2000 and some 
> early versions of Windows XP it might be important for some companies or 
> customers. But supporting IE is an other thing.. (but at the end it 
> means accessibility..)

But IMHO the current BE is a lost cause. There's too many legacy code 
(PHP and HTML) around. Starting from scratch is a difficult thing but I 
see TYPO3 5.0 as chance for a real UI overhaul. The current efforts may 
"only" offer added usability for a part of the users.

>> ... I am suprised to hear that some users are successfully using the 
>> BE without a screen device.
> Yes, it's really possible. But there are some problems which makes the 
> way to reach the aim very difficult.

Now, that I know that there is partially success, I'm interested in 
removing obstacles.

>> IMHO a standard website should be usable for everyone. OTHO the BE is 
>> so complex that I'm willing to have either different UI or a couple of 
>> UI config vars that enable or disable certain features.
> Having a different UI is a problem. As you know T3 had two different 
> UI's (the classic and alternative). If you have 2, you have to manage 
> both if you want to add a new feature. My propsal is to split the skins 
> from the skin engines. If T3 can use a new skin engine, that is 
> completly divided from the actual skin and only offers certain things as 
> a pagetree and a button system, etc... it would be able to have a skin 
> for both or 2 different skins, but with the advantage that there is only 
> one main part to adjust. The skins could automatically be changed by the 
> skin engine.

My idea for something like that was to use Smarty as a template engine 
with an API that is fit for all kind of UIs.

> BTW: Back to main topic: In terms of usuability: it might be good to 
> offer a possibility to switch of the standard module navigation 
> completly and just use those tab menu. Maybe the nice ajax ext can be 
> used with skin_grey2 so that skin_grey2 uses the same ajax technique.. 

I'm lost. You're not talking about the propesed AJAX features here?

Masi