Without going into too much detail (probably already too late for that statement?) I believe what you are seeing is actually an *opportunity* to customize, not a requirement.
Media Query (CSS3 option) allows for formatting based on the device being used to display. You can define as many or as few targets as you like, and the definitions can be within ranges. That means you can choose to: define one "look" for everything, define mobile, tablet, laptop and large monitor targets define more explicitly for specific devices Regardless of the tool, the CSS3 simply needs to know the things that are important to you, and then apply the formatting based on the user's device of choice. RoboHelp provides device definitions for things available today, and allows you to define new things as they become available, or customize the things that already exist. -Matt Matt Sullivan technical communication | online training | eLearning twitter: @mattrsullivan phone: 714 960-6840 On Feb 11, 2013, at 9:37 AM, "Carol J. Elkins" <celkins at awrittenword.com> wrote: > Matt, yes I am using RH's Multiscreen output. I'm annoyed at the differences > in the out-of-box options for the various device outputs. There doesn't > appear to be a unified "set" that retains the same color scheme or other skin > characteristics. But my biggest whine is that RH10 treats the device outputs > as separate entities with a separate folder for each output device. There is > a separate index.htm file for each output device. And within each device > folder, the entire set of templates for each device is repeated. For > example, here is a simplified folder structure to illustrate: > !ISSL! > --Multiscreen_HTML5 > ----|android_galaxy_tab > ------|index.html plus my project files > ------|template > ---------|Android_Phone_Layout > ------------|all PNG files for the layout > --------|-Desktop_Knowledge > ------------|all PNG files for the layout > ---------|iPad_Layout > ------------|all PNG files for the layout > ---------|iPhone_Layout > ------------|all PNG files for the layout > ---------|Kindle_Fire_Layout > ------------|all PNG files for the layout > ---------|resources > ---------|scripts > ------|whxdata > ----|android_phone > ------|index.html plus my project files and the other folders as listed above > ----|desktop > ------|index.html plus my project files and the other folders as listed above > ----|ipad > -------|index.html plus my project files and the other folders as listed above > ---|iphone > ------|index.html plus my project files and the other folders as listed above > ----|kindle_fire > > I don't understand why the redundancy is necessary. So what I'd like to know > is whether or not WWP's output contains this redundancy or whether they build > all of this into one separate HTML5 and one separate css. It seems to me that > as the device market expands and new devices are added, RH will be limited by > what it is currently configured for. What I see in WWP suggests that their > coding will be truly "responsive" and flexible regardless of the device that > displays the output. If I'm wrong here about either product, let me know. > That's what I'm trying to determine. > > Carol > > At 09:38 AM 2/11/2013, you wrote: >> @Carol, are you using RH's HTML5 SSL, called Multiscreen? >> >> Although you can still create SSL's per device, using Mulitscreen as your >> SSL produces only one set of HTML files, with a single CSS3 to do exactly >> what you mentioned in your post. > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.frameusers.com/pipermail/framers/attachments/20130211/7e8a721b/attachment.html>
