TYPO3 Core

I hate the idea of the loading indicator ;-)

It's only shown, when a frame is changed through the API, not when a simple link is clicked. Think it should be no problem, to make it consistent for sb. with ExtJS knowledge (you? g). Can you provide a patch?

can be solved using the managed iframes in extjs:

http://www.sencha.com/learn/Extension:ManagedIframe

I'm really busy at this point, sry - but i can't spend enough time to dig into the complete backend extjs and find the point for the fix. I have a lot projects which are in the last phase before release. (Very stressfull part - you know).

Saying I hate the loading indicator only is a personal opinion. Although I think the same, it alone is only a matter of taste, but no reason to remove it.

But there in fact are good reasons which should make us remove or at least drastically modify this indicator again.
- Some people say this indicator looks nice. But "looking nice" is not the most important thing a CMS should do. We are not composing a picture here, but something you must be able to work with in a reasonable fashion.
- You might argue that this indicator tells you that there is something happening in the background and that this is the reason why you have to wait. But that is not convincing. You can already see the loading progress in the status bar. We don't need another loading indicator, less than ever one which fills the whole screen and makes the system unusable when it is displayed. And if the loading in the background does not continue (e.g. because your network connection shortly breaks in between), you still see the indicator although nothing is happening at all. In that case the loading indicator only pretends that something is happening while in fact you are waiting for nothing while you maybe could already use the BE (because maybe only a picture is missing). You are waiting for nothing.
- The loading indicator makes the backend feel slow, much slower than the BE of current versions feels. It is quite boring to see always this turning icon while nothing is happening. There already where people in the newsgroups who legitimately complained about that. The indicator always again and again reminds you that you have to wait and that you cannot do anything but wait. Being told that you must wait is annoying and must be avoided.
- But the most important reason to remove the loading indicator is that it makes TYPO3 objectively slower. It does not only feel slower, but working with TYPO3 really becomes slower. Before you could at least have a look at the loaded module and you could much more easily get a first orientation on where to click next and begin moving the mouse there. With the indicator that has become much harder. You do not see the module content until the disappearing of the indicator allows you to.

That is why we have to remove (or at least drastically improve) this indicator again.

There also has already been a discussion in Core List (#23614) where people agreed to modify the loading indicator.
The idea to solve this problem was to put a small loading indicator in a top corner of the reloading frame. This prevents all the negative effects listed above while it still gives you the information where something is loaded. I think that really is a good idea.
This has not yet been fixed because Ext JS does not yet offer the needed options itself. Steffen K wanted to ask the developers of Ext JS and maybe write the functions himself, if needed.

Kay, could you please also have an eye on #23614 and think of it before the final version is released? That would be great!

ofcourse.

@Loading indicator:
I'm not sure if i like / dislike the loading indicator (Therefor we have UI specialists.). But in my opinion it must be consistent if there is one or not.

#0015811 is about removing the indicator that would be ok for me too.

Yes, the discussion went to another direction (showing a small indicator in a corner of the BE). I can live with that, too.

But as you say: It should be consistent: Everywhere or nowhere.
(Usabilitywise: Please first make it small and THEN introduce it everywhere, not the other way around. ;-) )

don't know, close it for now, as it is ignored anyway?