[Typo3-dev] Make configuration simple

[Kasper Skårhøj]

Hi Guys,

My repeating frustration when thinking about redesigning any part of TYPO3 is 
that I honestly fear I will not be able to hit the mark, because what IS the 
mark? 

What is the perfect solution that is 
- easy, 
- standards based, 
- works out of the box, 
- Fool-proof (validatable)
- solves all usability problems, 
- allows deep configuration without tons of complexity 
- etc. 

I would love to produce this for the TYPO3 community, but if we cannot make a 
clear definition of how this model looks with a 99% guarantee that it will 
work and solve the problems for all of us, then I will not start it. 
Especially; if we just change things so one group is now happy while another 
will be frustrated, then we did nothing but re-distribute the criticism. I'm 
not wasting time on that.

- kasper




On Monday 17 October 2005 11:11, typo3user at gmx.net wrote:
> >What does a DTD?
> >
> >In short it gives an answer to the question: What language elements are
> >allowed in the current context?
> >
> >Editortools than can offer the appropriate elements like attributes,
> >text and childenodes. Checkers can validate if everything is in the
> >allowed places. (Still before validation is done syntax checkers test if
> >the document is "well formed".)
>
> and IMHO a BIIIIG plus --> XML+DTD does not only unravel unused or made-up
> fields but it offers the editing tools (= backend GUI) the possibility to
> _LIST the available fields!!_ This means - no digging in TSref anymore as
> the user can clearly see what fields in the current context are allowed!
> And even better - chances for a click'n'run backend just like the current
> Template Constants editor but on a defined language (XML)
>
> just my 0,02 ¬
>
>
>
> _______________________________________________
> Typo3-dev mailing list
> Typo3-dev at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

-- 
- kasper

-----------------
Think future, not feature