> >Some of my other plans are to go into real war with Flash
I guess it depends on which context you look at Flash in. I think DHTML is
superior for well designed site interfaces that may or may not deploy Flash
elements inside of them. Flash performance on scrolling of heavy text is
very poor.
Also, Flash is an SVG based technology and I would tend to be more
threatened by it from it's dynamic scalability perspective rather then its
ability to animate objects, though scaling plays a large role here to.
Flash sites (moving lines of random motion) have been deprecated
significantly but it's finding new life in embedded objects and wireless
technologies market. Scalable vectors prove "very" beneficial in these
environments.
If you want to truly go to war with Flash (where it matters) be prepared to
integrate SVG and all the misery that comes along with a partially
implemented solution. Personally, I think Flash provides a clear role for a
limited use (great for MP3 integration), other developers may tip the scale
of preference the other way.
I think we will make stronger inroads focusing on integrating DynAPI with
the server side object world (in a platform heterogeneous way) then
attempting to make non scalable sprites compete with scaling vectors. In
the end, most clients would love to have dynamic interfaces presenting
server-side objects remotely rather then watching a lines wiggle on the
screen.
DynAPI's power is in its adapability and the speed which an open source
group with defined focus can move a platform. Lets just make sure we move
it in a direction that matters.
Laters,
Ray
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
