Re: New layout language.

> Ok, so essentially what you're thinking is this: (if I can sum it up)
> 
> Classes are more an idea of css, in that they work better for text styling
> and such.  In this case (for a css parallel) you're thinking IDs.  Each
> individual area sits on its own, you don't really expect to have multiple
> of the same screen space.  That right?

Yes.

> As far as the actual implementation I think you're saying this:
> 
> All layout regions are specified by a number of units from the left and top
> of the screen.  In addition to that you specify a width and height for the
> region, otherwise it wouldn't appear.  You have no need for margins because
> you're already controlling the regions directly, so any spacing between
> regions will be manually controlled by the initial placement.  RIGHT?

Close enough. Spacing can be affected as well by manipulating left and
top percentages. But your assesment about margins is correct.
 
> Assuming I got all of that correct (actually I need this answered even if
> my impression is wrong) what is it that you're trying to do that CSS can't
> in the example I tried to duplicate in CSS?  Cause, I must have REALLY
> missed the boat.  PLEASE PLEASE PLEASE answer that for me.  More pictures
> if neccessary.  You can e-mail me the pictures directly if the group would
> rather not deal with them.
> 
> My understanding of the issue was a static left nav area, with a liquid
> right nav that resizes based on the amount of content inside it and the
> width of the screen viewing it.  Is that wrong?  Please Advise.

There is no mechanism in CSS for telling something to take up the
remaining space outside the proposals for calc() and %%.

So while one region has static width and the other dynamic width,
there is no CSS that will allow the second region to take up the
remaining space in the viewport.

Orion Adrian

p.s. More pictures coming.

-- 

Orion Adrian

Received on Tuesday, 5 July 2005 19:57:50 UTC