I can't figure out how rows and columns work.
What is the difference?
When I add a row, it appears that it is immediately treated as a column. So what's the point of a row?
I add a row, then look at properties and it shows it as a column.
It appears that a row is just a full width column, then you can change the width of the column. I don't get the point of rows.
The only thing I can see is that when I add a new row, it goes below all of the others, and can't be moved up even if I make it 6 spans when the one above is 6 spans. It remains as a separate row, but is still labeled as a column. I'm confused....
What is the difference?
When I add a row, it appears that it is immediately treated as a column. So what's the point of a row?
I add a row, then look at properties and it shows it as a column.
It appears that a row is just a full width column, then you can change the width of the column. I don't get the point of rows.
The only thing I can see is that when I add a new row, it goes below all of the others, and can't be moved up even if I make it 6 spans when the one above is 6 spans. It remains as a separate row, but is still labeled as a column. I'm confused....
When I add a row, it appears that it is immediately treated as a column. So what's the point of a row?
A row is made of of columns. Every Element has a column, every column has a row and every row has a column.
The only thing I can see is that when I add a new row, it goes below all of the others, and can't be moved up even if I make it 6 spans when the one above is 6 spans. It remains as a separate row, but is still labeled as a column. I'm confused....
You are adding a row. Think of it like a table. You have Table which is the grid, you have a TR which is the Row, and you have TD which is the column inside the TD you place your content.
So in responsive language that means, Grid > Row > Column > Element (content).
If you want two TD's (Columns) together you place them in the same TR (Row).
Does that helps?
I think I'm getting it.
A row takes up the full width of the grid, then 1 or more columns are place on (in) the row, into which the elements are placed. It threw me for a while when I added a row and it immediately looked like a column except for the fact that it wouldn't move up or down.
It helps to think of it as a table. That makes sense to me now. I've been playing with RLM for the first time this evening and it's a bit of a learning curve.
Thanks for your quick and helpful response.
A row takes up the full width of the grid, then 1 or more columns are place on (in) the row, into which the elements are placed. It threw me for a while when I added a row and it immediately looked like a column except for the fact that it wouldn't move up or down.
It helps to think of it as a table. That makes sense to me now. I've been playing with RLM for the first time this evening and it's a bit of a learning curve.
Thanks for your quick and helpful response.
There is no real learning curve with RLM. It is code, just as you would find in HTML Editor.
You just have to have that "AHA!"moment where it all clicks and you say, why did I not see this before!
You just have to have that "AHA!"moment where it all clicks and you say, why did I not see this before!
Adam East wrote:
There is no real learning curve with RLM. It is code, just as you would find in HTML Editor.
You just have to have that "AHA!"moment where it all clicks and you say, why did I not see this before!
There is no real learning curve with RLM. It is code, just as you would find in HTML Editor.
You just have to have that "AHA!"moment where it all clicks and you say, why did I not see this before!
I don't agree with this. There certainly is a learning curve. You need to figure out what all the properties of the various elements do, and also how you can achieve what you want. It has taken me some time, and I'm still not on top of it (but getting closer).
Like havng a different background colour for a sidebar and make it stretch down full length. In normal coding it can be done by setting the height in %, but in RLMP there isn't such a setting, so it is necessary to find a workaround. I've been working on that now for a week, and last night, as I couldn't sleep, I got up again and finally found out what to do.
And I slept well after that.
Ha en riktig god dag!
Inger, Norway
My work in progress:
Components for Site Designer and the HTML Editor: https://mock-up.coffeecup.com
Inger, Norway
My work in progress:
Components for Site Designer and the HTML Editor: https://mock-up.coffeecup.com
Adam East wrote:
There is no real learning curve with RLM. It is code, just as you would find in HTML Editor.
You just have to have that "AHA!"moment where it all clicks and you say, why did I not see this before!
There is no real learning curve with RLM. It is code, just as you would find in HTML Editor.
You just have to have that "AHA!"moment where it all clicks and you say, why did I not see this before!
Not being a little condescending there a little, old chap of course there's a learning curve if there wasn't why is there that there's so many questions from experienced and the not so experienced. Generally speaking when you have a powerful program there is a learning curve.
However I do agree with you that it's like looking at rows and columns like tables that's what I've being thinking as the best way to see them.
http://www.dozydayz.co.uk
http://nbdesigns.me.uk - responsive
http://brewstersartz.co.uk - responsive
http://nbphotography.me.uk - responsive
http://nbdesigns.me.uk - responsive
http://brewstersartz.co.uk - responsive
http://nbphotography.me.uk - responsive
EEEKK Tables.... Eric he said the "T" word!
Taking over the world one website at a time!
Steve Kolish
www.misterwebguy.com
YouTube Channel:
https://www.youtube.com/channel/UCL8qVv … ttneYaMSJA
Steve Kolish
www.misterwebguy.com
YouTube Channel:
https://www.youtube.com/channel/UCL8qVv … ttneYaMSJA
When that aha moment comes you will know what I am talking about.
@Inger - You said you have to figure out what the properties for the elements do. The properties are the same properties you have been working with in regular HTML. Margin, Padding, width, etc. Granted there are some new ones, but most of them have been around since 1998, we just have not been using them.
The background issue you spoke of, could have been fixed once you exported the code or within RLM. Remember there are several different ways to accomplish the same thing in code. But the point I am getting at is, it was not RLM that forced you to find a new way to accomplish this, it was responsive design. As we have been saying, responsive is a new way of thinking.
@G'kar- A friend of mine once told me, "The only limitation placed on what you can achieve is the limitation you place on yourself."
@Inger - You said you have to figure out what the properties for the elements do. The properties are the same properties you have been working with in regular HTML. Margin, Padding, width, etc. Granted there are some new ones, but most of them have been around since 1998, we just have not been using them.
The background issue you spoke of, could have been fixed once you exported the code or within RLM. Remember there are several different ways to accomplish the same thing in code. But the point I am getting at is, it was not RLM that forced you to find a new way to accomplish this, it was responsive design. As we have been saying, responsive is a new way of thinking.
@G'kar- A friend of mine once told me, "The only limitation placed on what you can achieve is the limitation you place on yourself."
Adam East wrote:
@G'kar- A friend of mine once told me, "The only limitation placed on what you can achieve is the limitation you place on yourself."
@G'kar- A friend of mine once told me, "The only limitation placed on what you can achieve is the limitation you place on yourself."
I'm sure he did Adam, but that has nothing to do with what were talking about
http://www.dozydayz.co.uk
http://nbdesigns.me.uk - responsive
http://brewstersartz.co.uk - responsive
http://nbphotography.me.uk - responsive
http://nbdesigns.me.uk - responsive
http://brewstersartz.co.uk - responsive
http://nbphotography.me.uk - responsive
Inger wrote:
I don't agree with this. There certainly is a learning curve. You need to figure out what all the properties of the various elements do, and also how you can achieve what you want. It has taken me some time, and I'm still not on top of it (but getting closer).
Like havng a different background colour for a sidebar and make it stretch down full length. In normal coding it can be done by setting the height in %, but in RLMP there isn't such a setting, so it is necessary to find a workaround. I've been working on that now for a week, and last night, as I couldn't sleep, I got up again and finally found out what to do.
And I slept well after that.
I don't agree with this. There certainly is a learning curve. You need to figure out what all the properties of the various elements do, and also how you can achieve what you want. It has taken me some time, and I'm still not on top of it (but getting closer).
Like havng a different background colour for a sidebar and make it stretch down full length. In normal coding it can be done by setting the height in %, but in RLMP there isn't such a setting, so it is necessary to find a workaround. I've been working on that now for a week, and last night, as I couldn't sleep, I got up again and finally found out what to do.
And I slept well after that.
Inger - so how did you do a work around to get it to stretch down full length?
I've struggled a bit not seeing a height settings as well. Maybe that's something you just do in the html after exporting?
Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.