Skip to content

Discussion: Style 'add note' as button #44

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

Closed
Henni opened this issue Jan 5, 2017 · 10 comments
Closed

Discussion: Style 'add note' as button #44

Henni opened this issue Jan 5, 2017 · 10 comments
Assignees
Labels
enhancement New feature or request

Comments

@Henni
Copy link
Member

Henni commented Jan 5, 2017

Should we style the 'add note' action like a button? This would align notes to other apps like contacts:

see also:
#42 (comment)

cc @nextcloud/designers

@skjnldsv
Copy link
Member

skjnldsv commented Jan 5, 2017

Yes, we should aim to uniform designs :)

@MariusBluem
Copy link
Member

👍

@jancborchardt
Copy link
Member

I agree with this, yes. It makes the primary action clearer and we do this in Contacts & Mail as well. (And to some extent in Files and Calendar)

@jancborchardt jancborchardt added the enhancement New feature or request label Jan 14, 2017
@Henni Henni self-assigned this Jan 14, 2017
@Henni
Copy link
Member Author

Henni commented Jan 14, 2017

Looks like we currently don't have a .primary-button style in core.
I think we should change that so that we can reuse it in contacts, mail and here in notes.

@skjnldsv
Copy link
Member

I completely agree.
Should be in apps.scss. A #app-navigation > .primary-button-container > button.primary-button?

  • Mail has its button inside a div
  • Contacts has it inside a custom element (which a class can be easily applied)
  • Calendar has 3 buttons (previous, month and next) maybe we should uniform the .primary-button-container with some flexbox to be compatible with that too?

@Henni
Copy link
Member Author

Henni commented Jan 14, 2017

I would ignore calendar and just define a simple primary button.

A wrapper element like .primary-button-container shouldn't be necessary. And maybe we should even remove #app-navigation to allow primary buttons in the app-content.

Also: Do we only want button or also input[type=button]?

@skjnldsv
Copy link
Member

Since every app is using a wrapper, it could be useful to think twice about it.
I agree with you, this isn't necessary, but I like the idea of a unified buttonS wrapper wich include calendar.

@jancborchardt
Copy link
Member

We do have .primary though, as used by the log in button and the main button of the file picker, and in the Calendar app for event saving, and in Mail for send and reply button. :) So that should be used.

@jancborchardt
Copy link
Member

This is fixed, we now have a nice button there. :)

@jancborchardt
Copy link
Member

Thanks to @andreasjacobsen93 who fixed it in #108 ;)

korelstar pushed a commit that referenced this issue Apr 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants