[TYPO3-dev] Best practice for ajax use in BE?

[Jens Hoffmann]

Strange discussion ...

1. You CAN'T combine Frameworks as long they manipulate the JS DOM CORE! like Prototype.
    This makes the JS Framework on the basic level uncompatible for other Frameworks.
    This is the main point why MooTools is better.

2. Why no JS ... Usability is important ... without JS most things are harder to do!
    So this is a nogo for me ... and everybody has in thoseday JS working ...
    Sorry but this is quite stupid to discuss this ... Good Fallback ... no Probs.
    Do you use a Browser or the Console to look at sites ... if yes ... why?

3. Prototype is not a good Framework, it's just popular ... just like Windows.

Greez Jens

ries van Twisk wrote:
> 
>>>
>>> The only button that doesn't work right now is the 'add to chart'
>>> button,
>>> and I do feel that can be solved without any JS at all.
>>
>> Hi,
>>
>> I didn't dig that deep. Already the dropdown select fails, when I turn JS
>> off. I miss the submit button. It should be there by default as usual. 
>> Then
>> you can hide it with JS in the moment JS is enabled.
>>
>> That isn't a question of ajax directly, but rather a question of an
>> divergent working style, that results from the usage of JS libraries. 
>> With
>> a server centric library you always start by coding the fallback 
>> solution,
>> the "normal" behaviour. You don't fall into the habit to forget it.
> 
> 
> Normally users would press the cars as shown on the site...
> The drop down is just a quick jump for people that know the site.
> 
> Ries
> 
>>
>>
>> Regards
>>
>> Elmar
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> TYPO3-dev mailing list
>> TYPO3-dev at lists.netfielders.de
>> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev
>