Replies Back to Article

Missing content and suggestion for update

April 10, 2002 by Danilo Celic

Hi, I really like the idea of this extension. It should haven't been avaliable as part of the SDK, but I'm glad that you were able to get it together. It seems that the functions that make up the APIs of each type of extension, (eg Commands), is not there. I tried looking up setMenuText, commandButtons, and canAcceptCommand and could't find anything. I think that listing the APIs you cover as "The xxxxx API" is not intuitive. I would find it better without the "The" Enjoy.

RE: Missing content and suggestion for update

April 10, 2002 by Greg Olone

Aren't the individual types of extensions listed near the top? I reinstalled the extension this morning and most of the extension APIs showed up at the top of the list (with a " " in front of them to group them together). If the search is not working, I will look into that.

As far as the naming scheme goes, I think it was an attempt to keep those APIs types together, the way they are in the manual. From the standpoint of someone who has used the manual for a few months, I guess it makes sense. I will look into posting an alternate reference.xml file with everything alphabetical.

Greg O'Lone, President
Stretched Out Software, Inc.

RE: RE: Missing content and suggestion for update

April 11, 2002 by Danilo Celic

George, thanks for the response.

I do not see any of the extension types listed at the top of the API drop down. Perhaps you have a higher version number than I do. I downloaded from the UDZone site and have 1.0.0.

I do see "Command functions", but it lists only : dw.edtiCommandList() and dw.runCommand(), not canAcceptCommand() and commandButtons() that I was looking for. The functions I mentioned in my post are Commands API functions, and I could not find them within the reference panel. I also did a Find within the reference folder and could not find the Commands API functions at all. I tried looking for other extension type API (Object, Property Inspectors, etc) and didn't find there API functions either.

I understand your reasoning about using "The," however, I always thought that was a failing of the manual. I'd suggest prefixing each type with "API -" and that would separate them from other types of DW functions.

Also, found a couple of typos in the UI access within Extension Mangager: You use &amp a couple of times, however you forgot the trailing semi-colon. And should it be listed as a Dictionary in EM rather than Reference?

Enjoy

RE: RE: RE: Missing content and suggestion for update

April 11, 2002 by Greg Olone

Danilo-

Sorry about the confusion...My guys installed a new version on my machine after I did the upload. The new version has been packaged and is now available from the site. Sorry about the inconvenience.

As far as your suggestions, yep, I agree. I will send them along to my programmers and see what they think.

Greg O'Lone, President
Stretched Out Software, Inc.

RE: Missing content and suggestion for update

April 11, 2002 by Waldo Smeets

Greg, again thanks for sharing it with us!

Lookup not working in DWMX

May 1, 2002 by Waldo Smeets

Greg, you might want to update this extension for DWMX. Macromedia moved the folder for reference books and this broke the lookup feature. Best is to check on version number in the js file to point to the correct path.

Extending Fireworks References

August 22, 2003 by Robert Walch

This is great! Almost just what I needed. How about an MX version, and and extension for dreamweaver to support fw js documents with code hints and such?

Excellent!

March 9, 2005 by Ryan Chesney

Kudos!  I spent hours trying to find this level of documentation on the web, forums and Macromedia's website.  Here it is in one place and integrated into the Dreamweaver Code Reference pallete.