DynAPI
is supposed to do a little more then just setting your font colors or
face
If you
want simple things, don't use complicated solutions.
"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
"
No
it's not.. it's supposed to give tools (<- read S) to create heavily enhanced
websites that actually work
cross-browser. So again, if you'r looking
for simple stylechanging things, you could possibly
write
a
single function to take care of that...
Also
don't expect Opera support for a LONG while, they don't support 100% dom (as
usual) and have
left
out some key-functionality needed for DOM scripting.. so unless they start
putting that in for new
releases, Opera support will not
happen.
"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."
It
isn't .. it all depends on what you expect.
Actually all style properties can be set using the .css
property of a dynlayer but NS4 is not capable of supporting it
all.
Pascal Bestebroer
[EMAIL PROTECTED]
http://www.dynamic-core.net
-----Oorspronkelijk bericht-----I can't say that I know of any way to create a site without including special
Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Namens [EMAIL PROTECTED]
Verzonden: dinsdag 6 maart 2001 19:20
Aan: [EMAIL PROTECTED]
Onderwerp: Re: [Dynapi-Dev] Suggestions for the DynAPI - Part 2
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.
