Observations on using Rf for app prototype

Question

Been working with Rf for about 2 months on prototyping a web app. I've been able to create a responsive prototype that shows the developers -exactly- how it should look on different screens, which is great!
However, the most frustrating thing is for the non-programmer to understand "Position" types. I have to use a lot of trial and error to get objects to adjust in a logical manner.
Trying to get the page to do simple adjustments can take hours (especially if you have several objects on the page) because one wrong setting on a single object can mess up the whole page.
I don't understand the logic of how an object is related to another object: Text block top margin is related to the rule above, but another text block's top margin is related to a totally different object??? How is this determined? Can I change this?
It would be nice to have a view (maybe called Responsive View?)--similar to Show Object Edges, but includes (margin, padding, floating relation to other objects, etc.) so one can "design" the responsiveness as we design the layout.
Responsive View could show relationships between objects with small icons (chainlink, rubber band, etc.) and allow you to change those settings by clicking on the little icons...
I think this would be a great feature since a lot of what designers are spend more time on is how to make each screen size look ideal.
Here are some other observations:
- Placing a new object is tedious because it can mess up the layout. They should be set with default settings that don't affect other objects.
- objects loose their settings when a new object is placed.
- objects change Margin setting of Auto to % when they are nudged or a new object is placed. 
- if two buttons are grouped I expect them to act as a single object when the window is resized.
- would be nice to have a table tool

Answer 1

The only problem I thought I saw with doing something like:
MyProps.getInt("age");
Would be that you have all of these hardcoded strings throughout your code. Also, if you make a typo it could create a few run-time bugs. I considered making a static variable and using it like this:
MyProps.getInt(MyProps.AGE);
If I needed to also make a small tweak to the actual property name, I only have to change it in one place.
public static String AGE = "newage";
I guess this really is only useful if you anticipate you may change some of the wording, which probably isn't that common.