Having read and watched the provided materials, I understand that the key things SP has done is to add a 2nd and 3rd leg to the in-flow item responsiveness component, by providing a WYSIWYG way to control breakpoints (including eliminating content through unchecking the display box), and a way of switching between a listed high-level navigation level and a single nav icon to access the nav list on a separate page.
Am curious to know from code savvy readers where they see the most freedoms and limitations in the solution, and from all readers what their wish list is of added functionality.
The breakpoint solution looks impressively robust to me, and am hoping that high on the list of features to add are show/hide layer triggers by scroll or anchor position, so one could, for example, show a fixed band of anchor links at the top of the page, and have the selected anchor in the list change as one scrolls down a long page communicating “you are here” to the reader.
We draw code and control it via “some” clicks and adjustments. This is incredible time-saving. I simply missed some things first (cause haven’t had a detailed look into the manual - shame on me).
It’s just see, do, set and forget.
Doing responsive pages doesn’t need really features constructional spoken.
The link-thing I am overwhelmed - simply not sure what you mean. Do have a prominent example somewhere?
It seems that sites are being designed now with fewer and longer pages and more anchors. Perhaps this is simply a parallel but unconnected trend to layout responsiveness. It cuts down on wait time for page loads, but readers can get disoriented as to where they are within a super deep page.
the trend is called One-Page Layout and yes - in principle everything is on a one long page. The key for this trend (IMO) is HTML5 with its entirely new way to structure content. In the past it was simply invalid to use multiple H1-Tags but today it is using multiple items, each able to carry one H1 Tag without breaking the outline.
This should be (no - it can) be done in Freeway as well.
@Wim
No doubt - Inflow-Constructions are still (and will be for a long time) the key to do rock-solid. The new features are just a classy way to do it “on-the-fly” using FW inspector rather than doing it by hand.
But absolute positioned pages should be good as well - the difference is just, that you need to grab each item and position it new - item, by item.
One small limitation is, which is called “Text-Styles”. It is sometimes good, to slightly adjust font-sizes especially in Mobile. But this can be fixed by a hand-made query but it would be classy if there could be an opportunity to add it to the internal query.
As far as I can tell, you won’t need to do that. I recently made an inline site responsive using Freeway 7, and the only issue I had was in needing to adjust my layout mechanics a little. I was using left and right positioning on the outermost container, and I had to switch that to left + width on the smaller breakpoints. But Freeway 7 makes this super-easy and non-destructive to do. It’s not quite multiple undos, but you can reset a breakpoint at any point and start over without needing to adjust any of the others.
Walter
On Jul 30, 2014, at 11:25 AM, Wimdg wrote:
@thomas
I am not really convinced about the advantages of the upgrade yet. I have a inline webpage which I made responsive.
Do you think I can easily migrate that site to 7? Or do I have to re-position my inline construction and the columns and so on.?
@thomas
I am not really convinced about the advantages of the upgrade yet. I have a inline webpage which I made responsive.
Do you think I can easily migrate that site to 7? Or do I have to re-position my inline construction and the columns and so on.?
Difficult to answer. Let me say it that way:
What we made (or at least you) is naturally still valid - but theoretically better to keep it as it is.
I am currently testing it on my backstage example page which is not responsive yet. The quickness on turning it is stunning.
I see no reason for not upgrading - I still of course run 6 parallel. Keep the current, duplicate the project folder and give it a try in 7 - compare.
@Julie
Nothing specific - this is just because I haven’t had the eggs yet to introduce the HTML5 stuff. The fixed in window I already did - but not the “scroll to fix”.
The WWF page is cool looking and worth to rebuild - but haven’t got the time to do (without a real plan).
