Re: [Dynapi-Help] Dreamweaver plug-in specific

[Henrik V�glin]

I have begun to script my own dreamweaver extension for DynAPI with the Dreamweaver extended (and restricted) javascript DOM. Right now I'm finishing the command who will insert the necessary code to begin use DynAPI on a page. As for me it has nothing to do with not having to understand the DOM's or javascript as I'm doing this for my own use. Instead it's more out of convienience, cause i want to put my focus on the design at design time, so I can accomplish the UI I have in mind - on the edge DynAPI usage will though most probably still have to be done the "original way", which no premade extensions can replace, so I really don't see a conflict.   If anybody should be interested, I'd like to have an collaboration of extensiondevelopment, so just email me and you get a snapshot of the code in development...   Henrik V�glin ----- Original Message ----- From: Doug Melvin To: [EMAIL PROTECTED] Sent: Wednesday, December 27, 2000 3:23 AM Subject: Re: [Dynapi-Help] Dreamweaver plug-in specific 'tis alright.. I wouldn't have asked if I wasn't interested in everyone's opinions. :-) If not a plug-in.. how about a stand-alone..? Keep in mind here that the point is not to take the code away from the coders.. The point is to allow us to build the basic infrastructure of our dynAPI apps in less time..   More opinions/suggestions/comment wanted..   Doug Melvin ----- Original Message ----- From: Raymond Smith To: [EMAIL PROTECTED] Sent: Tuesday, December 26, 2000 3:04 PM Subject: Re: [Dynapi-Help] Dreamweaver plug-in specific 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 ----- Original Message ----- From: Doug Melvin To: dynapi-help Sent: Tuesday, December 26, 2000 5:17 PM Subject: [Dynapi-Help] semi OT.. well Ot then can anyone tell me if the result of encoding a string (or server.urlencode, or escape/unescape) is considered unicode data? Or alternatly, and VB coders out there, I am modifying the data uploading scheme of my companie's Web site admin software to use HTTP "Post" via the winsock control, and need to know how to encode my data so that it doesn't bugger up the server... (you know, incase the client puts / or \ or & , ect. in one of the product names or descriptions..)   Doug Melvin   P.S. Any VB coders out there interested in making a DreamWeaver Pluggin for DynAPI?