I dont know why people like to use <div> I strictly forbid it in all my
code due to the fact that IE and Ns4 handle <div> entierly differently. IE
handles <div> as a layer were NS4 handles it more like <p>. This can be
seen when you goto a page created by an amature using some off the wall 3rd
party html creator, and when you go in IE everything is all overlapping and
you cant read most of the page. Maybe these problems have have been
resolved since last I used NS4 but still I avoid the use of <div>
> Exactly what I'd like to see in Zk. "When" is a different story.
> - Jon
> On Mon, 2002-03-18 at 13:17, Marc Groot Koerkamp wrote:
>> A lot of discussion about the div proposal. But how will the
>> architecture look like in SM 2.0?
>> I didn't overlooked the zookeeper stuff but I hope it will support my
>> next idea.
>> All the elements on a page should be descriped in a php class. In this
>> class things like style properties (another class) should be stored.
>> You can describe all the HTML elements by classes.
>> The class should contain the html spec properties, an embedded
>> style-class and an event-class.
>> Extra properties of this class should be the relationship with the
>> other elements on the page. In the case of tables the relationship
>> between tr td and tables is stored. (master class and id) Most of it
>> is static information.
>> With all that information it should be possible to generate a page
>> with supports any browser. You just need to know how the
>> styleproperties behave on the different browsers and it should be
>> possible to adapt them to your browser. If your browser supports CSS
>> then a lot of the style properties are useless so they can be skipped
>> in the page creation.
>> If our style class contains all the elements of CSS 1 then we can make
>> a style generator which translate the CSS properties to the style
>> properties we normally supply to our elements.
>> We also need a style sheet creator which extract the information out
>> of our source file containing the classes. (We need it as a utility to
>> keep our information synchronised between our supplied css file and
>> our defined classes)
>> And now the most important :-) the interchangeability of the table and
>> div element.
>> We don't need the div element in our core code. We use the table, tr
>> and td element and define in our class file the properties for it's
>> positioning, the border and the rest.
>> If your browser supports css then our page generator should ignore the
>> table, tr and td element and replace them by <div>.
>> Because we stored the dependency between the elements it's possible to
>> create a beautifull correct page-layout.
>> the header and the body and make it possible to write the event
>> properties of an element then flexibility is created!
>> Your comments please.
>> Marc Groot Koerkamp.
>> squirrelmail-devel mailing list
>> List Address: squirrelmail-devel@...
>> List Info:
> squirrelmail-devel mailing list
> List Address: squirrelmail-devel@...
> List Info:
| My BlowFish ate my MD5 |