Hi Everyone, I’m still trying hard to understand what I’m doing in trying to work with the box model/inline/responsive layout models. I see much promise in them, if I could only get reproducable/predictable results.
Current issue, I have a sample work-in-progress webpage that works for the header and footer areas. Where the responsive model isn’t working, is in the middle, the 3 columns I have setup for the body of the webpage. I would like the text in each column to resize as one changes the width of the browser in Preview, they do not. I would expect the columns to resize and as the window is shrunk down to stack above each other.
Also, I’ve seen where graphics resize in some examples of responsive design, I do not see how to get, for example the header graphic to resize, nor the graphics inline in the body area columns.
I’ve created the three column by using percentages in all the columns to get something that would display three columns, if there’s another/better way to create 3 columes, please advise!
Also, feel free to download the demo version of Backdraft. It comes with the two-column and three-column module that you can dissect/replicate/use. You can also see the responsive CSS for it by going to Page > HTML Markup > Before from within FW.
Your instructions on flexible width images was superb - thank you!
I’ve also updated the web page with the suggested change to the pagecontent element. It looks better when shrunk to an iPhone size but the right column doesn’t break below the middle column. Still working to get columns more predictable, not sure if it’s something to do with breakpoints or something else. Also the column spacing and separation between them seem to be not quite predictable or as I want them. I don’t always want three equally sized columns, sometimes it’s 20% - 50% - 30% or other variations.
I’ve also updated the web page with the suggested change to the pagecontent element. It looks better when shrunk to an iPhone size but the right column doesn’t break below the middle column.
Cause it’s set to “float right” and it never will change its attitude as long …
Still working to get columns more predictable, not sure if it’s something to do with breakpoints or something else.
… you do not tell this buddy to do, using the @media query (breakpoints).
Also the column spacing and separation between them seem to be not quite predictable or as I want them. I don’t always want three equally sized columns, sometimes it’s 20% - 50% - 30% or other variations.
Much appreciate the assist – Lewis
You’re on a good way, Lewis - so this note is more for other followers (a case of lil self-advertising):
Naturally it is a good thing to challenge all stuff on your own, however think of some little help (even paid) to get the basics taught. This could shorten up the work to get more concentrated on other things such as design (time is money). I did long ago, others did as well. And there is help - not far away.
In looking at Caleb’s sample template, it looks like one needs the CSS coding at Page > HTML Markup > Before to do the breakpoints. Seems to me there might be another way?
I appreciate Thomas’ comments, but find no specific help or directions in resolving the questions I have, other than “buy my instructions”. I am trying to struggle through doing this to learn and understand what’s going on, but find I do need some input.
I would love to see Softpress issue some guidance and detailed instructions about achieving in-line/box model/responsive web modeling as it IS possible in Freeway, but not without some specific information and tweaking. I would also love to see Softpress really embraced and enhance this model and incorporate being able to do it more easily in Freeway Pro in the next version updates. Perhaps even including some of these model templates with FR would be a start, please some instructions, please!
So much is already freely given away, yet it’s not enough. Never enough.
That is the truth of what happened to Dan Jasker.
If you’ve been given all the help you can get and it’s not enough, then buy
it. Softpress didn’t invent the inline/box-model technique or responsive
design, and they aren’t the ones dishing out free help and support here.
Support the people who support you.
I don’t think asking for documentation is too much. Nor do I think suggesting that Softpress embrace and make using these design models easier is too much either. There are upcoming programs like McCaw that could take away Freeway business, if it falls behind or doesn’t keep up with current web trends/needs. So far, Freeway Pro is a terrific solution!
I’ve bought Dan Jasker’s offerings, so don’t lecture me about supporting those ‘who support’, and I’ll likely buy offerings from Caleb and Thomas, if I think their offerings will advance my efforts. I’m trying to get to that point where I think this is worth pursuing.
I don’t think you should chastise users who want better products and better documentation. Things can always use improvement and to stifle suggestions is really counterproductive to the ongoing success of a product.
I think it’s safe to say Ernie wants an improved Freeway as much as anyone. But it seems to me that his reply (correct me if I’m wrong, Ernie) was more of a general frustration about how the overwhelming majority of help is generously given by a precious few people free-of-charge, and how sometimes when things are constantly given freely expectations go up and appreciation/value goes down. Honestly, I don’t think it was intended to be personal, Lewis.
Freeway has struggled to keep pace with the changing landscape for a very long time. Macaw might be the latest competition, though to me the biggest threat to Freeway’s survival has always been Freeway/SP.
Todd
There are upcoming programs like McCaw that could take away Freeway business, if it falls behind or doesn’t keep up with current web trends/needs.
I’ve given away more value here than you have - though you are free to
change that.
You want Softpress to document a way of using their product they didn’t
invent or pursue… good luck with that. Many are still waiting for FWP to be
fully documented. Your tone is becoming ungrateful and obnoxious… and I
realize that I’m not the paragon of sweetness myself - most of us put in
many hours of community service here, and when we ask for support we
usually put it all back into the community. That you have come this far is
fair testament to how that is working.
So be grateful for the amazing amount of (free) support there is already
here for you… Buy the templates. Subscribe to the lessons. Complete your
journey and then dedicate yourself to giving back. Who knows, maybe one day
you’ll make an amazing template or action that you can sell for peanuts and
then see how this conversation looks from the other side.
In looking at Caleb’s sample template, it looks like one needs the CSS coding at Page > HTML Markup > Before to do the breakpoints. Seems to me there might be another way?
The only way to do responsive layouts with FW is to hand-code the CSS breakpoints, that kind of functionality is not in FW (and probably won’t be anytime soon). You don’t have to put the CSS in the tag, it’s actually preferable to use an external stylesheet.
If you want to know how to create responsive websites in Freeway, you must be able to hand-code responsive websites. Learn HTML & CSS, and learn them well. Freeway is still a hostile environment for this kind of work, so you need to have that background knowledge.
Codecademy is a good, free, resource to learn the fundamentals of those languages. Check it out, and devote an hour a day to learning this stuff. If all goes well, within several months you should be able to bring your knowledge to Freeway and force it to obey your will.
Shortly after that, you’ll find that it’s actually easier - and faster - to hand-code a responsive website than it is to work with FW. But then you’ll discover that you need to learn Javascript and jQuery to replace some of the actions, so back you go to spending a disproportionate amount to time trying to learn this stuff.
Your social life will consist of running to the grocery store, and your best friends will be your keyboard and headphones. Coffee is life, and sleep is a luxury.
A Freeway manual will teach you the app and its use, the rest is written in “The Black Book of FreewayPro or what you never wanted to know”. I’m part of the black side of life and long started to cover the message of the unnamable.
My bible?
Cheers
Thomas
(Written today in the early 2014 - things may change
Hi Todd, thanks for your guidance of temperance, though I do take offense that the only non-helpful, non-constructive posts to my questions is one from someone who appears to be a frustrated, bitter individual who seems to feel their input on these forums is under-appreciated, under-valued and that he has not been monetized enough for his efforts. Funny I missed the notice one should expect to pay for any real help on these forums. This obnoxious standing on one’s soapbox is bullying enough to discourage those of us who want to ask questions and make suggestions of things we’d wish for to make Freeway an even better program than it is now.
I have been grateful and thankful for the helpful responses from Caleb and Thomas, and they both have followed up with more detail and more information. I’ve used the words “superb”. “thank you”, and “much appreciate the assist” and “appreciate Thomas’ comments”.
I am still trying to determine if I can/should use the inline/box model/responsive design: 1). to be sure I can predictably change a layout without things going all to heck. 2). to be able to use unequal sized odd number of columns and have them break properly for responsive design. At such a point, as I said above, will likely purchase offerings from Caleb and Thomas.
Again, my gratitude for those that have made efforts to stay on track and simply offer help and answers.
It sounds to me, you have two choices for a responsive design. One, learn to code it. Probably with the (paid) help of Thomas’s vids. Or, two, buy Caleb’s templates. It sound like he’s done all the heavy lifting and you just jhave to customize which sounds like Caleb is more than willing to help folks with.
On a personal note, I have relied HEAVILY on the generosity of the folks on this forum. I have dozens of FREE Actions that I simply could not have gotten the job done without.
I have purchased a few Actions and have also purchased the inline/WebYep tutorials from Dan which were INVALUABLE as he builds an entire site from scratch.
I’m on a very limited budget, so I appreciate all the free help. I wish I could contribute more (I’ve contributed a pittance to help with the new and improved Actions Forge.
OK. My long winded point is, folks around her are the most helpful I’ve run across. It is frustrating when you’re stuck and can’t get the answer you want, but these folks will never steer you wrong.
Sorry appears I’m always late to a discussion these days…
There’s a massive difference to an “Instruction Manual” and a “Advanced Training Guide”. An Instruction Manual that is bundled free with a product might say “Add oil here” and “select the gear 1-4 here using the gear stick”. It would never cover “how to change the gearbox” or “how to chop and lower the car” or “how to drive the Nürburgring ring in under 9 seconds”.
I think the expectation for the Free Softpress Manual to do anything more that the “basic stuff” is way, way beyond reasonable. The Softpress Manual a starting point for your adventure into Web Design.
If you plan to make a career from web design then you will work hard to learn how it all works and realise you actually never stop learning, and there’s no quick fix. Some will fall by the wayside. If you’re not making a career in web design then just realise there is no Free lunch and good advice and tools to make things easier come at a price. Or even ask Ernie to design/build it for you. He would do a darn good job.
For me the recent responsive CMS sites I’ve built are the culmination of several techniques and hard won experience (and of course many mistakes) building over many years. There’s still a way to travel.
(I’m sure the word “grasshopper” should have been in there somewhere)
–
David Owen
On 5 Feb 2014, at 19:21, Robert B email@hidden wrote:
