Re-naming Styles

I'm working in Keynote 6.5 and want to re-name a style based on "free form". I duplicated the style as "Free Form 2" and when I try to rename, using the dropdown next to the style and typing "Survey Question", the name reverts back to "Free Form 2".
Suggestions?

You'll have better luck with this particular question if you post it to the Phtoshop Elements forum: http://forums.adobe.com/community/photoshop_elements

Similar Messages

Name of the predefined style in the template removed in the output-RTF

When using predefined named styles in an RTF-input-template, these get removed from the resulting output-document.
* Create a BI-Publisher -project and use an rtf-file with a predefined style (you can define one on the fly by changing the default style and call it eg. "MyStyle")
* Type in some text in the template-rtf marking it with "MyStyle"-style
* Save your template, add a dummy dataset and then view it as rtf-output
* The Name of the predefined style is not in the style-list of the output-rtf anymore.
Basically, BI-Publisher seems to remove the names of the styles in the list of the rtf and thus making it impossible to work consistently with styles afterwards for people wanting to modify the resulting rtf using a in-house-style .
Does anyone know a workaround for this ?
Thanks,
Peter

Hi,
According to your requirement there is no such standard SAP report.
Develop a custom Z-report using LDB PNP in Tcode SE38.
Hope this helps.
Thanks,
Sarika.

Can I use stylesheets to create multiple button styles?

I am trying to create a custom look-and-feel within UIX to get it as close as possible to
our existing application's look-and-feel.
As part of this, I customized the UIX button by overriding the following named style:
ButtonServerText
and also by providing my own icons for:
buttonStart
buttonEnd
buttonTopBackground
buttonBottomBackground
The good news is that I was able to get the button component to look exactly like our existing
application buttons.
The bad news is that we have different types of buttons in our application
for different purposes. (i.e. the image used for the button can be completely different based on the context e.g.
yellow button for important actions and light-blue buttons for secondary actions)
It seems like there is no way in which I can use this stylesheet mechanism to create different types of buttons
and use them within my application. (sometimes different types of buttons can appear on the same page)
Please let me know if there is a way.
This is in fact a general question regarding overriding a stylesheet for customizing look-and-feel.
Lets say I customize the "contentContainer" component using the stylesheet. This change would then be global.
But I do want to have different types of contentContainers in the application. I would be forced to create my own custom
UIX elements similar to contentContainer and write my own renderers.
(I know contentContainer does have the light, medium and dark styles. I used this just as an example.)
Please let me know what my options are.
Thanks,
Jayesh Kapoor

Hi Jayesh -
The good news is that I was able to get the button
component to look exactly like our existing
application buttons.Cool - I'm glad to hear you were able to get this working!
The bad news is that we have different types of
buttons in our applicationRight. This is a fundamental limitation of our look and feel customization functionality - we only support global customizations, not instance-specific customizations. I agree that there are many cases where instance-level customization would be useful, but this just instance supported yet.
The only solution that I can think of for your button dilemma would be to use static images. It's pretty easy to wire up an image to behave like a button - just embed the image in a link and use <fireAction> as the link's primaryClientAction.
Obviously, the downside of this approach is that you need to create the button images manually - which also isn't ideal if you are planning to translate your applications. One possible solution here might be to use UIX to pre-generate your button images. The idea would be to create custom LAFs for each style of button, then create a UIX page for each button style, including <button> instances for each translated value. Then, you could configure UIX to run in the desired look and feel, hit the corresponding page, and UIX will generate the required buttons into your image cache. Again, not ideal, but this might be easier than creating the buttons by hand.
This is in fact a general question regarding
overriding a stylesheet for customizing
look-and-feel.
Lets say I customize the "contentContainer" component
using the stylesheet. This change would then be
global.
But I do want to have different types of
contentContainers in the application. I would be
forced to create my own custom
UIX elements similar to contentContainer and write my
own renderers.Right - this is a generic problem. But for some components, like content containers, an easier solution might be to leverage UIX's templating mechanism. Remember, you can embed arbitrary HTML contents in a UIX page/template by setting the namespace to "http://www.w3.org/TR/REC-html40". You can then reference these templates from your other UIX contents as if they were in fact UIX components. I'd recommend that you explore UIX's template support to see if this will meet your needs.
Andy

Select text based on format (free form style text)

As suggested by Apple, I'm trying to create my first ePub using Pages as opposed to inDesign.
I only have a PDF as a source file and don't want to re-type all the text.
When I copy the text from the PDF and paste to Pages, the text comes in with the 'free form' style applied no matter what options I select during copy and paste.
In order to produce an ePub, I need to set styles for the text. This is quite tedious.
Is there any way to select text based on the way it is formatted when styles are not applied to the text?

Here is a script which may be useful if your problem surface again.
--{code}
--[SCRIPT words_attributes_to_Style]
Enregistrer le script en tant que Script : words_attributes_to_Style.scpt
déplacer le fichier ainsi créé dans le dossier
<VolumeDeDémarrage>:Users:<votreCompte>:Library:Scripts:Applications:Pages:
Il vous faudra peut-être créer le dossier Pages et peut-être même le dossier Applications.
Ouvrir un document Pages contenant des mots soulignés
Aller au menu Scripts , choisir Pages puis choisir “words_attributes_to_Style”
Le script appliquera :
le style "Souligné" aux mots soulignés
le style "Accentuation" aux mots en gras
le style "Italic" (si vous l'avez créé) aux mots en italique.
--=====
L’aide du Finder explique:
L’Utilitaire AppleScript permet d’activer le Menu des scripts :
Ouvrez l’Utilitaire AppleScript situé dans le dossier Applications/AppleScript.
Cochez la case “Afficher le menu des scripts dans la barre de menus”.
Sous 10.6.x,
aller dans le panneau “Général” du dialogue Préférences de l’Éditeur Applescript
puis cocher la case “Afficher le menu des scripts dans la barre des menus”.
--=====
Save the script as a Script: words_attributes_to_Style.scpt
Move the newly created file into the folder:
<startup Volume>:Users:<yourAccount>:Library:Scripts:Applications:Pages:
Maybe you would have to create the folder Pages and even the folder Applications by yourself.
Select a Pages document embedding underlined words
Go to the Scripts Menu, choose Pages, then choose “words_attributes_to_Style”
The script will apply :
the named style "Underlined" to the underlined words
the named style "Emphasis" to bolded words
the named style "Italic" (assuming that you defined it) to italicized words.
--=====
The Finder’s Help explains:
To make the Script menu appear:
Open the AppleScript utility located in Applications/AppleScript.
Select the “Show Script Menu in menu bar” checkbox.
Under 10.6.x,
go to the General panel of AppleScript Editor’s Preferences dialog box
and check the “Show Script menu in menu bar” option.
--=====
Yvan KOENIG (VALLAURIS, France)
2011/11/13
2011/11/13 enhanced by Nigel Garvey in : http://macscripter.net/viewtopic.php?pid=145883#p145883
--=====
on run
          set Underlined_loc to my getLocalizedStyleName("Pages", "Blank.template", "STYLE_Underline")
          set Emphasis_loc to my getLocalizedStyleName("Pages", "Blank.template", "STYLE_Emphasis")
          tell application "Pages" to tell document 1
                    set character style of words whose underline type is single underline or underline type is double underline to character style Underlined_loc
                    set character style of words whose bold is true to character style Emphasis_loc
Assuming that you defined your own Italic style named "Italic", you may use : *)
                    try
                              set character style of words whose italic is true to character style "Italic"
                    end try
          end tell
end run
--=====
Example
set Heading8_loc to my getLocalizedStyleName("Pages", "STYLE_Heading 8")
Requires :
getLocalizedName()
on getLocalizedStyleName(theApp, tName, x)
activate application theApp
          tell application "System Events"
                    (application file of application process theApp as text) & "Contents:Resources:Templates:" & tName & ":Contents:Resources:"
                    return my getLocalizedName(theApp, x, result)
          end tell
end getLocalizedStyleName
--=====
on getLocalizedName(a, x, f)
          tell application a to return localized string x from table "Localizable" in bundle file f
end getLocalizedName
--=====
List of default styles embedded in the Blank template :
"STYLE_Body" = "Corps";
"STYLE_Body Bullet" = "Puce du corps de texte";
"STYLE_Bullet" = "Puce";
"STYLE_Caption" = "Légende";
"STYLE_Emphasis" = "Accentuation";
"STYLE_Footnote Text" = "Texte de note de bas de page";
"STYLE_Free Form" = "Format libre";
"STYLE_Harvard" = "Harvard";
"STYLE_Header & Footer" = "En-tête et bas de page";
"STYLE_Heading 1" = "Sous-section 1";
"STYLE_Heading 2" = "Sous-section 2";
"STYLE_Heading 3" = "Sous-section 3";
"STYLE_Heading 4" = "Sous-section 4";
"STYLE_Heading 5" = "Sous-section 5";
"STYLE_Heading 6" = "Sous-section 6";
"STYLE_Heading 7" = "Sous-section 7";
"STYLE_Heading 8" = "Sous-section 8";
"STYLE_Heading 9" = "Sous-section 9";
"STYLE_Legal" = "Légal";
"STYLE_None" = "Aucun";
"STYLE_Normal" = "Normal";
"STYLE_Normal 22" = "Normal 22";
"STYLE_Normal 4" = "Normal 4";
"STYLE_Normal 8" = "Normal 8";
"STYLE_Numbered List" = "Liste numérotée";
"STYLE_Series_0" = "Series_0";
"STYLE_Series_1" = "Series_1";
"STYLE_Series_2" = "Series_2";
"STYLE_Series_3" = "Series_3";
"STYLE_Series_4" = "Series_4";
"STYLE_Series_5" = "Series_5";
"STYLE_Strikethrough" = "Barré";
"STYLE_TOC" = "Table des matières";
"STYLE_TOC Heading 1" = "Sous-section 1 de table des matières";
"STYLE_TOC Heading 2" = "Sous-section 2 de table des matières";
"STYLE_TOC Heading 3" = "Sous-section 3 de table des matières";
"STYLE_TOC Heading 4" = "Sous-section 4 de table des matières";
"STYLE_Title" = "Titre";
"STYLE_Underline" = "Souligné";
"STYLE_[Null]" = "[Nul]";
You may use more sophisticated custom styles embedding several properties:
baseline shift (real) : Raise or lower the target text.
bold (boolean) : Whether the font style is bold.
capitalization type (all caps/normal capitalization/small caps) : Whether a capitalization style is applied.
character background color (color) : The color of the character's background.
color (color) : The color of the font.
font name (text) : The name of the font.
font size (real) : The size of the font.
italic (boolean) : Whether the font style is italic.
ligatures (all ligatures/default ligatures/none) : Remove ligatures from the target text if the document is set to use ligatures.
name (text) : The name of the style.
outline (boolean) : Whether the font style is outline.
shadow (boolean) : Whether the text box content casts a shadow or not.
shadow angle (real) : The directional angle, in degrees, that the shadow is cast.
shadow blur (integer) : The relative amount of blur of images seen through the shadow.
shadow color (color) : The color of the shadow.
shadow offset (real) : The offset from the text box content that the shadow extends to.
shadow opacity (real) : The amount of opacity for the shadow, in percent.
strikethrough color (color) : The color of the strikethrough line(s).
strikethrough type (double strikethrough/none/single strikethrough) : Whether one or more lines are drawn through the characters.
subscript (boolean) : Decrease the font size and lower the baseline of the text.
superscript (boolean) : Decrease the font size and raise the baseline of the text.
tracking (real) : The space between text characters, in percent.
underline color (color) : The color of the underline(s).
underline type (double underline/none/single underline) : Whether the font style is underline.
--[/SCRIPT]
--{code}
Yvan KOENIG (VALLAURIS, France) lundi 2 janvier 2012
iMac 21”5, i7, 2.8 GHz, 12 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.2
My iDisk is : http://public.me.com/koenigyvan
Please : Search for questions similar to your own before submitting them to the community
For iWork's applications dedicated to iOS, go to :
https://discussions.apple.com/community/app_store/iwork_for_ios

Help with problem specifying text properties (style & antiAliasMethod)

I would be very grateful if someone could help me figure out what I am doing wrong in specifying certain text properties, namely style and antiAliasMethod. I have tried many different things and consulted the JavaScript Reference Guide, Tools Guide and PS CS4 Scripting Guide, as well as several example scripts, but I can't seem to find the information needed.
The snippet of code below adds a text layer to a document and places text on it; What I want is white Arial bold 10 point text with no antialiasing (this would appear as "none" in the PS CS4 text tool dialog). This code does everything except get the bold property and the antialiasing = none property. Instead, what this code produces is white Arial normal (not bold) crisp (not none) text,
My attempt to get no antialiasing instead of "crisp" causes an execution error, so that line is commented out below. The line setting style to "BOLD" does not create an execution error, but it doesn't give me bold, either (instead I get normal).
I am certain these errors mean I do not understand the correct way to express the code to set these properties. Can someone set me straight about how to do this?
Thanks.
        // Create a new text layer at the top of the document
        var myLayerRef = newDocRef.artLayers.add();
        myLayerRef.kind = LayerKind.TEXT;
        myLayerRef.name = "Test";
        var myTextRef = myLayerRef.textItem;
        // Set the text color, font, size, etc.
        var textColor = new SolidColor;
        textColor.rgb.red = 255;
        textColor.rgb.green = 255;
        textColor.rgb.blue = 255;
        myTextRef.color = textColor;
        myTextRef.font = "ArialMT";
        myTextRef.style = "BOLD";
//        myTextRef.antiAliasMethod = "NONE";
        myTextRef.size = 10;
        // Set the text position, blend mode and opacity
        var tx = 10;
        var ty = 50;
        myTextRef.position = new Array(tx,ty);
        myLayerRef.blendMode = BlendMode.NORMAL;
        myLayerRef.opacity = 100;
        // Insert the text
        myTextRef.contents = "Hello World";

Update:
I discovered how to fix both problems myself.
The antialiasing was fixed by statement: myTextRef.antiAliasMethod = AntiAlias.NONE;
The bold problem was fixed by changing the font name to "Arial-BoldMT" and deleting the statement which attempted to set the style to "BOLD".
Thanks for your interest. No further help is needed on this issue.

Changes to [No Paragraph Style] causing unwanted style overrides

Hi fellow InDesigners
I'm using InDesign CS6. I'm working with long documents that were originally created in previous versions (CS4 and possibly earlier). My standard workflow for these jobs is to do the bulk of the text formatting in a newly created, bare-bones, single column document. First, I load the paragraph and character styles from the template, and when I'm done I copy and paste the formatted text back into the template for final layout and typesetting. This used to work fine in CS4, but in CS6, all my paragraphs show the plus sign in the Paragraph Styles panel, indicating that they have been overridden. They should be identical, since I imported the styles from one file to the other. The overrides include drop cap alignment, and even more obscure things like 'IdeoSpaceBehavior' and 'Diacritic Positioning'.
It seems likely to me that this problem is due to Adobe having changed the definition of the mysteriously ubiquitous '[No Paragraph Style]' style between versions. The template file has carried over the definition from CS4, but the newly created working files have the new definition, and since [No Paragraph Style] is not included when importing styles from one document to another, the inconsistency remains. Copying and pasting text with no overrides in one document, shows overrides in the other.
So the simplest solution I can think of, would be to change the [No Paragraph Style] in the template to match the definition of new CS6 documents. Is this even possible? My Googling thus far suggests that [No Paragraph Style] is pretty much untouchable.
Is there nothing for it but to create the template files again as new documents in CS6?

No worries Michael. Yes, I vaguely remember the change too.
My understanding is, [No Paragraph Style] is very much a style—a paradoxically named style to be sure, but a style nonetheless. Check out the [Basic Paragraph] style definition by double clicking on it in the Paragraph Styles panel. It's style definition is: '[No Paragraph Style] + next: [Same style]'. That's it. Minion Pro 12 point, with auto leading—and every other conceivable paragraph attribute—all handled by [No Paragraph Style]. Adobe needed some defaults, and that's what [No Paragraph Style] is—just a default style. You can never escape it either, since every style, no matter what it's based on, has [No Paragraph Style] as its most senior ancestor.
So that's essentially my problem. Adobe has, in their wisdom, changed the [No Paragraph Style] style between versions, so that a document originally created in an earlier version and a document created in CS6 have different [No Paragraph Style] settings. I'm pretty confident this is the cause of my problems.
Lots of my paragraph styles inherit from other styles. Why would I not want that? My custom 'Paragraph' style has lots of other styles based on it—from typesetting variations, to quotes, lists, etc. But the 'Paragraph' style itself is based on [No Paragraph Style]. As I said, you can't really escape [No Paragraph Style].

How to Make a "fonts.css" style sheet

Hi, I have a wordpress blog with a stylesheet named “style.css”. I want to change the fonts in the style sheet and so I want to create a separate style sheet named “fonts.css"
I could just duplicate the ”style.css” page and then rename it “fonts.css” but I believe I read somewhere it is better to create a new style sheet named “fonts.css” and then add my font styles to that. Doens anyone know of a tutorial or how I make the new style sheet and add my fonts?

I only typically use two stylesheets on any given site, layout.css and styles.css. One is for the overall layout/positioning info of the site and the other is the style information which would include fonts, colors, shadows, transitions, etc.
If it is better in your mind and for your workflow to create a third stylesheet just for the font values, go for it. To me, fonts are just another style element though, so they stay in my styles.css file.
There's really no right or wrong to doing it either way. Just make sure you create another link in the head section of your site to the new file if you create fonts.css.
Thanks jon,
Yes I agree, I could just change the fonts in “style.css” and then have less style sheets, but the themes developer told me to create a new style sheet named “fonts.css” only because the theme is updated regularly and uploading a new theme will write over the file named “style.css” and then your fonts will default to their original fonts.
I don't see anything wrong with that approach. Just remember that if you have both styesheets linked to the same page then the page will get it's css styles from the last linked stylesheet.
So for instance if you have:
body {
font-size: 14px ;
in the style.css
and
body {
font-size: 12px ;
in the fonts.css
and the last linked stylesheet was styles.css the page would display 14px text.
So you just need to get them in the right order IF you have more than one styleshet linked to a page.
Thanks Osgood,
Yes that was my other question. So in my uploaded CSS folder I have the original “style.css” file and now my new “fonts.css” file. “style.css” is above the “fonts.css” file and both contain the same information except the file “fonts.css’ has been changed to use different fonts.
So if I understand you correctly I need to either move the file “fonts.css" above the file “style.css” or delete “style .css” from the CSS folder so the file “fonts.css” will take precedence. Is this correct?
Also, I needed to open style.php and edit the code to include “fonts.css” which I did.
I opened "style.php" and then added the code in "red" then uploaded it to the (CSS) folder on the server.
<?php
header( "Content-type: text/css" );
$files = array();
$files[] = 'style.css';
$files[] = 'responsive.css';
$files[] = 'fonts.css';
foreach($files as $file) :
    $content = @file_get_contents( $file );
    echo minify( $content );
endforeach;
function minify( $code ) {
          $code = preg_replace( '#\s+#', ' ', $code );
          $code = preg_replace( '#/\*.*?\*/#s', '', $code );
          $code = str_replace( '; ', ';', $code );
          $code = str_replace( ': ', ':', $code );
          $code = str_replace( ' {', '{', $code );
          $code = str_replace( '{ ', '{', $code );
          $code = str_replace( ', ', ',', $code );
          $code = str_replace( '} ', '}', $code );
          $code = str_replace( ';}', '}', $code );
          return trim( $code );
?>
After doing all of this I still didn’t see any changes to my fonts so I must have done something wrong.
Any ideas?

Mysterious FM- RH style mapping override with span tag

I have been working in a super clean FM and RH project that is has one to one mappings for all my styles in the FM to same named styles in RH, just to be sure I do not mess up. Still, though, I seem to get a mystery mapping. For my bullets and lists, RH is adding a span tag with font set to Times Roman. I cannot find *any* css that has Times Roman. I've checked things like my character tags, my cross reference tags, etc and cannot find a correlation. Where would this be added if it's not in my FM Format definitions and not in my RH Style definitions. I tried reimporting the book to see if it needed a tickle of the project mappings template but that didn't help.
I'm attaching some images in hopes someone has ideas. The example does not appear to be times roman in Design view, but in more complex topics it's pretty obvious.
I have so many hacks for single sourcing now, about ready to give up.
Got help?
FM 10
RH 11

Thanks for the fast reply Arnis,
I did not even notice that the span tag ended on the spaces, so it can't be what's causing the odd previews I'm seeing. So it seems my original question is not well thought out, so I'm going to retest with some other style changes.
Still, though I'm wanting to follow up on getting rid of the Times tag anyway. The bullets are always defined as Verdana. Bullet is set to use "Default Font" while BulletLevel2 uses "Bold" (the char def for Bold is also Verdana). Is there some place I have to map "tabs" to not be Times? I dont think it's the Default Font issue because bullet 2 uses Bold.
Here are some screenshots.

Styles and "space before" quandry

I will assume that most readers are familiar with PowerPoint and are aware that for your average bulleted slide master you can change the space before or after on a per-level basis without using named styles. I want to use spacing in Keynote but am seeing annoyances.
Method 1) If I use all the same style name as in the default themes, then I end up with that asterisk after all but one style, because there is only one unmodified "Body" style and the rest are considered overrides.
Method 2) If I use different styles, I have to reach for the mouse more.
Am I missing a technique to effect this, without overrides and with (I assume) using only one style?

Thanks but that's not what I meant. I can use the spacing just fine. The issue is with the outcome of the two methods. #1 introduces overrides (and, by the way, reassigning or clearing them does not always work), and #2 requires an assignment to many paragraphs.

CSS Questions :: Renaming Class Styles & Replacing Styles Globally

1) Renaming Class Styles
I have a large website that I redesigned over a year ago and now manage. I've been doing some housekeeping and attempting to rename some of the class styles I've applied to different parts of each page.
Problem: When I change the name of a class style, the style no longer is applied to the text. I've tried this in both GoLive CS2 (8.01) and Dreamweaver CS3. It's the same with both. They both allow you to change the name, but then the text loses the connection to the class style.
How can I rename the property (or style rule) without losing the connection to the text it is applied to? To go through and have to reassign the newly named styles to each section of each page would be an enormous undertaking.
2) Replacing Styles Globally
Is there an easy way to delete a style and chose a new one to take it's place globally?
Thank you for any help you can offer!
Linda

Hi Nate,
Thanks for the suggestions!
> In CS2, The CSS tab on the left side of the site window is handy for that. For instance, if you want to change very instance of a class to a different name, find it in the classes list and rename from there, which should update any pages using the class, and update its name in any external CSS files. Really useful for global changes, but definitely one of those things worth making a back-up of the whole site first.
For some reason when I do this it breaks the formatting style.
> If you want to change any references to one class to references to another, go to the same place and just change the class name to the other class name (so, you'd temporarily have 2 items in the list with the same name). Then, if you refresh view, you'll see they've really been consolidated into references to the same class. If that makes sense.
This does make sense.
I'm still experimenting. I may need to resume this in the morning. I'll let you know how it goes.
Linda

Setting overall styles in DW CC fluid grid layout

I have just watched this tutorial on Adobe TV about fluid grid layout in DW CC: http://tv.adobe.com/watch/learn-dreamweaver-cc/create-fluid-responsive-web-pages-in-dreamw eaver/community#community
This is a great start, but I need to know more!
Where do I set the body text, background, background tile and drop shadows, plus the H1 to H4 and a link attributes? Is it in the <div class="gridContainer clearfix"> or do I do i somewhere else? I saw another video on fluid grid layouts that briefly mentioned using a separate css stylesheet for fonts as 'it was better' but no more detail was given.
Also where can I change the a link attributes in a div if I want different a link styles in that div to the rest of the website? I can't see an area in the properties panel where I can change a link behaviour.
Thanks so much.

Generally, when you are building a website, you want your styles in a separate style sheet (a CSS document). With respect to the tutorial, he details that he is creating a CSS document he calls "style.css" and saves it in the local root folder. I usually place my style sheets in a /css/ folder but, for the purpose of his demonstration, placing it in the root of the defined site in Dreamweaver is just fine.
Now, once he has saved his initial HTML file, Dreamweaver CSS tells him that his document needs two more documents that Dreamweaver will pull in from the Dreamweaver library. One is a JavaScript document, respond.min.js, that handles figuring out what to do on a cell phone, versus a tablet, versus a desktop and the other is "boilerplate.css" that handles fluid grids. If you look at the HTML document, you'll see links to these three files in the root of the defined site.
Now, you'll notice when he's creating the header (id="top") and doing the centering of the logo image, he tells you to select the corect stylesheet, namely "style,css."
Here's the essential problem with the way he's showing you how to do this. You're not actually working in the code. He's demonstrating all of these panels and entry areas for Adobe's Dreamweaver that actually hide the code from you. In fact, he encourages this by switching you from "Split" view to Design (only) view for centering the logo image.
I think this is disingenuous. Everyone here in this forum will tell you, "You need to learn HTML and CSS." And they're absolutely correct. Dreamweaver's fluid grid layout gizmo may not ever define body text, background, background tile, drop shadows or your "h" tags at all. Or, they may be defined, but you are never taken to the code that shows you those definitions.
Open the CSS document that is the basis of the tutorial, which is style.css. In that document, you should see a "body" definition like this:
body {
          background-color: #FFFFFF;
color: #000;
          font-family: "Lucida Sans Unicode", "Lucida Grande", sans-serif;
          margin: 0px 0px 30px 0px;
In English, this means your background color is white and your text color is black. You're using Lucida Sans Unicode or Lucida Grande as your typeface, defaulting to sans-serif if those are not available. You have a 30-pixel bottom margin, no margins for either top or sides.
If you need to create a background color or tile, you would change the background-color attribute or, if you are tiling a background, you would place the following in the body definition in CSS:
background-image: url("images/tile.jpg");
This assumes you have a file in your /images/ folder in the root of your defined site called tile.jpg. Since you did not include a background-repeat command, your tile will repeat x and y.
And if you don't want a tiled background in your body and do want it in a different div, you simply look for the name of the div in your CSS and put it there.
As to your heading styles, you may find them all ready defined in your CSS document. You may redefine them or create new header styles.
This should get you started. The key is to open the CSS document, "style.css" and see what's there.
-Mark

Using Custom Styles for Levels in Outline View

How do you associate different levels in the Outline View with custom styles? By default they are associated with Heading 1, Heading 2, etc.
Thanks!
Bobby

Styles apparently have a hidden "my associated outline level is #" property. However you have to start with a style that has this hidden property set as there seems to be +no way+ to access or change this property yourself (This is unusually poor interface design from Apple - they've traditionally been better than that.)
You essentially need to use only the names "Heading 1", "Heading 2", etc, for styles associated with outline levels, and you can't create these styles yourself. You can change the formating of these styles in the normal way: Start with a paragraph formatted using "Heading #", changing the outline level to the appropriate one, manually change the text to look the way you want, select the new formatted outline level paragraph, and do "redefine style with selection". You can't just apply another style, it over-writes the hidden outline level # property with its own, usually "body", making it really difficult to add an outline to an existing document - you have to re-create all the styles.
You can have mutliple styles that apply at the same level by doing the same as above, but instead of redefining the appropriate "level #" heading do "Create new paragraph style from selection". (You have to name it something other than "Heading #").
Applying this style gives a paragraph the associated outline level as well. Unfortunately, if you promote or demote an "outline level #" tagged paragraph, its hidden "outline level #" property is changed and the new style will always become the "Heading #" style associated with the hidden "outline level #" property. There is no memory of where it came from, of course, so if returned to its original outline level, it looses the "custom named style". There is no way to tell Pages that it should choose your custom named style by default instead of the "Header #" style for a given outline level. I can see no reason Pages couldn't do this too.
I have a complicated document that was written with consistent styles for headers, and now want to use the outline feature. I have to literally recreate all the heading styles from scratch. I can then do "select all instances" for my former styles and then click on the "Heading #" style reformatted as a copy, changing them to exactly what they were before, except with the new mandated name and the one magic hidden property changed.
There is also some weird behavior used to hide unused "Heading #" styles: You can see evidence of this if you repeatedly demote an outline paragraph; the extra heading styles automatically appear in the style draw. Then if you then repeatedly promote the same outline paragraph, these intermediate styles go away. How that works without loosing user-defined styles with the same name I have no idea.
Message was edited by: Stuart R. Jefferys
Message was edited by: Stuart R. Jefferys

Can I include my own style definition in a .xss file for a custom laf?

I am trying to create a custom look-and-feel within UIX to get it as close as possible to
our existing application's look-and-feel.
So I have an elance-laf.xml which points to an elance.xss stylesheet.
In elance.xss, I override some of the simple laf styles.
In addition, I also want to define my own styles.
so elance.xss looks something like this:
<?xml version="1.0"?>
<styleSheetDocument xmlns="http://xmlns.oracle.com/uix/style">
<styleSheet>
<style name="DefaultFont">
<property name="font-family">Courier</property>
<property name="font-size">14pt</property>
</style>
<style name="ButtonServerText">
<property name="background-color">#CEC992</property>
</style>
<style name="myStyle">
<property name="background-color">#8397AF</property>
</style>
</styleSheet>
</styleSheetDocument>
The problem is that "myStyle" never makes it to the automatically generated
cabo/styles/cache/elance-desktop-2_2_8-en-ie-6-windows.css
Is this not allowed?
I need this because I will be writing some custom template
based renderers where I would want to use my own styles.
Any help is greatly appreciated.
Thanks,
Jayesh Kapoor

Hi Jayesh -
The XSS language supports two different types of styles: named styles and selector-based styles.
Named styles are used to define a set of style properties that are referenced by name from other styles (using the <includeStyle> element). These styles do not show up in the generated CSS style sheet - they are used to simplify the XSS style sheet definition.
Selector-based styles are associated with a CSS selector instead of a name. These styles do show up in the generated style sheet.
So, if you want to define a CSS style, you'll need to specify a selector-based style instead of a named style. That is, instead of:
<style name="myStyle">You want:
<style selector=".myStyle">Note that I added the "." prefix to your style name to indicate that it is a CSS class selector.
Andy

Trying to add css style sheet to an old-fashioned html file.

I have several old html files that I have worked on regularly for the last 25 years. I recently recognized the value of separate css style sheets.
I set up the old html files in separate folders like this -
_css
_images
_notes
_scripts
.htaccess
index
profile
the _css folder contains a file named style.css which looks like this -
@charset "utf-8";
/* CSS Document */
<style type="text/css">
          h1 {font-size:250%; font-family: "Comic Sans MS"; color: #66FFFF; text-align:center;}
          h2 {font-size:120%; font-family: "Comic Sans MS"; color: red; text-align:center;}
          p {font-size:100%; font-family: "Comic Sans MS"; color: #EEEEEE;}
</style>
<body style="background-color: #55035F";
I open the index file with DW. - I click on "class" at the bottom of the page. - I click on "attach style sheet." -   it shows file/url: as "_css/style.css" - I click on "OK" - it says "file _css/style.css appears to be an html file and cannot be opened as css"
I copy the contents of style.css onto a new blank css file and save it as a css file.
I go through the same routine and the same thing happens over and over again.

You need a proper CSS document. CSS files cannot contain any HTML code.
@charset "utf-8";
/* CSS Document */
<style type="text/css">
          body {
               background:#55035F;
               font-family: "Comic Sans MS", "Comic Sans MS5", cursive;
               font-size: 100%;
          h1 {font-size:250%; color: #66FFFF; text-align:center;}
          h2 {font-size:120%; color: red; text-align:center;}
          p {color: #EEE;}
</style>
<body style="background-color: #55035F";
Nancy O.

Update document after style change

I have an application that allows named styles in a DefaultStyledDocument to be modified through a dialog. I would like the displayed document to be updated to reflect the changes when the dialog is closed.
I get changedUpdate DocumentEvents in the listener for the document, but I don't know what to invoke to get the changes displayed.
The document is displayed in a JTextPane. I am using Java 1.4.1_02.
Thanks,
Barry

I figured out what the problem was. I was using setCharacterAttributes on DefaultStyledDocument to set the style for a string, but this appears to only copy the attributes to the created leaf element - it does not hook the style into the resolveParent like it does for branch elements (this is a difference between setLogicalStyle and setCharacterAttributes). The DefaultStyledDocument class doesn't have an equivalent for setLogicalStyle at the content level, but it is possible to accomplish the same effect by creating a dummy style that has the desired style as its parent and using that in setCharacterAttributes. This appears to provide the required effect.

Re-naming Styles

Similar Messages

Maybe you are looking for