W3C home > Mailing lists > Public > www-style@w3.org > July 2005

Re: New layout language.

From: <Kris@meridian-ds.com>
Date: Tue, 5 Jul 2005 13:11:35 -0500
To: www-style@w3.org
Message-ID: <OFE25DC88D.824EA5D8-ON86257035.0063F028-86257035.0063F04A@meridian-ds.com>

Orion Wrote

>I haven't specified a syntax. This language is designed to replace the
>functionality of CSS layout and would use a different syntax. It's
>region based and not class/id based.
>You didn't quite get what I was saying unfortunately, but you at least
>did get the intention. Perhaps if I were to explain how to get the
>linear functions.
>Create a set of regions in space. Each region is given an (x, y)
>coordinate and a width and height. Give the viewport a width and
>height that incorperates the proper spacing.
>Now exactly double the size of the viewport (e.g. if 1000px, now
>2000px). Since the regions use constant coordinates the viewport
>resizes but nothing inside the viewport changes. Now that's not the
>desired effect. So I resize and move the regions around inside the
>viewport to get new positions and sizes that take advantage of the
>viewport's increased size.
>Now take each shift in space (x, y) and each resize in space (+x, +y)
>and divide them by the increase the viewport had (1000px). This
>represents the growth/shift (represented as a percentage).
>There are no margins, borders or padding. There is no display. This is
>completely separate from CSS as it stands.
>A linear function is described by a delta and a constant. The delta
>here is a percentage between 0 and 100% inclusive. The constant is any
>non-negative number.
>The langauge was designed to be fairly easy to write by hand and very
>easy to manipulate with a WYSIWYG editor.
>It isn't any more verbose than CSS is now, actually less so in complex
>layouts because it manages to combine left, top, right, bottom, width,
>height, display, min-width, min-height into 4 properties left, top,
>width, height.

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?

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?

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.

Received on Tuesday, 5 July 2005 18:12:02 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:19 UTC