[TYPO3-core] Fwd: Improved page tree (and lots of other fixes)

Kasper Skårhøj kasper2007 at typo3.com
Fri Jul 13 09:37:44 CEST 2007



Begin forwarded message:

> From: Jens Hoffmann <jens.hoffmann at baiz.org>
> Date: July 13, 2007 9:31:08 AM GMT+02:00
> To: Kasper Skårhøj <kasper2007 at typo3.com>
> Subject: Re: [TYPO3-core] Improved page tree (and lots of other fixes)
>
> Hi Kasper,
>
> sorry that I have to "spam" you.
> I don't know how to get access to this list ...
>
> 1. I would turn cool featchers on :)
> 2. Filter InputBox by default ON
> 3. Tree Seperation by default OFF
>      (New cool Concept ... But it will be quite strage if you  
> UpDate Typo3)
>
> Hope it helps, have a nice and productive day! :)
>
> >> ... Study Construction Engineering ...
> Cool ... you are crazy :) ... Did this as "Fachabitur" (vocational  
> baccalaureat diploma << leo.org .. hehe )
> for one Year to get the licence to be disposed to study at the  
> university. I wish you the best for this!!!
>
> Greez Jens
>
> Am 13.07.2007 um 08:57 schrieb Kasper Skårhøj:
>
>> Hi Benjamin,
>>
>> Rewriting the functions and adding options like  
>> "options.pageTree.separatePageTypes = notinmenu,sysfolder" is fine  
>> with me, but I would like to commit my work first to Trunk and  
>> then all of you can modify it as you please to improve it. Thats  
>> the best way to collaborate because I'm out of office for a long  
>> time now.
>>
>> The question whether the feature should be on by default;  
>> Traditionally we have been too chicken-shit scared to introduce  
>> changes like this by default that we have made it all optional.  
>> This results in a situation where the default TYPO3 installations  
>> doesn't evolve because all the cool features are not turned on. I  
>> would like to propose that we change that strategy so the default  
>> TYPO3 evolves with features like this - which can always be  
>> disabled of course. Naturally, every such feature must be agreed  
>> to as a default feature by a majority of the core team I believe  
>> because some could be too exotic.
>>
>> This is why I want it by default - because I think it is time that  
>> we take a stand.
>>
>> I have included Jens Hoffman in copy of this mail because he is  
>> our usability guy and I would like to know what he thinks; if it  
>> should be default or not.
>>
>> (finally, if you all think it should be turned of by default I'm  
>> absolutely fine with that...)
>>
>> - kasper
>>
>>
>> On Jul 13, 2007, at 0:47 , Benjamin Mack wrote:
>>
>>> Hi Kasper,
>>>
>>> I have one small addition -- could we change the option
>>>
>>> from
>>> options.pageTree.dontSeparateNotinMenuPages = 1
>>> to
>>> options.pageTree.separateNotinMenuPages = 1
>>> or even better:
>>> options.pageTree.separatePageTypes = notinmenu,sysfolder
>>>
>>> so it's not a new default value, since a lot of people don't know  
>>> why it changes after one.
>>>
>>> Also, could we rewrite your Tree functions so they go into the  
>>> Tree-object in JavaScript?
>>>
>>> What do you think?
>>>
>>> -- 
>>> greetings,
>>> benni.
>>> -SDG-
>>>
>>> www.xnos.de // www.xnos.org
>>
>> - kasper
>>
>> ----------------------------
>> NOTICE: NEW EMAIL for 2007: kasper2007 at typo3.com
>>
>>
>>
>

- kasper

----------------------------
NOTICE: NEW EMAIL for 2007: kasper2007 at typo3.com



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20070713/8bbf88d6/attachment.htm 


More information about the TYPO3-team-core mailing list