This discussion of whether to update to 7 or not has been so interesting. It has made me decide to stick with Plan A and use the site in a different way, to simplify things for me. I do not want to spend squillions of hours in front of the screen adapting or completely recreating the site - I can’t do that anymore after the damage that the ophthalmologist did to one of my eyes a few weeks ago and it is more important for me to save screen time to keep publishing.
Thanks for the info on RPL and yes, I sometimes find problems with overlapping and having to sort that out. So is the question of using tables, widths and heights in percentages.
All food for thought before leaping ahead.
Elizabeth
On 5 Nov 2014, at 8:37 pm, Thomas Kimmich email@hidden wrote:
Really - how? You refer to just visual layout, and reorganizing for different sizes via breakpoints maybe? Or something else? Responsive without Inline Construction would be an interesting side discussion!
Maybe yes, however it could be a pretty short one.
Caveat
RelativePage Layout Action doesn’t work anymore within 7’s new responsive features. So you can’t prevent yourself from “overlapping” items just by set-and-forget.
Conclusion
In fact it works, cause you can deal with changing x/y position (absolute) at a certain breakpoint as well or technical spoken, you can cascade all CSS properties whenever, however you like.
But consider, that items can overlap - not only in one browser (as in the past), it can happen on every device and every OS to any time.
“The control which designers know in the print medium, and often desire in the web medium, is simply a function of the limitation of the printed page. We should embrace the fact that the web doesn’t have the same constraints, and design for this flexibility. But first, we must 'accept the ebb and flow of things.”
####John Allsopp, “A Dao of Web Design”*
This has been written in April 2000!!!
Absolute positioning as being the number one choice of construction is simulating print and is as successful as using tables.
And should I use tables for construction purposes?
http://shouldiusetablesforlayout.com
With FW7 I took it as a cue to force myself to start thinking differently and try to learn inline (box model) construction as my default approach for the foreseeable future. There are just too many tablet and phone surfers to ignore.
Which is EXACTLY the right track to go.
Elizabeth - to go to a responsive inline layout you would pretty much be building a different type of framework and plugging your original data into it. It’s not so easy as moving a few things around or ticking some boxes. There is a learning curve and it is no longer the original visual layout at that point.
Yes, yes and yes again. And this has NOTHING to do with the application you use, this is FrontEnd development today. In short:
A fluid grid
Good news is there are many resources to learn this and some templates (at extra cost) to learn from as well.
But back to the OP question:
The above exactly explains why it is hard to tell people if a layout breaks or not by upgrading to a higher version. In my world (usually) nothing breaks because
a) I don’t use much actions
b) my widths and heights are declared in percentage
But I heard other things. For exactly this reason I recommended to proper back-up current things (never change a running system) and start to try (as I did in my first post of this list).
As long as you don’t touch any item on pages you don’t like to adjust - nothing happens - they stay rock solid as before.
So you can indeed just start with one page (articles or whatever) within you project making it “responsive”.
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options