Getting back into a company site after a year away from Freeway. It was built in Freeway Pro 6. Some of the actions used don’t list that they are compatible with Freeway Pro 7 on Actions Forge.
ACTIONS IN QUESTION
CSS3 Corners (item-action) - v. 0.6.3
CSS3 Gradient Backgrounds (item-action) - v. 0.9
Background Supersizer (page-action) - v. 0.3.4
QUESTIONS
Are the actions compatible with Freeway Pro 7?
Has Freeway Pro 7 obsoleted the need for any of these actions with new built in functionality?
On Mar 6, 2015, at 1:13 PM, TeamSDA email@hidden wrote:
Hello Freeway Talk Community…
Getting back into a company site after a year away from Freeway. It was built in Freeway Pro 6. Some of the actions used don’t list that they are compatible with Freeway Pro 7 on Actions Forge.
ACTIONS IN QUESTION
CSS3 Corners (item-action) - v. 0.6.3
I think you can skip this one, rounded corners are native in Freeway 7.
CSS3 Gradient Backgrounds (item-action) - v. 0.9
I think you will still need this one if you want to use CSS for gradients.
Background Supersizer (page-action) - v. 0.3.4
There’s nothing native in Freeway 7 that can do this, but you can create a full-screen background with the Extended palette, same as you could in Freeway 6 and 5 (and probably 4).
QUESTIONS
Are the actions compatible with Freeway Pro 7?
They will probably work, but they will not respect any breakpoints you set in the new interface. Then again, no Action will do that yet.
Has Freeway Pro 7 obsoleted the need for any of these actions with new built in functionality?
You indicate that the CSS3 Corners Action is no longer needed in FWP7, I am aware that rounded corners are available in a Table, But cannot find any reference to Rounding Corners on HTML item for example?
Or have i missed something, which is very likely???
No, you’re not missing anything – I am mistaken. You can create a rounded corner on an element in Freeway, but it uses a bunch of meaningless non-semantic extra elements to do this trick. Sorry to get your hopes up. (If you want, you can use this effect by clicking on the Style tab in the Item Inspector, then clicking on the first icon at the left in the Graphic Effects segment, then setting a corner radius there. I could have sworn that border-radius was added to the core of Freeway in the last major revision, so I am sorry again to lead you astray.
Walter
On Mar 7, 2015, at 6:06 AM, ejw email@hidden wrote:
Walter,
You indicate that the CSS3 Corners Action is no longer needed in FWP7, I am aware that rounded corners are available in a Table, But cannot find any reference to Rounding Corners on HTML item for example?
Or have i missed something, which is very likely???
Hello Walter… Thank you for your detailed response. While I have a grasp of the basics of responsive design as it pertains to rearranging elements on a web page based on screen size I am new to how Freeway Pro is handling this.
Could you expand on what you mean by?
“They will probably work, but they will not respect any breakpoints you set in the new interface. Then again, no Action will do that yet.”
Sure. The Actions API allows developers to write Actions that rewrite the contents of the page (HTML, CSS, and JavaScript) in almost any manner imaginable. However, from an Action’s point of view, there is only one page, not N breakpoints x each page. When Freeway writes out the CSS for the page, it takes into account whatever differences you have created at each of the breakpoints you have defined. Actions can only see the default style, and are not a part of the process of creating any of the non-default styles. So if you had decided to make a carousel that perfectly fit the large screen, then tweaked the dimensions of that carousel at the other breakpoints, the only thing that the Action would see (and would be able to adjust) would be the default styles.
Freeway (and/or the Actions API) would have to change to make this possible, or I would have to radically rethink the way that the Action works so that it could respond to breakpoints naturally without “knowing” what they are.
Walter
On Mar 8, 2015, at 11:28 AM, TeamSDA email@hidden wrote:
“They will probably work, but they will not respect any breakpoints you set in the new interface. Then again, no Action will do that yet.”
Very helpful, thank you. A few questions for greater clarification…
Will the CSS3 Corners and Gradient actions I listed above be affected by the change in size to either the page or items by setting up breakpoints and re configuring items so long as I don’t make an item to small to accommodate the radius or such?
Or are all actions impacted by the actual size of the page or position of an item and are now a no go if I am using the new break point features in Freeway Pro 7?
If item 2 is the case, then do I need to add all features/styling manually through Freeway for each item that has changed on the page due to a new breakpoint?
On Mar 8, 2015, at 12:55 PM, TeamSDA email@hidden wrote:
Very helpful, thank you. A few questions for greater clarification…
Will the CSS3 Corners and Gradient actions I listed above be affected by the change in size to either the page or items by setting up breakpoints and re configuring items so long as I don’t make an item to small to accommodate the radius or such?
You will only be able to set a single set of corner radii on a page, and you will not be able to make the radius different at different breakpoints. If you can live with that, then you should be able to get along fine with this Action.
Or are all actions impacted by the actual size of the page or position of an item and are now a no go if I am using the new break point features in Freeway Pro 7?
Any Action that generates style information or modifies style information will be something to test carefully before implementing it in a production site. As noted earlier, the only thing that any Action can modify style-wise is whatever the page looks like at the default breakpoint. Any changes made at that level will cascade downward to the smaller breakpoints.
If item 2 is the case, then do I need to add all features/styling manually through Freeway for each item that has changed on the page due to a new breakpoint?
Freeway’s implementation of breakpoint styling is very manual – Action or not – and you have to make any and all changes that you wish to see at a particular breakpoint for yourself, on each page. Any changes you make at a non-default breakpoint will need to take any Action changes to the starting CSS into consideration. And if an Action fundamentally rewrites the HTML (as the original Carousel did) then you will not have the actual HTML in the page (in Freeway) in order to construct your desired breakpoint CSS. The elements just won’t be there at all, and so Freeway won’t be able to make CSS for those elements. Your only recourse will be to create a manual override stylesheet, link it to your page with one of the External CSS Actions, and code your CSS by hand.
Sorry, to clarify, I mean PER OBJECT, not one set of curved borders on the whole page. This is the opposite behavior of per breakpoint x per object, which is the goal I believe we all want to reach.
Walter
On Mar 8, 2015, at 1:19 PM, Walter Lee Davis email@hidden wrote:
Thank you for the deeper clarification and on the weekend nun the less. This is quite helpful as I have been getting reacquainted with Freeway Pro and the new Pro 7 after a year away. Lots of reading testing and preparing before retooling our corporate site and launching a site for a new venture mid April.
Again many thanks, your assistance is appreciated as always.