Skip to content
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

UI inconsistency on configuration modals #518

Open
hvelarde opened this issue Apr 27, 2015 · 12 comments
Open

UI inconsistency on configuration modals #518

hvelarde opened this issue Apr 27, 2015 · 12 comments
Labels

Comments

@hvelarde
Copy link
Member

when configuring a tile we have a title on the modal and Save and Cancel buttons:

configure tile

when configuring a row or column we have no title on the modal and no Save and Cancel buttons, but a close modal one:

configure row and column

this also relates to #127

@djowett
Copy link
Contributor

djowett commented Apr 28, 2015

Also "Choose Class" should be "Choose Class for Column" or "Choose Class for Row" depending which icon you clicked. (Note they are quite close together)

@djowett
Copy link
Contributor

djowett commented Apr 28, 2015

The lack of Save & Cancel buttons is to do with the implementation choice for fixing 284 - it was done with JQuery, if you want Save & Cancel buttons then you probably want a Schema interface as done in branch issue_284_a - but that was a bit slower to run.

Note the column size popup doesn't have Save or Cancel buttons either.

I'm not saying I disagree with you here, just making points!

@hvelarde
Copy link
Member Author

we need to use one consistent UI in the package; I don't like the lack of Save and Cancel buttons

@djowett
Copy link
Contributor

djowett commented May 14, 2015

@hvelarde Just coming back to this... I don't like the lack of Save & Cancel buttons either...

Also this "Choose Class" requester doesn't save unless you click the "Saved" button on the main page after closing the requester.

@rodfersou any thoughts?

@hvelarde
Copy link
Member Author

@djowett mmm, that's bad and we need to fix it before the release of the feature will be useless.

right now we are doing some work on another package but we'll be back soon on this.

I think I'm going to create the branch to remove the carousel tile in the following days.

@rodfersou a good article about the topic http://www.nngroup.com/articles/efficiency-vs-expectations/

@hvelarde hvelarde modified the milestones: 1.0b1, 1.0b2 May 14, 2015
@rodfersou
Copy link
Member

@hvelarde @djowett agree to have consistent UI here, we should look into the resize tile button too, it uses the same jquery ui package and saves just the same way the class configuration does.

@rodfersou
Copy link
Member

I didn't change it before because I need to learn better how prep overlay works..

@djowett
Copy link
Contributor

djowett commented May 21, 2015

Just checking up further on my statement above:

Also this "Choose Class" requester doesn't save unless you click the "Saved" button on the main page after closing the requester.

@rodfersou you are correct that this is not different to the resize tile button, however the resize tile button DOES highlight this by changing the "Saved" button to "Save".
I think all that's required to make this work is adding

 le.trigger('modified.layout');

somewhere after:

 $(document).on('change', '#class-chooser select', function(e) {

But I would like your thoughts on that.

@rodfersou
Copy link
Member

@djowett I didn't notice that, I think it is easier to change button name first, and after we can replace all dialogs

@hvelarde do you think it is fair enough follow this path?

@djowett
Copy link
Contributor

djowett commented May 21, 2015

@rodfersou le.trigger('modified.layout'); will change the button name for you.

@rodfersou
Copy link
Member

@djowett 👍

@hvelarde
Copy link
Member Author

@rodfersou it's fair for now, but we need to inform the user that changes have been made if she tries to leave the page without saving the layout

@hvelarde hvelarde modified the milestone: 1.0b1 Oct 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants