Here’s a very simple layout made in TextMate: Test
Adorable, right?
Trying to replicate this in Freeway 6, I run up against a fundamental issue with the way the new flexible layout tools work. I can make everything work except the 100% heights of the individual panes. Freeway keeps adjusting these down to some mix of percentages that will add up to 100%, but it won’t let each one be 100% tall. Either I have to set the outer box to 300% tall, which blows up each pane too large, or I have to set each pane to 33.3333%, and that means that the panes can’t be edited the way they will appear (they will each have absolute-positioned children to convey actual meaning).
So I need to fool Freeway into showing me three 100% tall elements inside a 100%-tall parent. Any of you cracked this nut yet? So easy with hand-coded CSS… Client wants the layout in Freeway. I would like to make this easy for him.
Well - two methods I got in mind, however I can’t judge ig they are really Freeway-friendly:
Method 1:
The extended DIV(Style) dialog which overwrites the basic inspector-settings (such as the 33.33333%). Don’t forget the box-sizing:border-box.
The downside:
You have (sometimes) to “simulate” the appearance of the construction view.
Method 2:
Using the ID2class Action to “remove” the DIV styles from the Freeway workflow. This allows me to “natively” build styles without loosing the visual control of this DIV.
There’s a lot of overriding, but I bet you knew that already. The two BIG
things are 1) FWP’s insistence on writing PageDiv with min-height:100% -
overcome with your PageDiv Extended action. 2) the order which FWP writes
the stylesheet, making the background image hard to replace class-wise.
Overcome by writing those styles as Page Markup before /head but still
after the FWP style reference.
There’s still the issue of all the “junk” code FWP auto writes… If you
don’t need FWP to output this, it’s easier by hand - but it CAN be done.
–
Ernie Simpson
On Mon, Jan 6, 2014 at 1:24 PM, Walter Lee Davis email@hidden wrote:
Here’s a very simple layout made in TextMate: Test
Adorable, right?
Trying to replicate this in Freeway 6, I run up against a fundamental
issue with the way the new flexible layout tools work. I can make
everything work except the 100% heights of the individual panes. Freeway
keeps adjusting these down to some mix of percentages that will add up to
100%, but it won’t let each one be 100% tall. Either I have to set the
outer box to 300% tall, which blows up each pane too large, or I have to
set each pane to 33.3333%, and that means that the panes can’t be edited
the way they will appear (they will each have absolute-positioned children
to convey actual meaning).
So I need to fool Freeway into showing me three 100% tall elements inside
a 100%-tall parent. Any of you cracked this nut yet? So easy with
hand-coded CSS… Client wants the layout in Freeway. I would like to make
this easy for him.
Oh, and I would like to add that I used the Advanced Inline Style Mover
action to remove the div id’s – not absolutely necessary I think, but in
the spirit of trying to recreate the original code.
I’ve gone back and redone some things that were left out in haste… namely
made the page html5 instead of whatever.
I’ve also re-thought some of the css - nothing major, just my own biases
setting in. I used the PageDiv Extended action, but on secon thought that’s
easier dealt with in the internal user stylesheet.
If I kept at it, I think the big styling problem would become ordering user
styles in the external stylesheet. Ugh.
Thomas, that must be some browser thing - it’s overridden by the user body
rule.
–
Ernie Simpson
On Mon, Jan 6, 2014 at 3:53 PM, Thomas Kimmich email@hidden wrote:
cool Ernie, however there is a body (user-agent) style margin-top of 8px
that I don’t understand, honestly.
Externalizing the stylesheet could be done by trying to decipher how FWP
orders the stylesheet, then renaming the pane, one, two three styles to fit
that scheme. Easier I think to write those styles to a second custom
stylesheet and then reference it in the Page Markup before the closing head
tag.
Finished annotating the file on my server as well. Walter, it would be fun
to see what you’re doing with this… you’ve peaked my curiosity
Commenting by MarkUp seems not to be a good idea here. Applied the
RemovePTag action, but gives a weird output.
I know, I wish there were a better way to comment from within Freeway Pro,
it seems like so much work for the reward. Think I will just comment
afterwards - even retyping them after each output seems easier
Thanks very much, guys, you’ve helped me break the log-jam here. Getting Freeway to generate that precise code was never the goal, just getting it to look sane in the Freeway document while outputting code that looked the way it was supposed to look. The key was the PageDiv Extended Action – forgot I wrote that one. It’s very definitely not ready for Freeway 6 yet! Serious output error here when I use it.
Walter
On Jan 6, 2014, at 4:38 PM, Ernie Simpson wrote:
Commenting by MarkUp seems not to be a good idea here. Applied the
RemovePTag action, but gives a weird output.
I know, I wish there were a better way to comment from within Freeway Pro,
it seems like so much work for the reward. Think I will just comment
afterwards - even retyping them after each output seems easier
On Jan 6, 2014, at 4:42 PM, Walter Lee Davis wrote:
Thanks very much, guys, you’ve helped me break the log-jam here. Getting Freeway to generate that precise code was never the goal, just getting it to look sane in the Freeway document while outputting code that looked the way it was supposed to look. The key was the PageDiv Extended Action – forgot I wrote that one. It’s very definitely not ready for Freeway 6 yet! Serious output error here when I use it.
Walter
On Jan 6, 2014, at 4:38 PM, Ernie Simpson wrote:
Commenting by MarkUp seems not to be a good idea here. Applied the
RemovePTag action, but gives a weird output.
I know, I wish there were a better way to comment from within Freeway Pro,
it seems like so much work for the reward. Think I will just comment
afterwards - even retyping them after each output seems easier
