-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Child Association Headers suggestion #16
Comments
Something to think about.
Just so we are talking about the same thing: we do have an icon. A page icon. You don't seek something more visual, you're just not convinced that the metaphore works. Right? :) |
Thanks Nils, Breadcrumbs are a good thing in this instance yes, I just feel it takes up a lot of real estate at present. With regards to the icon, is it worth a text prompt/tooltip or something? we have Or does that look too much like a menu icon now? |
Personally, I have to say that I'm not fond of a drag indicator at all. We don't use it in the Symphony interface and the user already gets a drag cursor. If you have to explain to your users what the drag cursor means, you'll also have to explain to them what a drag indicator means. Additionally, if you have a drag indicator, people tend to think that that's the only area that can be used to drag, which is wrong – it works on the entire row. So for me it's already a design compromise to have it in the interface at all.
It does look like this at your place, does it? |
Nope... So there in lies the problem then :) I don't see that icon at all! missing svg maybe? using Chrome on mac. |
A different idea: How about making the caption a link which opens the editor? Much like it works in the section overview. |
Ha, okay. |
It's always the little things :) |
The thing is: it works just fine in Chrome here. Strange. It's an SVG image. |
And to further clarify things: |
Andrew, can you check, if you see the icon in other browsers? |
I'll check now. |
I don't see the icon in Chrome: Version 36.0.1985.125 on OSX Mavericks |
Let's move here: #17 |
Regarding the child headers, let's consider this for version 1.1.0. |
Agree. |
Hi Nils,
Looking at the UI as it stands, I think it's looking and feeling great. I still think that an icon/more visual prompt to edit should be considered. Will get me thinking cap on to suggest one or two things here.. I know Icons aren't really the Symphony way so it needs to fit into the current scheme of UI presentation.
The other thing that has cropped up for me is the depth issue when you have a child association which in turn has it's very own association:
We really do lose quite a bit of screen real estate when it goes deeper. What if we collapsed the UI down to a minimum for nested associations and used something similar to the below to navigate back up the tree?
Just a thought really.
The text was updated successfully, but these errors were encountered: