Re: [Dynapi-Dev] Suggestions for the DynAPI - Part 2

[JonathanErinDale]

I can't say that I know of any way to create a site without including special
conditions for specific browsers.  But from what I have seen of the DynAPI
code and all of the comments about it, the DynAPI is supposed to create an
object that emulates a browser's document object and provide a way to create
sites that operate as expected in at least NS and IE, possibly Opera soon,
with support for at least 4.x and up browsers.  I realize that bugs will
happen and that is an issue with code.  But when I can create a layer without
the DynAPI that allows me to set color and font properties, along with border
properties but can't do it with the DynAPI then I would think that it would
be a serious problem.  Having to use a 'label' which cuts out a number of the
properties available to a general 'layer' just doesn't seem right to me.  
Maybe I'm wrong here, maybe I'm missing the point, but from my closer
inspection of the code, it looks like it would be easier to just move the
label methods and properties into the layer object and still come out with
better code.