Page Div Styles

Is there an action that removes the style from the pagediv in the html? There is a great “remove div style” action by Weaver. Something like that, but to use on the pagediv, would be great.


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

What part of the style would you like to remove? There are a lot of
dependencies in the Freeway-generated HTML. If you were to remove the
“position:relative” part, for example, all of your position:absolute
DIVs that you drew on the page would suddenly fail (quite
spectacularly) to lay out the way you expect in IE and some flavors
of Safari.

If you want to remove the width of the PageDiv, then all you need do
is not align the page. If you want to remove the height or min-
height, then my question is “Why?”.

More info about your desired result, please!

Walter

On Sep 24, 2008, at 6:08 AM, maccie wrote:

Is there an action that removes the style from the pagediv in the
html? There is a great “remove div style” action by Weaver.
Something like that, but to use on the pagediv, would be great.


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


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

I want to clean out the html code and place all the styling in the css, as it should be. It would be nice if all the styling you do via the inspector palette is placed directly in a css stylesheet, like dreamweaver, instant access to the css file. Mmm, maybe freeway 6 …
Is there a specific reason why freeway places certain styles (width, height, float, bg color, position,…) in the html and not in the css? I like your site, Walter, and there is no styling in the html. Something tells me that you handbuilded your site, the coding is to nice …


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

I hand coded this version of my site, mostly because I was doing some
fancy stuff with a template engine. But Freeway taught me most of
what I know about clean HTML code – don’t sell it short!

I understand what you’re trying to do here. One reason why Freeway
does what it does is because each DIV is ID’d in a page-unique way,
but not a site-unique way. So if you use a site-wide stylesheet,
there’s a very real possibility of ID clashes. I know that this is
something (moving the style entirely out of the page) that they want
to do, but it didn’t make the cut for 5. Perhaps 6 will have it. And
inline CSS is perfectly valid, too. In fact, when you have a
singleton layout, it’s really the more correct way to go, because the
global stylesheet should be for things that are repeated across more
than one page.

Paul Dunning wrote an Action back in the Freeway 3.5 days that messed
with a site to extract all of the layout styles and move them into a
global stylesheet. It had to re-name everything on the page in order
to avoid clashes between pages (item1 on this page is a different
geometry than item1 on that page). As far as I know, this Action
doesn’t work with Freeway 5 or 4, because there is no way for an
Action to access or modify the external stylesheets. I could be wrong
about that, but last I heard it was dead.

Write to Softpress and let them know what you’re thinking. The more
people they hear from on this topic, the higher it will rise in the
feature list. Squeaky wheel gets the grease, and all that.

Walter

On Sep 24, 2008, at 5:39 PM, maccie wrote:

I want to clean out the html code and place all the styling in the
css, as it should be. It would be nice if all the styling you do
via the inspector palette is placed directly in a css stylesheet,
like dreamweaver, instant access to the css file. Mmm, maybe
freeway 6 …
Is there a specific reason why freeway places certain styles
(width, height, float, bg color, position,…) in the html and not
in the css? I like your site, Walter, and there is no styling in
the html. Something tells me that you handbuilded your site, the
coding is to nice …


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


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

Thinking about this. I suppose the only way I can see this working with the restrictions we have at the moment, is for an action like Paul’s to harvest the styles and place them at the top of the html and then add the class to the item (the version I have does this already)

Then the next step is for the action to create a .css document and place these styles that have been harvested into that document.

The next step would be that the style sheet would be named to match the page name and finally a reference to this style sheet needs to be written in the HTML specifically for that page.

This way any Global styles stay in the global style sheet and any page specific ones would be placed in there own page specific sheet.

Or we could wait and see what the next generation of freeway will do…:o)

max


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

HI,
I did have an Action for Freeway 3 which put all the CSS into an external CSS document. It worked well, and this Action worked with it.

However, you had to be very, very careful about how your items on the page were named. For example, item1 on Page 1 would not necessarily be item1 on Page 2. You had to design exclusively in the Master Page and ensure that each item had a user defined name. You could then add content (carefully) to the child pages.

The Action was more of an experiment than anything meant to be used in genuine anger. It had some excellent side effects - pages loaded far more quickly because the CSS was cached locally, so just the HTML downloaded.

The downside here is that at the moment, Freeway encourages page-centric thinking when laying out a document. Even if you work on a master page, the model is applied to each page individually, not to the whole site. Pages exist in splendid isolation, and know nothing about other pages. Because of this, such an Action has to work very hard to achieve a site-wide CSS file, and there is likely to be breakage which an Action can not work around.

Writing the Action to be a folder Action would not help, as the folder Action runs basically as a Page Action - it’s not site-wide in the sense that “the site is the object” which it implies.

The best solution for this problem would be for Freeway to handle this - which will require a shift in thinking from pages to the site when placing items. You should not have to think any differently, but the processes which control items and objects within Freeway need to change.

Let softpress know what you want. They read this list, but using this form to send them feedback can only help to move this feature up the list.
http://www.softpress.com/kb/contact.php


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