Design view is significantly different from output in Robohelp 10

This may be normal for Robohelp 10. I am not sure.
I am applying a new CSS to my company's help project as part of a major update to the design. The CSS includes table styles, and list styles - something that was signficantly lacking from the previous design.
I have noticed that there are significant differences between what I see in the design view and what I see in the output, and this causes a lot of confusion.
When applying the bullet style, in the design view I see a numbered list. However, the output displays bullets as I specified.
When applying a table style, the table looks unformatted until I view it in preview mode or generate the project.
My roman numeral list style appears as decimals in design view, but looks fine in the output.
This is very confusing to work with, and initially led me t make many manual changes before I realized that what I am seeing in the design editor is completely misleading.
Any suggestions are welcome.
Yehoshua

This is how it appears when I edit the style in Robohelp:
This is how it appears when I apply the style in design view:
However, when previewing the page (and also when generating ouput):
As I said, it is very confusing and misleading.

Similar Messages

Problem: design view looks completely different than live view

I am trying to make changes to my home page in Dreamweaver, and when I am viewing the page in 'design view' the background image for the container is missing, and the divs are all over the place. When I view the same page in live view and in browser preview, it looks fine.
Because I can't really see what the page is going to look like in 'design view', I can't really make changes to the site. Any help would be much appreciated.
Link to screenshot of 'design view'
www.simply-eden.com/images/screenshot1.tiff
Link to screenshot of 'live view'
www.simply-eden.com/images/screenshot2.tiff
link for purpose of viewing the code only
www.simply-eden.com/images/index.html
Thanks for the help.

When things get really goofed up, it could be caused by malformed code or orphaned div tags. Sometimes browsers will let you slide with poor code, but DW Design View won't.
Use these online code validation tools and fix any reported errors.
HTML Validator - http://validator.w3.org
CSS Validator - http://jigsaw.w3.org/css-validator/
HTML & CSS Tutorials - http://w3schools.com/
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
www.alt-web.com/
www.twitter.com/altweb
www.alt-web.blogspot.com

PDF/X-3:2 (PDF 1.3): Destination differs from Output Intent; how to set Destination -

Hello.
In InDesign CS5 (7.0), I set up a document containing greyscale images (profile: Dot Gain 15%) and cmyk-images (profile: Euroscale Coated v2). The latter is also the working space, and it is also the Output Intent Profile Name set in the Export Adobe PDF Dialog under Output – PDF/X. The Colour Settings in the .indd set the Colour Management Policies to Preserve Embedded Profiles (and Colour Conversion is set to No).
Now, when exporting this .indd to a .pdf (PDF/X-3:2 (PDF 1.3)), the Summary tells me that the Destination is ISO Uncoated Yellowish, and Acrobat (View – Navigation Panels – Standards) feels:
Conformance:
Standard: PDF/X-3:2002
ISO Name: ISO 15930-3
Status: verification succeeded
Trapped:False
OutputIntent
Identifier: ISO Uncoated Yellowish
Info: ISO Uncoated Yellowish
—so what was Destination in the export settings now appears as Output Intent, meaning: the Destination overrides the OutputIntent as set in the export settings.
I have no idea where this ISO Uncoated Yellowish comes from. As far as I can see, nothing, neither in the placed content, nor in the document, has this profile set.
In a second document, with the exact same settings as specified above and the only difference that it contains only greyscale images. In this case, Acrobat sees the Identifier as FOGRA1 (which is indeed the (greyed out, unchangeable) setting in the export Dialog's Output – PDF/X – Output Condition Identifiert—but that is the case in the first document, too), and the Info as Euroscale Coated v2. This seems correct, but why might "ISO Uncoated Yellowish" appear in the first case, and how would I get rid of it and set the correct Destination?
Thanks a lot.

No, it isn't a colour space, but there's still grey profiles, specifying e.g. the dot gain.
Links panel does list the gray profiles, but they're not used in anyway.
If you assign different gray profiles in Photoshop the gray profile makes the conversion back to monitor RGB for preview. So here's the same image with 10% and 30% dot gain in Photoshop and the previews are very different even though the output values are the same:
If I place the two images in ID and turn on overprint the previews are identical (the output values are also identical)—via the document CMYK profile, which is EuroScale here. The preview would be the same if you pasted the grayscale into the black channel of a CMYK document:
If I export the ID doc as PDF/X-4 which includes all profiles, the grayscales show as DeviceGray (no profile):

Design view different from preview - is muse still in beta testing

I have limited experience with coding html so when Adobe released Muse, I was excited. However, I'm wondering if they released it too soon and/or if it is still in beta testing - which I don't mind but would like to know what I'm dealing with. It seems to have a lot of quirks - mainly that the design view is sometimes different from the preveiw or browser view. I spent over an hour yesterday trying to get text boxes to line up. If there is an hidden element affecting the text boxes, I don't see it. I have moved everything off the page and >selected all
and nothing shows up.
Other issues:
Sometimes paragraph styles do not apply - even though in design view it looks like they do.
Can't find a way to center text vetically in a text box other than adjusting the leading?
Can't find a way to organize assets into folders?
When an object is selected on a page, is there a way to indicate that that is the object in the assests panel?
Sometimes the padding options are not available for no apparent reason.
Thanks to the Adobe staff for being responsive as these issues are discovered. One staff member in particular was very helpful as I was trying to get hyperlinks to work right. But I am STILL having a problem. The text box and the text itself have the hyperlink style applied but as you can see on the Dardanelle and Chad Lawson Trio hyperlinks - the style did not take even though they are both hyperlinks that point to the right URL. -- geezermusicclub is the correct link for Dardanelle - It's difficult to see in the pic, but the Dardanelle and Chad Lawson text color is black but the hyperlink text style is brown.
Persoanlly, I feel Adobe should lower the subcription price while all these kinks are being worked out in Muse. In a way, subscribers are **** a LOT of beta testing for Adobe. Not only are we not being compensated for that, we are having to pay for an application that has too many wrinkles.

Murray and David: it worked! It is a rare and joyous experience to have a straightforward solution to the sorts of problems I come up with (including other realms). But I have to say that with HTML and CSS (and hence with Dreamweaver), solutions to difficulties have seemed within easier reach than in other parts of the computer world.
By the way, I wanted to choose "correct answer" for both your posts, but after making the first click it was no longer available for the remaining post--so I typed "helpful" even though that one was correct too.
Thanks again.
--Paul

Design View differs from Live view problem

I have Dreamweaver CS5.5 with Mac OS 10.7.3 on an iMac. I have the same set-up on a Macbook Pro 17
The problem is that the Design view is showing different fonts and not picking up layout as per CSS style but the Live view is all correct.
All is fine on the laptop so it is my iMac specific glytch
I have checked the settings for diplaying CSS styles and they are ticked
I have switched off the activation settings for Suitcase Fusion 3 in case of conflict there
I have uninstalled and reinstalled Dreamweaver
I think it a font-related problem as the design view only seems to want to display non-serif fonts.
Am I doomed to only use the lap-top in my web work?
I hope someone can advise as I am rather frustrated

I think that's just the way it is...
http://forums.adobe.com/message/4312435#4312435
Martin

Table td not styling correctly in Design View CS4

Hello everyone!
I dont know if anyone else is experiencing this problem, or
if I'm doing something stupid! I've searched all over this forum
and google etc and found a few people with similar problem but no
solution.
please see this code (HTML first, then the external CSS file)
The code is complete, not truncated or stripped. In IE and
Firefox, the CSS body styling renders on all text outside the table
and inside the table (which I believe is correctly inherited) but
in CS4 Design View, the text inside the table renders at twice the
size!!
I'm doing a complex page and it's pushing all my elements
around in Design View and preventing me from working properly or at
times at all!!
Please tell me if this is a bug or is there something I can
do to stop it displaying like this.
Thank you!
Janine x

On Fri, 3 Apr 2009 09:29:57 +0000 (UTC), "Janine_Trumel"
<[email protected]> wrote:
> Sorry, I cant quite see why the first line of code is
causing the problem.
Regarding the XML declaration that Nancy suggested omitting,
the XHTML
specs suggest using the line, but it is not required if the
page uses
either UTF-8 or UTF-16 character encoding. See
http://www.w3.org/TR/xhtml1/#strict
where is says in part, "An XML
declaration is not required in all XML documents; however
XHTML document
authors are strongly encouraged to use XML declarations in
all their
documents. Such a declaration is required when the character
encoding of
the document is other than the default UTF-8 or UTF-16 and no
encoding was
determined by a higher-level protocol."
IE only pays attention to the DOCTYPE if it is the very first
thing in the
page. Put anything before the doctype and IE will drop to
quirks mode.
That's just an IE bug that you'll have to live with.
Gary

No Design View?

I hope I'm mistaken in understanding that design view has been removed from flash builder 4.7. That was one of the coolest things about flash builder, I think removing it had to be one of the dumbest ideas anybody's ever had.
Please tell me how mistaken and there is a way to enable this feature,

There is no other way to see what you are doing unless you publish a swf.
IMHO
For simple projects its not a big deal but if you work on large enterprise projects ( one of my projects has over 30,000 lines of code ) with complex dynamic designs that need to be compiled and uploaded to a server because of variables that need to be passed in and other remoting calls that need to communicate with services using session data it is a real drag. It can take several minutes to compile and upload just to test if I need to move something even as little as 1px in one direction or another.
And it is way faster to drag and drop components and set the properties in design view rather than typing everything in manually. Thats where the "Rapidly Deploy" was a big plus.
When you have several projects going on with multiple deadlines you need every second you can get.
Once the initial layouts are established DV is not used much except for some small changes that are called for.
Using FB4.6 and FB4.7 to work a project is just lame but I guess I have little choice if I wish to stay current.
Some may say "Migrate to HTML5,CSS3,JavaScript"
I would say "There are no HTML5 equivalents for these key features we use".
1) Encoding HD quality Video/Audio from the browser.
2) A way to stream that video to an RTMP server (AMS and/or Wowza) from the browser to record and send live streams.
3) Use RemoteShared Objects and other complex SSAS functionality that has various functions that also connect to external gateway services.
4) Use LocalConnections to commumicate with AIR apps our project launch.
There are more but these are the minimum I need to address to even think about migrating.
Adobe is leaving us high and dry with an inferior product compared to previous versions.
Nice job weenies. Your "Too Bad For You" attitude will bite you.

Why Design View will be removed?

My question is that: why Design View will be removed from Flash Builder?
Will it be substituted by another way of doing the things visually? Will adobe provide other visual tool to design applications? Disabling Design view and extinguing Catalyst seams that we will not any more visual tools. Is there any other plans for visual tools or Flash Designers or they will have to do the things in code-only?
Thanks

Whaaaa...... XML was designed to me machine read not human read! How can any sane person prefer to work purely in a horribly confusing environment when you can put your widgets directly onto a form and go from there? If Microsoft told all developers to develop their apps in pure code and run them to see, Visual Studio would not exist! For an example, you only went inside the VB6 .frm files when somthing went very badly wrong, as the display layout was totally seperate from the language code, and the base of Rapid Application Development was that the IDE did the heavy lifting of setting up the GUI and eased your code into it. That family of development tools more or less dominated desktop development from 1996 till today... But only on Windows. And so you all want to go back on that and do things the hard and slow way? I'm gutted.
You have the perfect environment for a multi-platform IDE, a proven language, a multiplatform system even mobile support in a one stop shop for Rapid Application Development that can be deployed to anything. I do not want to play with your MXML. I find it messy, clunky and slow. I do not want to mess with hand crafting each and every component... I can do it without even having to think about it with a GUI builder that is supposed to help me. If I wanted to hack around manually in source files and fiddle with declarations, correct typecase, naming and options for hours to get a script to run, I can do that already and it's called HTML+AJAX... Flex Builder was supposed to be a step forwards. Why throw it into reverse?
I was seriously thinking about using Flex and Air as a VB6 and C# replacement but this is a deal breaker...Well, this version should be supported for 5 years by Adobe according to their roadmap so in time I just hope that now the builder evolves for the better under Apache in that time and not get managed by people who prefer coding in VIM and ignore everyone else
Daniel

Design view not the same as live view

My design view is totally different the IE view or live view
in cs4, I read a thread that you have to basically live with it?
I hope this is not true, can anybody confirm?
Thx
Brad

You can see the IE result at http://www.spaline.ca/dreamweaver/
and I ahve attached a screen shot in a pdf.
I do not know what else i can say at this point
Thx
Brad

Is Photoshop CS6 different from CS5?

I recently went back to school to expand my career skills and the next class in line for me, is Photoshop. I’m trying to find out if I’m OK with CS5 or if I need to upgrade to CS6. As I just mentioned, I currently have CS5. For a couple classes I completed this year (Flash and Dreamweaver), I was able to use CS5 without any issue, limitations, or instances of “Yeah that can be done, but only on CS6.” I also did not have instances in the class lessons of “You can do this, but not if you’re on CS5.” However, from what I heard/read, Photoshop seems to have had the most significant changes in the CS6 update.
Here are my questions:
Please, from a technical perspective only, do I need to upgrade to CS6? Will being on CS5 on my home computer put me at a disadvantage in class when I'm being taught via CS6? Is Photoshop CS6 significantly different from CS5 where if being taught via CS6, I would be lost or very limited on CS5? When you upgraded to CS6 did you feel like you were learning a new program, or was it the same as CS5, just with a few new “nice to have” features?
Again, please provide information from a technical perspective only. If the decision to spend $2000 for CS6, was based on preference, I would have had CS6 a long time ago. Also, please don’t recommend CC because I’m not ready to upgrade to subscription based software yet.
Thanks!

Have you tried running the trial version of CS6 for 30 days to get a feel for the software and perhaps answer for yourself the many questions you obviously have?
Try http://helpx.adobe.com/x-productkb/policy-pricing/cs6-product-downloads.html
Or http://prodesigntools.com/adobe-cs6-direct-download-links.html

Design view and browser view in DW are different than when I view from local folder

I'm brand new to Dreamweaver CS5.5 and here is my problem:
I've made an html page in dreamweaver with a banner, with an additional graphic and some text on top of the banner. It displays just fine in every browser when I view from the local folder, but when I open DW and view, it displays incorrectly in all three design, live and browser views within DW. If I make changes to the css file until it views correctly in design view, it no longer displays correctly from the local folder and it still doesn't view correctly in live or browser view within DW. If what I'm doing isnt going to display accurately in any of the views provided by Dreamweaver as compared to the live server, whats the point in having this software? I could just keep building webpages in notepad and uploading with CoreFTP.
Any suggestions? Is it some setting that I dont know about that I need to change within DW? Please help.

align="center" is deprecated (obsolete) code in XHTML & HTML5 doc types. Instead of styling markup with HTML, you should be using CSS.
CSS
.center {text-align:center}
HTML
<p class="center">some centered text here</p>
With respect to break tags, in XHTML doc types the correct syntax is <br /> not <br>. However your usage of line breaks is inconsistent with good symantic markup. Use headings <h1> <h2> <h3> <h4> for important keywords. Use <p> for descriptive paragraphs. Use <ul> <li> or <ol> <li> for lists. Line breaks should be used minimally if ever.
XHTML doc types require all tags to be lowercase. Uppercase tags will throw errors.
Your design is too rigid. When text size is increased in browsers, your content is unreadable. See screenshot.
SOLUTIONS:
1) DO NOT USE POSITION ABSOLUTE. You don't need it. Absolute positioning removes content from the normal document flow resulting in a jumbled mess. Use default CSS positioning (none) with margins, padding & floats to align elements.
2) Remove HEIGHT values from all CSS containers. Height limits a container's capacity to hold more content when needed. Container height should always be determined by the amount of content it holds; not explicit values. If required to reveal a background image, for example, use CSS min-height instead of height.
CSS Box Model
http://www.w3schools.com/css/css_boxmodel.asp
CSS Floats
http://www.w3schools.com/cssref/pr_class_float.asp
CSS min-height
http://www.w3schools.com/cssref/pr_dim_min-height.asp
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
http://twitter.com/altweb
http://alt-web.blogspot.com/

Font in Design View different from font in Live View and browser preview

My external style sheet has the body set for a sans-serif font and there is nothing to contradict it in the HTML documents. But while I get sans-serif in the Design View (as you would expect), I get a serif font in Live View and Browser Preview, not to mention on the Web itself.
How is this possible (and what should I do about it)?
--Paul

Murray and David: it worked! It is a rare and joyous experience to have a straightforward solution to the sorts of problems I come up with (including other realms). But I have to say that with HTML and CSS (and hence with Dreamweaver), solutions to difficulties have seemed within easier reach than in other parts of the computer world.
By the way, I wanted to choose "correct answer" for both your posts, but after making the first click it was no longer available for the remaining post--so I typed "helpful" even though that one was correct too.
Thanks again.
--Paul

Design view differs from browser view

When viewing in Design view my code correctly shows 2
overlapping rectangles. In browser view it shows two smaller
rectangles that do not overlap. I am using DW MX 2004. I have
attached small sample code.
Thanks,
Alexariel

DMX2004's Design view is not a browser, and can only
approximate (poorly)
how a page will look. The browser is always right. For
example, DMX2004 is
insensitive to the CSS error here -
div {width:250px; height:100;px; position:absolute; }
(note the ';' between '100' and 'px')
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"Alexariel" <[email protected]> wrote in
message
news:gqh83o$kld$[email protected]..
> When viewing in Design view my code correctly shows 2
overlapping
> rectangles.
> In browser view it shows two smaller rectangles that do
not overlap. I am
> using
> DW MX 2004. I have attached small sample code.
> Thanks,
> Alexariel
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN"
> "
http://www.w3.org/TR/html4/loose.dtd">
> <html>
> <head>
> <title>Untitled Document</title>
> <meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1">
> <style type="text/css">
> body {margin: 0px; padding: 0px;}
> div {width:250px; height:100;px; position:absolute; }
> div.one {background-color:#FF0000; left: 0px; top: 0px;
> div.two {background-color:#00FF00;left: 75px; top:
25px;}
> </style>
> </head>
> <body>
> <div class="one">one</div>
> <div class="two">two</div>
> </body>
> </html>
>

Background in live view different from design view

Why when I am looking at my page in design view it shows up black like I want it to, but when I go to live view or view it on the internet it shows up like the template color that it was when started?

Without the code, it's pretty tough to say what might be happening.
One thing to look at would be the order of you css, including the links to external .css files in the <head> of the page.
If you have two like selectors, for example, two versions of: body {background-color:some color here;}, the one that comes last in the stylesheet links, embedded css, or in the html itself (inline css) will be the one that's used by the browser.

Live view different from design view

Hi folks,
Does anyone know why, in dreamweaver, there is a difference between the site design in Design View and what you see in live view; and how should oneapproach this difference?
Thanks.

Design View was coded a LONG time ago and Adobe hasn't really changed it much. It is very useful for my workflow, which is to work in Split view and jump back and forth between the Design view pane and the Code View pane. I know right off the bat that I won't see everything. Design View will never show me the newer CSS3 attributes, like shadow, gradients and so on. But it gives me a "rough" analog to work with while I'm doing general layout. Things like, "Am I breaking up the text enough to keep people on my web page?" "Do I have this typeface too small?" "Is the picture I just put in there positioned correctly?"
Also, be forewarned, "Live" view is Webkit (an Open Source browser) so it will accurately portray Google's Chrome and Apple's Safari. It will not accurately show issues with Firefox and Internet Exploiter. So, before you launch your website, do a check in all of the major browsers.

Design view is significantly different from output in Robohelp 10

Similar Messages

Maybe you are looking for