Christopher Torgalson wrote:
On Thu, Feb 25, 2010 at 5:11 PM, JoH asenau <[email protected]>
wrote:
IMO there's no real need for a tableless backend at all. If you
take closer look for example at the extJS interface components,
which will make a major part of the BE in T3 4.4+, you will notice
that they do use lots of nested tables as well, because they make
the look and feel cross browser compatible much more easily.
Is that the real reason? Maybe it's just because a lot of components
represent a tabular form?
I'm very disappointed to hear this. Regardless of whether or not
there are any actual problems caused by the use of layout tables, I'm
absolutely certain that this will be perceived negatively, and that
it will hinder wider adoption of TYPO3.
Tables are not evil and certainly not something that shouldn't be used
at all. Many components of an interface are in fact tabular data: list
module, file list, etc.
I've seen people using div's to render a file list; completely illogical
and unnecessarily complex to make it render correctly in every browser.
What should be avoided is using (nested) tables only for layout
purposes: to render a border around an object, etc. But even the
language view of a page module (each column representing a language) is
a logical candidate for a table.
It's difficult enough to convince people that the CMS universe
includes products other than Drupal and Wordpress, and this isn't
going to help.
If the selection criterium is "does it use tables or div's in the
backend" then I doubt that this person or organisation is ready for
using TYPO3.
Most clients do not spend money on styling the BE; they do want to spend
money to have the features they want and to configure the system in a
such a way that it fits their work flow. The BE should be functional and
must function correctly in the browser(s) which the client uses.
--
Regards, Jigal.
_______________________________________________
TYPO3-english mailing list
[email protected]
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
