Archive for May, 2011

FTPS support in Dreamweaver CS5.5

FTPS (FTP over SSL) provides both encryption and authentication support as compared to SFTP that offers only encryption support.

When using FTPS for data transfer, you can choose to encrypt your credentials, and also the data being transmitted to the server. In addition, you can choose to authenticate the server’s credentials and connections. The credentials of a server are validated against the current set of trusted CA server certificates in the Dreamweaver database. Certificate Authorities (CAs), which include companies like VeriSign, Thawte, and so on, issue digitally signed server certificates.

For more information, see http://help.adobe.com/en_US/dreamweaver/cs/using/WSee8adad8a8c1990b-6cb1a36e1266d204f20-8000.html#WSeffff8bffc802084-1de4b49712def0f4ecb-8000

Dreamweaver’s integration with jQuery Mobile and PhoneGap

Dreamweaver’s integration with jQuery Mobile and PhoneGap helps you create and package web applications for deployment on Android™ and iOS-based devices.

To create a mobile application for Android or iPhone™ mobile stores, do the following:

  • You can use any of the starter pages to create your Web application. However, if your web application, when deployed as a mobile application, accesses features native to mobile devices, use the jQuery Mobile (PhoneGap) page.The jQuery Mobile (PhoneGap) starter page contains the phonegap.js file in addition to the other jQuery Mobile files. The phonegap.js file contains the APIs required to work with the native mobile features such as GPS, accelerometer, camera, and so on.
  • Create a package of the application. Dreamweaver uses PhoneGap SDKs to create the package (.apk file for Android/.xcodeproj for iPhone/iPad).
  • Use the APK or XCODEPROJ file to deploy your web application to multiple platforms.

For more information, see

http://help.adobe.com/en_US/dreamweaver/cs/using/WSeffff8bffc80208478c8d43312e240fe0ad-8000.html

www.adobe.com/go/dw_mobileapp_sampleapp

Using Dreamweaver with jQuery Mobile to create web applications

Dreamweaver’s integration with jQuery Mobile helps you quickly design a web application that works on most mobile devices while adapting itself to the dimensions of the device.

For more information, see http://help.adobe.com/en_US/dreamweaver/cs/using/WSeffff8bffc802084-16bff63f12dbccd7e7c-8000.html

What’s new in Dreamweaver CS5.5

Dreamweaver CS5.5 provides a bouquet of features that help make it very simple for you to transition your current site to mobile platforms and devices.  Increased support for CSS3, FTPS support for better security, and W3C validation support are the other wonderful features that make Dreamweaver CS5.5  a must buy.

For more information on features that are new to Dreamweaver CS5.5, see:

http://help.adobe.com/en_US/dreamweaver/cs/using/WSe8b0455615e2dc47-1c751e8b12f0330ea27-8000.html

http://www.adobe.com/devnet/dreamweaver/articles/whats-new-dwcs55.html

Media query and Dreamweaver CS5.5

There was a time in the history of computers when users did not have too many monitors to choose from.  That was very good for web designers because there were only so many resolutions to cater to. The rules ensured that that their sites catered to the least possible resolution and extra spaces were filled up with beautiful backgrounds as users switched to higher resolutions. As monitor sizes increased and users’ preferences for resolutions changed, the rules changed too. Nothing dramatic – loosening a nut here, tightening a bolt there, and it was all done.  And Dreamweaver pretty much had the design aspect covered on all fronts.

With the advent of Web 2.0, the websites got way more smarter than their static HTML ancestors. There was more coding than what a designer could probably handle. Most designers either took to coding, or started working with teams that helped bring intelligence to design.  It was but natural for Dreamweaver to provide increased support for developers in the code view. ColdFusion, ASP, JavaScript, database connectivity – Dreamweaver tried to accomodate developers of all hues.

From design to code and back to design – the advent of mobile devices changed the rules yet again.  While designers were well accustomed to designing for increasing resolutions, with mobile devices they had to contend with shrinking monitor sizes. The websites not only had to display well on desktops but equally well on mobile devices that had no standard monitor size.  It would have been neigh impossible, if not downright foolhardy,  for designers to create a website for each resolution.

It was pretty obvious that the way forward was going to be driven by style sheets.  You create a different style sheet for different monitor size resolutions to help customize display on various devices.  But how would a browser know the CSS to use for displaying the site? Enter Media Query, a piece of code on the site that specifies the CSS to be used for a range of resolutions.  Media Queries use the reported dimensions of the monitor size to specify the CSS for the device.

It is but obvious that a website will look very different on the devices that it is displayed on – tablets, desktops, and mobile phones for now.  With media queries, you can have a single functional website that works the same but looks very differently on the devices that it is used. In Dreamweaver, you can create a site using media query, and also preview the site as it appears in devices with various resolutions. Dreamweaver helps ensure that when your site goes live, it looks and behaves exactly the way it did when it was previewed.

For information on using media queries in Dreamweaver CS5.5, see http://help.adobe.com/en_US/dreamweaver/cs/using/WSeffff8bffc80208443aaa2ab12db791fb9b-8000.html

Adobe Help Application: Access Denied Error Message

When opening the Adobe Communtiy Help application in CS5.5, the following error message appears:

“ACCESS DENIED”

This error is a result of a malformed property in the help configuration file. The file was mistakenly published with a staging URL (help.stage.adobe.com) instead of the production URL (help.adobe.com).

For information on troubleshooting this problem, see the article: http://kb2.adobe.com/cps/902/cpsid_90284.html