Ongoing Search for total CSS enlightenment!

What are these Freeway auto generated styles for - each one specifically?

.f-sp { font-size:1px; visibility:hidden }
.f-lp { margin-bottom:0px }
.f-fp { margin-top:0px }
.f-x1 {  }
.f-x2 {  }
.f-x3 {  }

And in the ie6.css file?

.f-x1 { height:100% }
.f-x2 { height:1px }
.f-x3 { display:inline }

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

On Sep 5, 2009, at 6:10 AM, WebWorker wrote:

What are these Freeway auto generated styles for - each one
specifically?

.f-sp { font-size:1px; visibility:hidden }

This one appears to be mostly applied to empty HTML boxes, say if you
draw a box and fill it with a color. This probably is what allows you
to draw an HTML box that is 1px tall and not have the browser force it
to be 16px tall (to accommodate the nonexistent paragraph that the
browser might decide “ought” to be in there).

.f-lp { margin-bottom:0px }

The last paragraph of a run of text. This sets the bottom margin to 0,
so there isn’t an artificial extra line of space at the bottom of a
close-fit container box. If you apply a background color to your HTML
box and unset the box height so it shrinks to the content, you’ll see
this.

.f-fp { margin-top:0px }

Same as above, for the first paragraph, sets the top margin to 0.

.f-x1 { }
.f-x2 { }
.f-x3 { }

These seem to set the stage for the IE fixes below. These empty styles
get applied to elements that IE would get wrong, and then the
conditional comments force the IE fix CSS to be applied later, and
only in the presence of the Dark Angel of Layout Failure.

And in the ie6.css file?

.f-x1 { height:100% }
.f-x2 { height:1px }
.f-x3 { display:inline }

Not sure, you’d have to plow through the source of a page that has the
various IE fixes applied to it. At a glance, they are used to fix IE’s
various and entertaining excursions away from the W3C HTML layout specs.

Walter


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Thanks for that Walter,

I was assuming there was a certain amount of zeroing out the browsers defaults to set a default stage. As I’ve been reading up on that recently.

Its interesting that the more power you see in CSS the less WYSIWYG Freeway needs to be for you. It will be very interesting how Softpress address this issue as more Freeway designers push the CSS envelope. Or will Softpress not do much on this front, and assume said designer will just move on to hand coding using something like CODA?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

It will be very interesting how Softpress address this issue as more Freeway designers push the CSS envelope. Or will Softpress not do much on this front, and assume said designer will just move on to hand coding using something like CODA?

It’ll be interesting to see what Softpress does to fill the lack of CSS options in FW. I’ve always been an advocate for creating a much larger separation between Pro and Express, because currently it locks FW at a beginning / starter-like software rather than producing a professional work-place app and it seems like they don’t want to jump too far forward because of the feature set of Express. Hence why a crowbar, not Walter’s, will suffice.

I believe, and I’ve stated it many times, that Softpress is missing a golden opportunity to expand both the company and the software and rather than ‘action-izing’ everything give its faithful users what they want (within reason).


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

It’ll be interesting to see what Softpress does to fill the lack of CSS options in FW. I’ve always been an advocate for creating a much larger separation between Pro and Express, because currently it locks FW at a beginning / starter-like software rather than producing a professional work-place app and it seems like they don’t want to jump too far forward because of the feature set of Express. Hence why a crowbar, not Walter’s, will suffice.

I believe, and I’ve stated it many times, that Softpress is missing a golden opportunity to expand both the company and the software and rather than ‘action-izing’ everything give its faithful users what they want (within reason).

The current state of FW’s multiple windows to edit css is cumbersome, I would love to see a single interface like CSS Edit’s right in FW.

Marcel


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I’ve passed on articles about several such ideas to the core team, you
should do the same. I would love to see a zero base built into
Freeway’s output, and then everything would Just Work™ the way it
should.

Walter

On Sep 6, 2009, at 3:14 PM, WebWorker wrote:

Thanks for that Walter,

I was assuming there was a certain amount of zeroing out the
browsers defaults to set a default stage. As I’ve been reading up on
that recently.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Don’t get me started about the layers of dialogs and sub-dialogs and
sub-sub-sub-dialogs. Grrrrr. RSI, here I come.

Walter

On Sep 6, 2009, at 6:36 PM, Helveticus wrote:

The current state of FW’s multiple windows to edit css is
cumbersome, I would love to see a single interface like CSS Edit’s
right in FW.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

The current state of FW’s multiple windows to edit css is cumbersome, I would love to see a single interface like CSS Edit’s right in FW.

I agree with this. Multiple windows, using the extended button for missing css properties and values, it goes on and on.

Cross our fingers for v6.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Hello,

Regarding the Freeway auto generated styles:

.f-sp { font-size:1px; visibility:hidden }
.f-lp { margin-bottom:0px }
.f-fp { margin-top:0px }
.f-x1 { }
.f-x2 { }
.f-x3 { }

Is there a particular reason that they do not automatically go into external css stylesheets when that is switched on in the document set up? Is it ok to move these from the html page and copy them into the external stylesheet? I have just tried this using Coda and all seems ok in the preview but want to make sure its definitely is ok to do this.

I have also moved the CSS menus (created with css menus action) into an external stylesheet and again it seems to be working but I just want to make sure it’s ok to do this.

Thanks

Mog


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Not sure why that is, you might want to file a feature request with
Softpress about that because it would make the page a little leaner.
Some of this is related to the IE-fix stuff, though, so it might need
to be at the page level in order to work effectively.

Note that you can do anything you like to these files, but the next
time the site is published from Freeway, all your Coda changes will be
rolled back. Freeway generates these files, but doesn’t read them back
in or consult them in any way after it does so. The only thing it does
is track the modification date-time of the files as it publishes them.
If the file is modified after that time, it may alert you the next
time you try to publish. (In the case of HTML files, it definitely
does this, but in the case of images or CSS sheets, it just silently
replaces the modified resource with its own.)

Walter

On Mar 1, 2010, at 1:27 PM, mog wrote:

Hello,

Regarding the Freeway auto generated styles:

.f-sp { font-size:1px; visibility:hidden }
.f-lp { margin-bottom:0px }
.f-fp { margin-top:0px }
.f-x1 { }
.f-x2 { }
.f-x3 { }

Is there a particular reason that they do not automatically go into
external css stylesheets when that is switched on in the document
set up? Is it ok to move these from the html page and copy them into
the external stylesheet? I have just tried this using Coda and all
seems ok in the preview but want to make sure its definitely is ok
to do this.

I have also moved the CSS menus (created with css menus action)
into an external stylesheet and again it seems to be working but I
just want to make sure it’s ok to do this.

Thanks

Mog


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

On Mar 1, 2010, at 12:27 PM, mog wrote:

Is there a particular reason that they do not automatically go into
external css stylesheets when that is switched on in the document
set up? Is it ok to move these from the html page and copy them into
the external stylesheet

It’s OK to move the styles into an external file but FW will continue
to add them to the page anyway (I think). I don’t know of any way to
stop FW from doing this. Out of curiosity, do you plan on using FW for
future edits or are you moving everything over to another app (Coda)?

Todd


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Hi Todd

I have been happily using Freeway until I was asked if I could remove the CSS menus code from the html page and put the code in an external file. So I’ve duplicated the files and I’m testing this out Coda to edit the last bits after I am happy with the overall design in Freeway. I guess if I have to do more updates/maintenance in Freeway I will have to keep re- editing the stylesheets in coda.

Thanks for your help

Mog


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

As long as they don’t leave us non-coders in the dust!

I’m starting to learn a little, code-wise, but I just don’t enjoy it and find it unintuitive. I like the Actions and I also like to know how and why they work, as long as I don’t get my hands TOO dirty!

I also work in 3D as a hobby and when coding comes up, I usually stay away, but the software I use has an expression, node, wire system that I can sort of use on occasion, but that’s it.

Bob


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

if you want to move all the inline styles and the styles generated by the navigation actions which are placed in the head part of your HTML document into an external css sheet, then I would recommend using tim plums externalize action
its worked flawlessly.
It moves al the page specific styles into a page specific style sheet while the generic styles are still kept within the normal external style sheet.

all the best max


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Hi Max

Thanks for that. I will try that option. Thanks to everyone for your help.

Cheers

Mog


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options