Box within a box, CSS Box Model, Inline Construction - take your pick from
its many names.
Not CSS Box Model. Never CSS Box Model.
C’mon guys, Thomas already guaranteed me the majority of you understand the
difference between “Box Model” (the unfortunately named and badly-branded
Freeway Pro technique of nesting html divs or “boxes” into each other via
the text-insertion tool to construct a layout) and “CSS Box Model” (the
archetypal web-design principle which describes the process of how a
browser determines the dimensions of absolutely everything as a function of
its content and that content’s padding, border and/or margin settings).
Failing the branding test of clarity, I move the name describing the first
process be changed… how about a contest?
The simple point is, that the majority of Freeway Users talk about the INPUT - so referring to the Freeway WORKSPACE (WYSIWYG). In this nutshell it could be named however you want as long you put the preface “Freeway” in front and never use it in conjunction with CSS.
The CSS-Box-Model is discussing the OUTPUT, so the generated code and it’s appearance in the web (CASCADING STYLES in a SHEET). And there we are:
Most average Freeway Users never reached that point so far. And those that did can handle the difference between and have therefore no problem with it.
I guarantee further that my subscribers WILL know this difference :-)*
However (and that’s what I wanted to answer you Ernie offline) I decided to open (and close it cause I have no time for further discussions in this) the naming-battle into:
Freeway Box-in-Box ModelPro Version X (short Box-in-Box)
Now it’s up to us to strictly advertise this idea.
Back to Julie’s page:
Yes - david is on the correct track:
To ensure the appearance of a page cross-browser you should either use the Box-in-Box method or if you use the Drag’n Drop method, the RelativePage Layout could help you here. It should be noted that RPL only works if your items on the page DON’T overlap.
Cheers
Thomas
(*) … and to ensure this, I start now producing a couple of new episodes cause we have bank-holiday today in germany - so hurry-up Thomas
Okay, prepending FREEWAY so the term becomes FREEWAY BOX MODEL seems an
agreeable branding compromise.
Looking forward to more vids Thomas
–
Ernie Simpson
On Thu, May 9, 2013 at 9:20 AM, Thomas Kimmich email@hidden wrote:
Hi Guys,
uhhh - I guaranteed. Yeah I did.
The simple point is, that the majority of Freeway Users talk about the
INPUT - so referring to the Freeway WORKSPACE (WYSIWYG). In this nutshell
it could be named however you want as long you put the preface “Freeway” in
front and never use it in conjunction with CSS.
The CSS-Box-Model is discussing the OUTPUT, so the generated code and it’s
appearance in the web (CASCADING STYLES in a SHEET). And there we are:
Most average Freeway Users never reached that point so far. And those that
did can handle the difference between and have therefore no problem with it.
I guarantee further that my subscribers WILL know this difference :-)*
However (and that’s what I wanted to answer you Ernie offline) I decided
to open (and close it cause I have no time for further discussions in this)
the naming-battle into:
Freeway Box-in-Box ModelPro Version X (short Box-in-Box)
Now it’s up to us to strictly advertise this idea.
Back to Julie’s page:
Yes - david is on the correct track:
To ensure the appearance of a page cross-browser you should either use the
Box-in-Box method or if you use the Drag’n Drop method, the RelativePage
Layout could help you here. It should be noted that RPL only works if your
items on the page DON’T overlap.
Cheers
Thomas
(*) … and to ensure this, I start now producing a couple of new episodes
cause we have bank-holiday today in germany - so hurry-up Thomas