Can anyone who has created a Responsive Website just by using 100% Freeway 7 (Not Backdraft or templates) please send me a link and maybe some feedback on how you got on ?
Just interested. Thanks Steve
I’d like to point out here that inline construction is NOT an absolute requirement for creating responsive sites. It is definitely important if you’re feeding in content from CMS sources, but for predefined content it’s not the only way.
http://panoramaphotographer.com/ is one basic example. It’s also something that would be, well, let’s just say “challenging”, to recreate using inline methods in Freeway.
This uses a flexible-width page and stretchy objects in a normal (not inline) Freeway layout, and it has tweaks for object sizes and positions at different breakpoints. The zip archive includes a couple of custom fonts; remember to install or activate those before you open Freeway.
Your site keeps crashing the Safari tab (a problem occoured when loading this page so it was re-loaded - over and over) on this iPad 4. Might be a memory issue perhaps?
Almost certainly. Which iPad are you using, and what version of iOS?
Does it help if you terminate and restart the browser?
I do need to look at this; having four fairly hefty panoramas in the one page (one of those doubled-up for VR headsets) is a bit of a strain. But for the record (for those reading) this is nothing to do with how the page is built.
Hm - I’m neither sure what the OP is after, nor do I understand the ongoing discussion about the page-example. Responsive design doesn’t depend on the app/software you use - it’s a question of attitude, planning and construction (no matter which design you’re after).
I started Responsive Design in mid 2012 using Freeway 5.5 and this is the very first (naive) example I did:
To me, Responsive Design is “Evolution” - using the given tool (@media query) to change some small properties. This is just because I’m consequently develop the given things further.
Involved in ten billion discussions since three years now, I’m pretty convinced, that this audience understands responsive design as “Revolution”. This mainly happens by ignoring the signs of the time - over years.
Position: absolute - or drop and drag is obviously the preferred way to go, however stops the evolution all of a sudden. So threads like these will attend us to the end of time.
In mid 2015, I’d like to start discussions which are bringing us further. Such as:
How to manage styles better in order to get cleaner code.
Flexbox - Just another property or big chance solving problems never had been solved before?
What about responsive resources (conditional loading) and JS in an adaptive world?
Does it make sense to discuss those right now or should I wait another three years till mid 2018?
This is my first attempt at a responsive site. http://www.unitywoodstock.orghttp://www.unitywoodstock.org/
I used Backdraft and it helped me construct the site as well as the learning curve; also provided excellent support. Other leaning assists were the Softpress responsive templates and Tom Kimmich’s website, not to mention this listserve. I am grateful for all of them.
You’ve been around FWT long enough to know that when it comes to technical discussions it often requires considerable poking and prodding by the minority before the majority takes a proactive interest. That’s assuming they do at all.
By all means open a dialog! But don’t be surprised if the people that participate are the same 6-10 people that always participate in this type of discussion. As a community it’s a tough group to engage or motivate on a technical level. Effecting change around here can be a slow tedious process.