[TYPO3-core] RFC #16032: Overwork tree frame design

Steffen Gebert steffen at steffen-gebert.de
Wed Nov 10 09:56:05 CET 2010


> Not in scope of this RFC, nevertheless, not to be forgotten:
>
> * navFrameWidth and navFrameResizable are not respected any more. The
> first one needs to be fixed, the second one can be deprecated, it's not
> needed any more

Thanks for the review, Helmut!

Hopefully we get a StateProvider (like the default CookieProvider [1]), 
which saves the state in the BE_USER uc field. SteffenK's ExtDirect 
provider for the User Settings is the foundation for this. I think the 
remainder is pretty easy then.

This will save the state of the panels (width, collapsed etc) and IMHO 
we then could remove navFrameWidth, too as it makes not too much sense.
Reporting is a good start - if we don't get the StateProvider, we should 
fix it, yes.

Kind regards
Steffen

-- 
[1] http://dev.sencha.com/deploy/dev/docs/?class=Ext.state.CookieProvider

Steffen Gebert
TYPO3 Core Team Member

Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/


More information about the TYPO3-team-core mailing list