Re: Parent pseudo-containers - a method for seperation of content from design

It seems one of the fundamental problems is that percentage values
which are more often used to represent a portion of a whole with the
sum of percentages being 100%. This means that there must be a method
of specifying width and height in percentages where if they sum up to
100% they must actually behave as if they take up 100% of the space.
This means that margin must be incorperated into the widths and
heights.

Calculations aren't necessary given this system. What is needed is the
ability to reference the properties of other objects in the system.
This would be a highly valuable function and allow authors to write
CSS in a way that is highly maintainable. There are currently no
language features in CSS that improve the maintainability of an
author's code.

Orion Adrian

> On Apr 8, 2005 9:56 PM, Emrah BASKAYA <emrahbaskaya@hesido.com> wrote:
> 
> On Fri, 08 Apr 2005 11:26:20 +0400, Maniac <Maniac@SoftwareManiacs.Org>
> wrote:
> 
> 
> > I was doing it myself and I'm glad to see I'm not alone :-).
> > However there are things that I've always found hard to resolve between
> > these two stylesheets. For example take borders. They are needed mainly
> > for decoration purposes but they also affect layout. In some cases the
> > problem can be quite severe: if you have two 50%-wide floats side by
> > side adding a border to any of them places them one below the other.
> > Do you have any more or less defined methods of dealing with this?
> >
> 
> This is a good example why the CSS2 box model was a bad choice IMHO.
> Hopefully in CSS3 we'll be able to select the box model. Current method
> could be much more bearable for flexible layouts with simple arithmetic
> expressions like %50 - 6px (for a 3px border, in this example). There had
> been a discussion on expression recently I guess.. Dunno. I don't need
> complex expressions. Just adding and subtracting two same/different units
> would have been killer.
> 
> One method to deal with that is to have a box in box. BAD :) Other is
> giving them smaller % on a trial basis. Another one, which is encouraged
> by this current model, is to use px. and have a non-flexible design. BAD,
> again.
> 
> --
> Emrah BASKAYA
> www.hesido.com
> 
>

Received on Saturday, 9 April 2005 13:53:40 UTC