Key Problems at Adobe and with Dreamweaver CS3
February 14, 2009 Category: Client Programming, Desktop Databases, ECommerce, IDE Editors, Web Databases, Web Programming
If you have rang Adobe suport for help and support on, say Dreamweaver MX 2004 or CS3 problems, then you will no doubt understand our sentiments!
Not only does Dreamweaver has serious problems handle thousands of images in a given directory, but if you ask Adobe support for a resolution they will tell you to ‘another ftp client’ - which clearly should be illegal under the grounds of ‘not being fit for purpose’ (here in the UK).
If that was not bad enough, if you have a given file that you are working on that is a specific size in bytes - or any factor of this size, you will have serious problems with Dreamweaver. This is clearly an outrage and needs to be solved, rather than just releasing new versions such as CS4!
In our opinion, if you dont have to use Adobe Dreamweaver MX2004, CS3 or CS3 - then we would recommend either the Open Source GUI IDE’s such as Eclipse and Notepad++ - both of which can print in colour - something which Dreamweaver MX2004 and CS3 cannot!
Dreamweaver CS3
January 25, 2009 Category: IDE Editors
As a WYSIWYG IDE (integrated development enviroment), Dreamweaver can hide the HTML code details of pages from the user, making it possible for non-coders to create web pages and sites. One criticism of this approach is that it can produce HTML pages whose file size and amount of HTML code is larger than an optimally hand-coded page would be, which can cause web browsers to perform poorly. This can be particularly true because the application makes it very easy to create table-based layouts.
In addition, some web site developers have criticised Dreamweaver in the past for producing code that often does not comply with W3C standards, though recent versions have been more compliant. Dreamweaver 8.0 performed poorly on the Acid2 Test, developed by the Web Standards Project. However, Adobe has increased the support for CSS and other ways to lay out a page without tables in later versions of the application, with the ability to convert tables to layers and vice versa.