It’s fixed, and I took down the broken version. The Convert to Style
Sheet should be 2.01, if you have already downloaded the broken one.
Just to add a bit to the discussion of this Action suite, here’s how I
use it (and thus how I imagined other would use it).
First, the Convert to Style Sheet is a bit of a lame duck any more.
When I wrote this, the problem was that you couldn’t get Freeway to
create an external stylesheet at all. It does this trick now, out of
the box. But it still has a bit of use in the cases where you might be
assembling a page out of template parts or partials. If you have
carved up a page into little bits that get run through a server
process and merged on the fly, you might find that a bit of text from
one page is referencing a CSS style that doesn’t exist on the parent
page where this assemblage is taking place. So by pasting a bit of
reference text into your “style” page and applying the Action to that
page, you can create a stylesheet containing the missing styles, and
then inject that back into the main shell page where these template
partials are being used.
Second, the Extra Styles button was added to Convert to Style Sheet in
order to allow you to easily hand-code a few extra styles into a sheet
that was largely created by letting Freeway write the styles, not as a
general editing environment. After all, if you want to hand-code CSS,
the fwBigPrompt control is hardly the place for it. There’s no syntax
highlighting, not even tabs are allowed – totally primitive, like
coding in System 4 SimpleText. Now that you can attach regular files
(coded in a proper editor, like CSSEdit or a programmer’s text editor)
there’s really no need for this side of the suite to exist besides
converting Freeway-drawn styles into an external reference.
So if you want to make up a bunch of hand-coded styles, just create a
new sheet in a real editor, save it as a file somewhere on your disk,
and then in Use External Style Sheets 2.0, un-check Use Site Pages As
Stylesheets and simply attach your .css files directly. No copy and
paste into a separate page required.
Walter
On Jan 25, 2009, at 5:25 PM, waltd wrote:
sorry, typo in the Action. Should read
fwParameters[‘remove’].fwBoolValue
with a dot between the parameter and the attribute name.
I’ll fix it in a few minutes.
Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options