Some time ago - right after the release of CS6 - I popped a question several places, including a feature request directly to the DW staff, at Adobe.
The question was about the possibility to get the Server Behaviors within DW CS6 updated to make use of the new and improved MySQLi- and / or PDO-features.
Yet, nothing has happened...
Now, I´m asking you guys - in the forum, if I´m the only one, having this feature high on my priorities list???
Also - IF any members of the dev-team is reading this forum, I´d really like an answer to this question, from you.
Behaviors are like pre-defined snipplets - only with some-what crappy additional code; so in that perspective, I totally agree with you.
I just want Adobe to recoqnize, they´ve forgotten to update one the key-features in DW - as MySQLi and PDO are the Standards of web-development today - and what more; I want the dev-guys to DO something about it!
In DW CS6, there has been so many improvements on other areas - but this, they seem to have forgotten completely.
Let´s make this a widespread discussion as to what can be done to:
I´d really like some input from other high-end devs (and the Adobe DW-devs) on this too, please
I have never used DW Server behaviors. My observation is that most DW users are still using the older mysql extension, though of course they should upgrade. Maybe DW is waiting to follow the lead of their user-base.
I don't use DW to write any code, for the following reasons:
1. I like my own code better, my naming conventions, etc. and only use the PDO extension.
2. I use a Logitech G19 programmable keyboard which allows me to enter commonly used keyboard sequences in single keystrokes.
3. I keep a library of snippets for common code sequences that are longer than the G19 keyboard can maintain.
4. Although I don't use a framework like ZEND, my code is portable, at least across my own projects.
Therefore, if Behaviors and Spry are ways of generating sections of code quickly, I have my own personalized way of achieving the same thing, better. I have sometimes wondered if serious coders ever do use things like Behaviors, Spry, etc. Don't misunderstand me--I'm not saying that "no serious coder would use behaviors," but I assume (as someone who has never used them) that at some point every coder would outgrow them, for the kinds of reasons W3 mentions--wanting to use a database extension they don't support.
I agree with you too, Rob - no question ´bout that.
I´ve also adapted a nice collection of snipplets and use my own naming convetions - but this is not within the scope of this thread.
For DW to maintain its position as one the leading brands of IDE´s, I think it´s important, to stay "on top" in all "diciplines" - including the handling and execution of the latest SQL-standards.
Spry is not even an option in my book - as jQuery does the job, so much better.
If options supplied in an editor does not live up to industri standards - they should either be updated or removed.
Either way demands action from Adobe - which is my objective, with this...
I´ve used DW very little, the last year, as CODA and NetBeans does the job just as well - but I still believe, DW deserves a fighting chance.
Yes, I realize my post diverged from the original focus, but the thing I did mention in the beginning is that most of the people who frequent this forum seem to still be using the original mysql extension, so Adobe may not be feeling the pressure to upgrade. Big mistake for everybody, of course. Everyone needs to stop using the old extension.
I have not used Netbeans or CODA. Not even familiar with CODA. I use ZEND studio. Yes to jQuery over spry. I don't think spry offers anything I can't just code myself, but jQuery has some very useful widgets.
I have used Coda and it's SQL editor and CSS gradient tool in Coda 2 is amazing. However, I've encountered enough bugs with using responsive design and their preview to hold off on a complete switch at the moment. I tried reporting it but they don't see responsive design as a prominent market at the moment.
I just came about this post today.
Normally I always do all my coding manually (no wizards) and I only use the mysqli versions of the php functions.
This week I was tinkering about woth CS6's Database bindings with the idea of: "It's Adobe so it could be better en easier than what I' doing".
WHAT A DISAPOINTMENT!!
I fully agree that CS6 should have moved on to the newer ad more modern mysqli behaviour/functions!!
@ Dreamweaver team: PLEASE ISSUE AN UPDATE THAT TAKES CARE OF THIS!!
(sorry for me having to shout this out loud ).
I want to add my voice to this request. I've been a Dreamweaver user for several years but now I am starting to use other tools to write PHP code because of the lack of support for MySQLi- and / or PDO. The PHP coding forums are saying lots of negative things about DW because of this and serious developers are leaving.
Dreamweaver team: When are you going to support these important features??? At least let us know if you are listening to us!
I agree. If the mySQL support is not updated to stay current, DW will die. I hesitate to build anything new in it because of this issue. RIght now, it is an expensive code editor that does not do a whole lot more for me that UltaEdit on new projects.
DMXzone is scheduled to release a free Dreamweaver extension today that may provide a solution to this issue for some people. The extension isn't out yet, but they posted some screen grabs and a tutorial at:
It appears that the extension can use both public rss-type feeds and local databases as sources of data. The examples all show how it manages public feeds, cuz that seems to be what the developers are excited about, but this "HTML5 Data Bindings" extension looks to me like a very promising replacement for the database functions in Dreamweaver.
I don't think so unless you want to code your connection into a feed and read it that way. Even so, I doubt the extensions will be able to read the feed. I suspect that the "database" source will use the DW PHP/MySQL connection that DW already uses.
I hope you're right, but I don't think this is it.
Don't worry, just spend another grand on your suite and it will be in CS7 with the bugs fixed in CS8.
Maybe it is a little more promising than I thought...
http://www.dmxzone.com/go/21868/dmxzone-database-connector-coming-soon /?utm_source=DMXzone+Newsletter+Content&utm_medium=newsletter&utm_cont ent=DMXzone+Newsletter+%282059%29+6%2F26%2F2013&utm_campaign=DMXzone+D atabase+Connector+Coming+Soon
... not holding my breath though.
I feel your pain. As a stopgap measure, I found this from Oracle, a converter that can sweep through your .php pages and convert the mysql_ functions to mysqli_.
I haven't tried it yet, but I do know that the converter needs to connect to the databases to work properly, and it will not follow the Dreamweaver-generated "include" statement to find Dreamweaver's connection scripts. Because of that, the code from the connection scripts will need to be pasted into the .php pages to replace the "include" bit, at least temporarily.
Also found a post from Shawn Reeves, who documented the steps he took to convert his pages from mysql_ to mysqli_. He posted Dreamweaver regex find and replace strings to handle the conversion all within Dreamweaver itself.
Neither of those is a final solution. One of the advantages of using mysqli is to use php's "prepare" function to protect against SQL injection attacks, and those methods will not rewrite the Dreamweaver code to do that.
Also, the Dreamweaver-generated code is written in php's "procedural" syntax, and it needs to be switched to the "object oriented" syntax. I found a tutorial on how to do that, but the conversion of hundreds of .php pages will be tedious at best:
I found the same articles, but once converted, DW is useless.
I'm basically moving to PHPStorm for development and using DW for templates or not at all. I went from 3 to 5 to 5.5 to 6 and the deprecation notice has been there throughout. For the kind of money Adobe wants and the crappy upgrade deals, enough is enough. I still use PS, AI, etc., but Adobe has been killing DW for a long time. They killed ADODB through InterAkt, not really supported IDE development or updated DW meaningfully for the future. Flash is dying to HTML 5 and jQuery/Bootstrap with the proliferation of mobile devices.
Now they want a subscription and go to a SAAS model.
How's about an update that fixes all versions of Dreamweaver to at least use MySQLi. I like to use PDO, but would settle for only the improved extension. I imagine that Adobe hasn't done anything about this because they assume that even though the MySQL extension will soon be deprecated that, like other older things that are deprecated but whose total removal would break the web, support for MySQL will not be removed from PHP versions going forward.
I like using the things in Dreamweaver that are driven off of the database connection. I like being able to build forms based upon what's in my database. I like controlling the login features based on that as well. This is a big deal, enough to get me to give up on Dreamweaver if it doesn't get fixed. Otherwise, why shouldn't I just use Netbeans? It isn't nearly as good as Dreamweaver in terms of what it can do for me, but it would force me to get away from building stuff that would only break in the worst case scenario (which I have to respect even if Adobe doesn't), to the anger of those I build things for, very soon.