Studio MX 2004 released Support Product Page

This topic was archived

Dreamweaver's Lack of JavaScript Support

Posted 18 Sep 2003 22:49:45
1
has voted
18 Sep 2003 22:49:45 elliot larson posted:
I was really hoping that in this version of Dreamweaver, Macromedia would greatly improve its handling of JavaScript coding. Currently there really isn't a good integrated IDE for developing JavaScript scripts. I would like to see Dreamweaver offer code completion for JavaScript, integrated debugging, and a better JavaScript help section. The current layout of the Reference panel makes it really a pain to use. Nusphere's phped IDE got it right. They give you a searchable list of functions, and you can click to see a full page article on the chosen function in the editor window. This is a huge help.

Dreamweaver also does this strange thing with JavaScript where the color coding preferences only work if the JavaScript is in a separate .js file. If you are writing JavaScript in an HTML page, your color coding preferences don't work. Since most JavaScript is identified as such in the script tag it shouldn’t be that hard to provide this.

Additionally, Homesite allowed you to split the code screen into two different sections, so you can work on one piece of code at the top of your page, while having access to code in another part of the page. This was really helpful. I wish Dreamweaver could have this feature.

Overall, my impression is that Dreamweaver is an awesome, very polished IDE, but it caters more to the visual developer than it does to hand coder, which was fine when Homesite was available, but now, it is clear that Macromedia is phasing Homesite out. As a result, I have been using tools like TopStyle Pro to write my XHTML and CSS. If TopStyle offered better(any) JavaScript support, I don't think I would use Dreamweaver anymore. Alas, creator Nick Bradburry says he has no plans to get involved with JavaScript. Too bad.


Replies

Replied 21 Sep 2003 02:52:41
21 Sep 2003 02:52:41 Diane Jensen replied:
I have to agree. I use JavaScript in just about every site I build, and DW is useless for help with the code. I think this expensive version will cause a lot of us to look at alternatives. I've already been using TopStyle rather than DW for my CSS. I'll bet Adobe comes out with something better soon in a GoLive update!

Diane
Replied 21 Sep 2003 21:09:38
21 Sep 2003 21:09:38 Warren Beatty replied:
<BLOCKQUOTE id=quote><font size=1 face="Verdana, Arial, Helvetica" id=quote>quote:<hr height=1 noshade id=quote> I'll bet Adobe comes out with something better soon in a GoLive update!<hr height=1 noshade id=quote></BLOCKQUOTE id=quote></font id=quote><font face="Verdana, Arial, Helvetica" size=2 id=quote>

Adobe GoLive....hmm. Funny how people always say "This version of Dreamweaver sucks...I'm moving to GoLive." I'm not saying that is exactly what was said, rather what was implied. If everyone is so unhappy, then move to GoLive. For what Dreamweaver does, I'm not surprised there are bugs. As far as overlooked functionality, don't know what to say. The JavaScript I use in sites is often via extensions, and a few canned scripts found scouring the net. I have JavaScript reference books here too.

Reply to this topic