[TYPO3-hci] devilish details - improvement suggestions

Irene Höppner ih at abezet.de
Thu Jun 1 19:36:18 CEST 2006


> - no page targets like PAGE_TARGET = xy - should not be necessary. There  
> are many places where default content elements have strange targets,  
> that bloats the code.
+1 (frames are outdated)
> - no default blurlink() outputted - not necessary for most projects
+1 but not very important
> - no default doctype, does not hurt if not present and can be set  
> manually very easy
-1
> - in general - no default output except the typo3 message in the header
-1 (i'm not sure, which other default output you don't like... there is  
really not much...)
>
> TEMPLATE
> move setup field above constants - i guess 95% of the people use this  
> field more often.

-1 because constants are - when used - required for setup. Means: you have  
to add first the constant and then use it in setup. If done like you  
suggest, setup would have to be the first field in the form, which pobably  
would not increase usability.
>
> EXTENSIONS
> remove the wrapped div of extensions by default. I had many cases where  
> this breaked my code and added unnecessary complexity. Well done  
> extensions and templates (and thats what we want, do we?) don´t need  
> fancy default styles. Most things can be easily done with a well made  
> "masterstylesheet".
----1 You can remove it easily in your own extensions. I want to be able  
to style extensions depending on that div, and I pretty often need that  
(complex layouts)
>
> RTE
> if RTE edit in HTML mode nothing of the output should be touched (except  
> filtering <script> maybe).
what do you mean? Do nothing before saving to the database or do nothing  
before outputting in the frontend? I disagree with the last, because i  
like that in textarea fields ppl can add things like <link  
132>slfjsdl</link> and the output is transformed to a correct link.
If you need your HTML-Output use the HTML-Content Element, not the RTE.
>
> For 5.0:
> A system that "feels" css 2.0 XHTML. Right now Typo3 still shows  
> everywhere that its roots are html 4.0 with its disadvantages.
+1

Greets: Irene

-- 
Irene Höppner
A.BE.ZET GmbH i.G.
http://www.abezet.de/



More information about the TYPO3-team-hci mailing list