Hello everyone, I had posted a message to the DynAPI-Help concerning Javascript include file errors (see http://www.geocrawler.com/lists/3/SourceForge/7120/0/7480317/ ).
I think I have discovered why I have been experiencing so many problems with the include files, as well as why so many other users have experienced problems using DynAPI. It's generally not because they are screwing something up, its because the development tool they are using is not properly interpreting the Javascript files. Both in Microsoft Visual Interdev 6.0, FrontPage XP and even in Notepad.exe, when I pull these files up, there are conversion problems (often <PRE> and </PRE> tags are present, < has been converted to <, > to >, " to ", & to &, etc.,). Wordpad.exe does the best job of interpreting these files, but even this has problems (pull up dynlayer.js in Wordpad and look at the number of converted characters you get). In a development tool like FrontPage, the code looks as it should in "Normal" view, but is messed up in "HTML" view. I suspect this interpretation issue has been an enormous problem to the use of the DynAPI platform ever since its inception. Dan Steinman's original DynAPI suffers from the same interpretation problem. The easiest way to solve this problem, I have now discovered, is to make sure these included files show up properly in "HTML" view of Microsoft non-Javascript development applications. I hope this helps your group expand the usage of DynAPI further than at present. You all should feel pride in doing such a wonderful service to the development community! Yours truly, Jerry Hammann _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com _______________________________________________ Dynapi-Help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dynapi-help
