Forums
This topic is locked
"DOG" tag inspector does not work in DW 7.0.1
Posted 20 Mar 2004 02:25:52
1
has voted
20 Mar 2004 02:25:52 Ann Lynnworth posted:
Does anyone have the DOG tag inspector example working in DreamWeaver? I tried it in veirsion 7 and 7.0.1 and the property inspector just does not work.Absolutely nothing happens if I put the file into the global Macromedia configuration\inspectors directory. If I put the file into the private (user settings area) configuration\inspectors directory, something (an error) happens when I click on the </dog> tag but I can't call that "working".
What is going on? Is DreamWeaver extensible or isn't it?
Another example which does not work is the one documented in the book, "DreamWeaver Extensions" by Laura Gutman. See Chapter 6, Making Inspectors: Practice Session. (The book is online at safari.informit.com) Following those steps leads to NOTHING HAPPENING in the property inspector.
Is version 7 completely broken?????
Replies
Replied 20 Mar 2004 02:36:46
20 Mar 2004 02:36:46 Ann Lynnworth replied:
Okay, to make the DOG example work you have to include at least a BREED attribute or it will not open the property inspector. That rule is hardcoded in the javascript file.
Still don't know why the "mood" example won't fire....
Still don't know why the "mood" example won't fire....
Replied 20 Mar 2004 02:52:43
20 Mar 2004 02:52:43 Ann Lynnworth replied:
The problem with the "mood" example from the book (safari online version) was that what looked to be a comment tag in the beginning of mood.htm was in fact a funky unicode character. All the hyphens in the first line were not simple hyphens, although visually in Notepad, EditPlus, Peter's XML Editor and DreamWeaver, they sure LOOKED like hyphens. Opening the file in Unipad (www.sharmahd.com/en/) revealed the syntax problem instantly.
So -- bottom line -- for anyone encountering similar problems -- open your HTM and/or JS files in an editor able to display Unicode information, and you may find some very surprising facts.
"There is no substitute for eternal vigilence."
So -- bottom line -- for anyone encountering similar problems -- open your HTM and/or JS files in an editor able to display Unicode information, and you may find some very surprising facts.
"There is no substitute for eternal vigilence."