Just a few thoughts about the recent developments with FW.
Having just bought a new computer to facilitate FW upgrade to use Backdraft as FW7 had not been released. Responsive is a must now for sites but having downloaded the FW Trial and had a play with it last night, I am still a bit confused as to how to best proceed.
Both solutions no doubt will do the end job but as I see things Backdraft uses modules on one layout whereas I really have to design a large width page first with FW7 then repurpose that page for the breakpoints for the other device widths - that seems like a lot more work.
Backdraft seems to be put on hold just now (re FW7) and I need to progress as I have a few sites in the pipeline.
I really do want to learn about responsive layouts and be comfortable again with Freeway.
I do feel that FW7 has not addressed the basic tutorial side of things too well - what I would like to see is a basic FW7 template that I could use to see how the basics work. Something like a header - content - image etc and a footer. Sorry but we are not all experts and the responsive layout features are a giant leap forward. So what direction should I go? I struggled last night to get a basic page working. Should I buy a Template from Marketplace and use it to deconstruct. If Softpress could post up some basic how to videos it would be a great help.
By the way when I am here in FW7 how do I make an HTML element on a page fill the full width of the browser. Like the green bar here:
I’m in pretty much the same situation and have the same questions/frustrations.
I also use image galleries via an iFrame and would very much like to move to Exhibeo (although the styles are exactly what I want) but I find it exasperatingly difficult to see from the demo, exactly what it would look like. So I just give up.
as I see things Backdraft uses modules on one layout whereas I really have to design a large width page first with FW7 then repurpose that page for the breakpoints for the other device widths - that seems like a lot more work.
that seems like a lot more work.
You dont have to design a large page width first - just the size you would normally design to.
Then when you preview at the smaller sizes you see where the problems lie.
And with the announcement of the new Responsive templates this will make things a whole lot faster.
Remember that Backdraft is really just a Template too and if you want to move on beyond templating then you should get to grips with the Responsive functionality of 7. (Or buy RapidWeaver!)
But with both solutions (and there is no reason why you cant use BD with 7) you do need to understand more about inline construction.
Have not made the step up to 7 yet, but have just looked at the Softpress tutorial that Thomas mentioned (will we be seeing some of your own in The Lounge soon?).
On this tutorial it describes the process of making a page responsive. But the objects (text boxes and image boxes) appear to be just placed on the page - and not using inline (or box) construction.
It is required cause it is the way 99% of the web-pages in the world are constructed - FW7 doesn’t change anything.
Those building their pages on “absolute drop and drag method” have to re-arrange all items manually to the new position - which is easy but way more work to do.
Currently I don’t see “the big need” of creating something new cause it is “pretty” simple to adjust your stuff once you built a proper inflow-construction - cause you work with corresponding items - one is pushing the next.
All you have to do is (basically) to reduce your page-widths to the same amount than the breakpoints at each breakpoint.
Unfortunately, cause Freeway’s workspace is not “border-box”, you have to re-adjust some widths (cause it looks initially like a mess).
Once Freeway will have (and I hope it happens as soon as possible) a workspace “border-box”, this step won’t be necessary anymore - and I think then it’s time to record a new set of screencasts.
My point exactly - the items there are just placed on the page so at the next breakpoint the items have to be re-arranged.
So really we should be building inline from the largest size - am I correct? and if so why show this “drag and drop method” if we are really supposed to be using inflow construction.
… cause 87.332% (of the above described 1% of pages - read my comment above) are built on “absolute”.
Let me be clear here:
“Absolute” is literally a fine method to place items - but restricted. In my world, they are part of a rock-solid construction. In other words:
They flavor my inline-model.
This is NOT a restriction of FW - it’s simply front-end developing (formerly known as web-design).
It is common to start with the biggest design but if you think “content-first (not to mix with mobile-first)” it’s even clever and exciting to start with the smallest screen (however I haven’t tried it yet in 7).
A Box-In-Box-Model doesn’t have restrictions, it’s up to you to adopt or not. Since years I fight for Inline - with not much of success, though.
Quite simply it is more difficult for the ‘average’ FW user to wrap their head around.
The big advantage that FW7 has brought to that ‘average’ FW user is that they do NOT HAVE to change their construction methods to achieve a responsive site.
In Freeway we can still build a site on two different ways: inline or drag and drop. For a not too fancy site drag and drop can be just fine. Certainly if you have just one breakpoint. At first you build your standard page and then well you have te rearange things on the breakpoint page. For someone who just wants a website which is responsive too, it is a fast and easy task. I do love inline though, but for a ‘simple’ site I would consider drag and drop, just because Freeway made it this easy to create. This is why its shown in the video tutorial I guess.
On the other hand I found it is not that hard to start building inline. I like the way it works: some kind of Lego building feeling! I think no one should be afraid of the whole learning process! It is really not that complicated! Having said that I do think there are gaps to fill on coming updates of FW7. For example a nice way to change fontsizes at breakpoints. In my situation certain fonts have to smaller for phones. It works fine (now) with css on my stylesheet. And I think fontsizes are quite important on responsive websites! Still nobody has been mentioning this here.
Thanks to all for your help and comments. I still have a lot to learn and relearn. I do want to progress to responsive sites. I understand now that I can use inline or the original construction methods. So, I need to start learning - again! Time for some tutorials!