[Typo3-dev] Less features, more future

[Peter Niederlag]

Hi,

Michael Scharkow schrieb:
> Kraft Bernhard wrote:
> 
>> Michael Scharkow wrote:
>>
>>> 4. Fields in content elements: Space after/before, Frame, Align? All
>>> those can be replaced by *one* CSS-class field in which these
>>> properties can easily be defined for the wrapping div field.
>>
>>
>>
>> I agree to all of you other ideas ... but not to this one.
>> I don't know if it's good practice of Editors we trained but some of
>> the insisted
>> in that they want to be able to place a variable amount of space
>> before a content element
>> (when they tought to CEs would be to narrow).
> 
> 
> I think this is very much against the separation of content and layout.
> Why would you let the editors screw up your layout by occasionally
> putting *variable* amount fo whitespace between CEs? If you really think
> that it could be useful in some cases to have space before and after,
> you can define a class=spaced and have editors select that. But leaving
> too much freedom in styling to editors will hurt your site's consistency.

NO. because then you need to add css-classes for multi-purpose. Only way
would be, if the css-class dropdown would turn into a multiselect.

Now I do use "frame" often to assign frames, colors, margins or
smoething alike on a CE by CSS.

Also i some cases I do use the spacing stuff to adjust some things on a
very detailed basis.

Yes, it could be done by allowing to assign multiple css-classes but
still I'd favor not to drop before/after now.

Cheers,
Peter
-- 
Peter Niederlag
http://www.niekom.de * TYPO3 & EDV Dienstleistungen *
http://www.typo3partner.net * professional services network *