Video: Multiscreen previewIf you're designing for multiple screen sizes, having the ability to accurately preview for those resolutions is incredibly important. The Multiscreen Preview panel was first introduced as part of Dreamweaver's HTML5 pack. With the CS5.5 release, it joins Dreamweaver as a native feature. So I have the index.htm in the 03_04 folder opened up, and this is going to give us an opportunity to explore the Multiscreen Preview panel and see what it can do for us. So this page currently has two media queries applied to it: one for tablets and one for mobile devices.
- Where to go from here
Viewers: in countries Watching now:
This course covers the enhancements to the latest release of Adobe's web design and development software. Author James Williamson examines Dreamweaver's updated support for current Web standards, such as code hinting for HTML5, CSS3, and jQuery, and new W3C-compliant code validation. James also demonstrates the new features introduced specifically for mobile development that allow developers to download, install, and configure native applications for Android and Apple iOS. These features include support for PhoneGap integration, jQuery mobile framework, native binaries, and platform emulators launched directly in Dreamweaver.
- Creating new HTML5 documents
- Using code hinting for CSS3, HTML5, DOM elements, and jQuery
- Configuring jQuery widgets with the Widget Browser
- Managing media queries
- Previewing web pages on multiple devices with the Multiscreen Preview panel
- Configuring mobile application frameworks
- Building and emulating mobile applications
If you're designing for multiple screen sizes, having the ability to accurately preview for those resolutions is incredibly important. The Multiscreen Preview panel was first introduced as part of Dreamweaver's HTML5 pack. With the CS5.5 release, it joins Dreamweaver as a native feature. So I have the index.htm in the 03_04 folder opened up, and this is going to give us an opportunity to explore the Multiscreen Preview panel and see what it can do for us. So this page currently has two media queries applied to it: one for tablets and one for mobile devices.
So if I go to my Multiscreen Preview panel and I click that to open it up, you can see it takes up a good bit of screen real estate, and if you have a high screen resolution, you can probably flip this panel around a little bit, but more often than not, it's going to take up a good portion of your screen real estate. So I have a Preview section for Phone, one for Tablet, and one for Desktop, and if I look in the upper right-hand corner, I have a few buttons up here as well. The first one is Media Queries, and if I click on that, we're going to see the same Media Query dialog box that we were working with in the previous movie.
So you can still manage, create, and control your media queries directly from the Multiscreen Preview panel. I am just going to go ahead and cancel that. And the next button is for Viewport Sizes. Now, each of these viewports-- one for Phone, one for Tablet, and one for Desktop--have discrete resolutions, and if I click this, I can affect those. So I could go into the Phone one, for example, and I could crank that one up to say 480 pixels wide. If I click OK, you can see that it has now manipulated this viewport. And of course I lost some space over here in Tablet, so I have got some clipping that occurs.
It does give me a scrollbar, but it's still clipping it just a little bit. So you can go back any time you want to to Viewport Sizes and you can choose Reset to defaults, click OK, and you're right back to where you were before, which is pretty cool. Now, in looking at this, everything looks okay. I have got my layout here in Phone that's different than the layout in Tablet that's different than the layout in Desktop. But the big problem is that for Tablet, this tagline really isn't supposed to be there. So that's one of the nice things about the Multiscreen Preview; we're able to find an error in the Tablet styles right off the bat.
Now, I would love to tell you that the Code Navigator works directly here inside the Multiscreen Preview, but it doesn't, so I am going to have to close this panel in order to find the problem. Now, I need to access my Tablet styles, and when you're dealing with your normal window, one of the easiest ways to do this is I'm just going to go ahead and minimize this window and float it. Now, on the Mac it's already floating, but on the PC I have to explicitly float it, and then I'm just going to scale this down until I start seeing my Tablet styles. Now, you may want to turn Live view on, but it's not required for what we're doing.
Now, as soon as I do that, I'm going to go ahead and find this tagline by using the Code Navigator. The easiest way for me to do that is to hold down the Alt key and click one time. Now, on the Mac you'll be holding down the Command+Option key and then clicking. Then I'm going to browse down to find my tablet.css, so that's why it was necessary for us to resize the window so that we could access those tablet.css files. I can see that we have an actionCall h1 selector inside the tablet.css. So I don't want to access to one in main. I want to make sure I am going into the one in tablet. I will click on that, and right there on line 62 I can find the actionCall h1.
Ah, that's why it's showing up, because it doesn't have the display: none property that it needs. So we'll go ahead and save that, and I'll go back to Design view, maximize my page again, and now it's time to go back to our Multiscreen Preview panel. Now the tagline is gone, and the find your tour action call button is in the right place. Perfect! Now, other than just previewing a single page, the Multiscreen Preview panel allows us to do something that's really, really neat, which is to preview multiple pages.
So I can follow these links, and I can click on any menu to follow the links and to jump from page to page. You can even test features because what we're getting here is we're getting basically a WebKit preview. So if go over to Tours, for example, I can scroll down in the mobile version and I can test the CSS transitions that I have here for hover events. In a mobile world, if you click or touch one of those particular items, it would go ahead and expand and you can read it, and that saves us a little bit of space in our mobile device. And I can preview that directly here inside the Multiscreen Preview without having to test that on the phone.
So that is really cool! I also notice that in the upper left-hand corner here I have what looks to be a browser navigation bar, and it works exactly the same way. You have your Back buttons, you have your Forward buttons, you can refresh the page if you would like. And if you want to go back to the page that you started in, you just click Home; that doesn't always mean that you're going to go back to the index page, but it is going to go back to the page that you actively have open and that you're currently browsing. Now, the Multiscreen Preview panel isn't the only way that I can test for different screen sizes. We've talked about this a little bit earlier, but I just want to show you this again.
So I am going to close the Multiscreen Preview panel. Notice that right down here under our Window Size, I can click on that, and I can Preview say Tablet or Smart Phone or Full Size, and those improvements do make it a lot easier to preview for different resolutions, but the Multiscreen Preview panel gives us a way to preview for multiple resolutions at the same time. And they give us the ability to click through the site to see how our media queries are affecting multiple pages. So if you need to design for multiple devices, I think you're really going to enjoy using the Multiscreen Preview panel.
Find answers to the most frequently asked questions about Dreamweaver CS5.5 New Features .
Here are the FAQs that matched your search "" :
- Q: This course teaches us how to create mobile app in the "Mobile App Support" chapter and the app works great. But when we try to upload to android market, it says that the Android Market can't upload a debug/release version. What's wrong with the app?
- A: As mentioned in the movie, the Dreamweaver emulator support does not create deliverable apps. It is designed to act as an IDE and debugging environment only. From there it is up to the developer to package and distribute apps to the various app stores.
Take a look at https://build.phonegap.com/. It's an early service dedicated to creating deliverable binaries for multiple platforms. Since it's PhoneGap, it's also the same framework used within Dreamweaver, so Dreamweaver based apps should port right over.
Sorry, there are no matches for your search "" —to search again, type in another word or phrase and click search.