[TYPO3-core] RFC #16318: Enable FlashMessages to fade out after delay

Ingo Renner ingo at typo3.org
Mon Nov 15 03:22:10 CET 2010


Steffen Gebert wrote:

Hi Steffen,

>> Right, the jumping content doesn't feel ok, but using fadeOut() instead
>> of the ghost() effect solves that issue.
> Without the parameter {remove: true}, the space appears white - with the
> parameter, the content jumps. Other possibilities?

Oh sorry, I was wrong. The correct effect is slideOut, I mixed that up:

message.pause(5).slideOut("t", {remove:true});


> However I dislike different behavior for the same thing, saying
> "everything went fine".

See below, it's just different right now, because the queue is not used 
consistently.

>> Admittedly, the queue is not used consistently yet, but that's on my
>> list. The queue should be used for cases when you show messages to
>> confirm the success of an action or reporting a failure of that action.
>> In these cases they need to survive a request, thus the queue and
>> storage in session.
> Yes, but for FlashMessage, which don't have to survive a request, we
> shouldn't always (have to) use the queue, don't we?

Right, after that I want to go and see where we need to make use of the 
queue for consistency. Other areas such as the install tool just stay as 
they are. - The messages are a little abused in such situation, but I 
think that's fine now as it provides a quick overview of status information.

The queue itself also needs some polish to make it more OOP like, right 
now it's just a collection of static methods, kind of functional 
programming.

>> I don't know why they were introduced, wasn't my idea. Are they actually
>> used in the core at all or is this an issue of "because we can"? Maybe
>> we should remove them again?
> No, searched for it, found nothing. I think it's "because we can" :)

:(


best
Ingo

-- 
Ingo Renner
TYPO3 Core Developer, Release Manager TYPO3 4.2



More information about the TYPO3-team-core mailing list