I apologize if this question has already been asked, but I haven’t been frequenting FreewayTalk in a while.
Are there any issues with upgrading a Freeway Pro 6 website to FWP 7? Is it simply a matter of opening a FWP 6 document and saving it as a FWP7 site or is it more involved than that?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
The only way of checking is to open the FW6 then save it as a different file name. Then test it. And test it again.
David Owen
On 23 Sep 2014, at 19:39, RavenManiac email@hidden wrote:
Are there any issues with upgrading a Freeway Pro 6 website to FWP 7? Is it simply a matter of opening a FWP 6 document and saving it as a FWP7 site or is it more involved than that?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
When we went from 5.5 to 6 there was a lot of good feedback on migration
strategy here on the forum. Still a 6 user, does anyone have feedback about
using 6 and 7 together… or does the actions folder and such become too
complex to use together?
–
Ernie Simpson
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
On 23 Sep 2014, 7:13 pm, The Big Erns wrote:
When we went from 5.5 to 6 there was a lot of good feedback on migration strategy here on the forum. Still a 6 user, does anyone have feedback about
using 6 and 7 together… or does the actions folder and such become too complex to use together?
There is a specific reason for less feedback - the two chapters of how to make inflow constructions:
Backdraft or Handmade!
An “I don’t deal with code user” doesn’t really matter - absolutely.
While a Backdraft-user depends on actions, a craftsman doesn’t (usually). And there we are at the most critical actions point:
####Auto-Clearfix and Box-Sizing
Both seems to break currently in 7. So if you depend on them - keep 6, if not - it’s just some additional styles and extended dialogue which work in 7, too.
This point is more critical. 7 doesn’t declare position:relative by default. It adds it as far as you add some child-items. This will mean, that you do not recognize this if you work from scratch.
But migration means:
If you have for example absolute positioned items in a relative parent, this item will be off parent. Solution here: Extended dialogue for the parent.
I can’t speak for much more actions cause I don’t use them. HTML5 set works, comment on DIVs works as well, google stuff had been adjusted (I hope for both versions).
For all the rest I can’t speak.
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
While a Backdraft-user depends on actions, a craftsman doesn’t
(usually).
I know where you’re coming from with that but it’s a rather simplistic
attitude. 
k
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Yes it is, apparently.
But it is just two steps to make backdraft working in 7 - I wonder why no one recognized it - no, it doesn’t make me wonder, so I keep up this line!
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Not to open the larger discussion, I am just wondering if there are any
problems using 6 and 7 side by side - in the same way we used 5.5 and 6
side by side without wrecking the work of either.
But when we do open the larger discussion, I have no motivation to upgrade
from 6 - there is nothing in 7 that I can’t already do as easily. Call me
when there is an upgrade that benefits my needs.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
6 + 7 use the same folders so it’s always a risk.
Keep 6 - I call you when the workspace in 7 works box-sizing:border-box.
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
For box-sizing I use the following CSS in my masters - along with a reset:
*, *:before, *:after {
-webkit-box-sizing: border-box;
-moz-box-sizing: border-box;
box-sizing: border-box;
}
It does the trick for me 
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
in browser yes - I’m talking about the workspace.
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
On 23 Sep 2014, 9:08 pm, The Big Erns wrote:
Not to open the larger discussion, I am just wondering if there are any
problems using 6 and 7 side by side - in the same way we used 5.5 and 6
side by side without wrecking the work of either.But when we do open the larger discussion, I have no motivation to upgrade
from 6 - there is nothing in 7 that I can’t already do as easily. Call me
when there is an upgrade that benefits my needs.
Big Erns, that is very encouraging to me. I’m old (71) and fairly low-tech. I have appreciated your expertise on this forum. If you are comfortable sticking with 6 Pro, that greatly reinforces my earlier decision to do so, too.
As long as I still have a functional brain and some health, I just want to devote myself to creating content, not facing a new learning curve.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
On 23 Sep 2014, 9:29 pm, The Big Erns wrote:
For box-sizing I use the following CSS in my masters - along with a reset:
*, *:before, *:after { -webkit-box-sizing: border-box; -moz-box-sizing: border-box; box-sizing: border-box; }It does the trick for me
Hey Ernie, I’d like to try this trick. Where should I place this code?
BTW, I am planning on upgrading to FWP 7, if nothing more than to support Softpress, but I’m hopeful that the transition from FWP 6 websites will be relatively painless.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Hey Ernie, I’d like to try this trick. Where should I place this code?
You can wrap the code in style tags and paste that into your master page
head - but that is not how I do it.
Open the Edit Styles window and create a new style. Clear the name field
and paste this into the Tag field:
*, *:before, *:after
Next, extend this new style with the Property Name: -webkit-box-sizing
In the Value part, paste the following:
border-box; -moz-box-sizing: border-box; box-sizing: border-box
And that’s it. As Thomas pointed out, it has no effect on the Freeway
workspace appearance but will affect your output just dandy. The nature of
the selector should take care of everything you need, especially if you
keep your styling uncomplicated.
Have fun.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thanks! I’ll give it a shot.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
… but it should be noted as well, that it is important to discuss every single item by hand:
Assumed you create the #area (the centering DIV - you know what I mean), define it on 75% width and apply a padding to both sides, you’ll recognize, that this DIV will have a new inspector value - let’s say 72.07%.
You need to adjust this - via extended (DIV style) back to width:75%. This is what the action does automagically! Or is supposed to do. But I’m sure that we discussed this in the screencasts (have to double-check) - so no excuse for my subscribers
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options