The whole reason for making styles in a separate stylesheet is to do
things that Freeway can’t do (or can’t do easily) in the normal
interface.
There is no earthly reason to replace the Freeway-drawn styles with
the same thing done over in an external stylesheet – and then wonder
why the interface is broken. Freeway is perfectly capable of creating
external stylesheets all by itself, and even if you have in-page
styles, there is nothing wrong with that approach at all.
The real reason for adding styles with CSSEdit and this Action is so
that you can do clever hand-coding things, and you don’t usually need
to apply those sorts of styles. If you are clever and hand-coding and
all, you know how to target elements without touching them in the
Freeway interface.
Draw a layered HTML box on the page, add some text and make links on
part of that text, make note of its name in the Inspector (item4 in
this example), then fire up your editor:
#item4 {
border: 1px dashed red;
padding: 8px;
margin: -9px;
}
#item4 p a {
text-decoration: none;
padding: 3px 6px;
margin: -3px -6px;
background-color: #000;
color: #fff;
}
Neither of these styles will show up in Freeway, but if you attach
this stylesheet to your page, then the box item4 will gain a bright
red dashed border, and all of the links that are children of paragraph
tags inside it (but not those that are children of list items or
headers) will become black boxes with white type inside. All without
you doing anything in Freeway besides loading this style sheet into
the page.
This is a silly example, but it demonstrates the sort of thing you can
do easily with a CSS editor that is non-trivial to do in Freeway
without risking RSI in the Extended dialog.
Walter
On Jan 29, 2009, at 4:56 PM, Robin Stark wrote:
But, where ARE these styles after I do this? I simply must be
missing something.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options