|
To me, it just seems "itchy-wrong" to
even ponder assimilating the DynAPI into a (mutter) WYSIWYG html
editor. While we all know that Macromedia assuredly lurks here hoovering
all our sweat and spent brain-calories for the next great "cut and paste"
editor for the masses; I think handing it to them in any form or fashion is
fundamentally wrong.
To me the DynAPI represents a higher 'art-form'
then what I like to term 'tool-users'. While a tool, in and of
itself, the DynAPI offers the ability to truly learn the DOM's and
oddities of each particular browser rather then having it hidden in the form of
drag-drop components.
The web is already plagued with the misconception
that a good web implementation should cost about $600.00; which surprisingly is
a faction of what most companies spend on paper based collateral. Most of
this fostered by people spending $400 for a piece of software (insert
Dreamweaver here) and then hanging a shingle outside their house announcing
"grand-enterprise".
I prefer to think of us all as
"Freeriders" liberated, by choice.., from the limitations of
prepackaged software. Were "tool-builders,
implementers" vs. "tools built by others,
used". Big difference.
Guess you struck a cord there Doug... Sorry
for the banter.
DS
|
- [Dynapi-Help] semi OT.. well Ot then Doug Melvin
- RE: [Dynapi-Help] semi OT.. well Ot then Eytan Heidingsfeld
- Re: [Dynapi-Help] Dreamweaver plug-in specific Raymond Smith
- Re: [Dynapi-Help] Dreamweaver plug-in specific Doug Melvin
- Re: [Dynapi-Help] Dreamweaver plug-in spec... Doug Melvin
- RE: [Dynapi-Help] Dreamweaver plug-in ... Theo Bebekis
- Re: [Dynapi-Help] Dreamweaver plug-in spec... Henrik V�glin
