Conversation
c3c3c8a to
28475d4
Compare
| t('Add Contact'), | ||
| 'notifications/contacts/add', | ||
| t('New Contact'), | ||
| 'noma/contacts/add', |
|
|
||
| public function indexAction(): void | ||
| { | ||
| $this->content->getAttributes()->add(['class' => 'full-width']); |
There was a problem hiding this comment.
Please move this to the bottom where the list is added to the content.
There was a problem hiding this comment.
✅
Also did this for the other occurrences:
- IncidentsController
- EventsController
| $this->addTitleTab(t('Add Event Rule')); | ||
| $this->getTabs()->setRefreshUrl(Url::fromPath('notifications/event-rules/add')); | ||
| $this->addTitleTab(t('New Event Rule')); | ||
| $this->getTabs()->setRefreshUrl(Url::fromPath('noma/event-rules/add')); |
| 'notifications/event-rules/add', | ||
| 'plus' | ||
| ))->setBaseTarget('_next') | ||
| ->addAttributes(['class' => 'new-event-rule']) |
There was a problem hiding this comment.
Please also remove the class then
| public function indexAction(): void | ||
| { | ||
| $this->addTitleTab(t('Events')); | ||
| $this->content->getAttributes()->add(['class' => 'full-width']); |
There was a problem hiding this comment.
to the bottom where the list is added please
| public function indexAction(): void | ||
| { | ||
| $this->addTitleTab(t('Incidents')); | ||
| $this->content->getAttributes()->add(['class' => 'full-width']); |
| [ | ||
| new Icon('plus'), | ||
| t('Add new entry') | ||
| t('Add Entry') |
There was a problem hiding this comment.
You've standardized it everywhere else to New ..., why not here??
There was a problem hiding this comment.
So the idea behind this is:
- You create/delete an Object (e.g. "New Schedule”), when you’re in the “schedules” views (Create)
- You add/remove “entry" objects to that “schedule", when you’re in the “schedules” view (Create and link)
This helps
- to clarify the different relations and
- with distinguishing the different actions better, especially in a view with many buttons in the same design
I decided against additionally highlighting the “add entry” button as a primary button, because it’s not that important in that view and would distract from the actual content which is the schedule itself.
There was a problem hiding this comment.
Ah, okay, but I also add a new rule to the list of already existing event rules. I also add a new contact to the list of available contacts. In both cases, the relation is the list on the left. And to a list you add new items. The perfect label would be Add New Contact, but that's a bit redundant IMHO.
So if you think Add Entry is fine on the schedules view, I don't understand why you think Add Contact is not, on the contacts list.
There was a problem hiding this comment.
Yes, don't you see the difference?
contact (list): new contact
schedule (list): new schedule
schedule: add entry
Not sure, how to make it clearer.
It also helps clarify the difference when there's that many different buttons of the same style, as shown on the screenshot.
I agree on the redundancy, especially as it doesn't add any value and distracts from the actual important term "Contact".
I don't want to discuss this to death. If you insist or it doesn't make sense to you, we can label it "+ New Entry".
There was a problem hiding this comment.
Everything you've added in here should be moved to Icinga Web 2. Add it there to forms.less please.
While you do that, please make btn-default a standalone class (should not require btn-cancel). This should also solve the issue that once again there are no focus styles!
There was a problem hiding this comment.
✅ As discussed “offline”, I dropped the custom styles for .form-controls.
69643e2 to
4b33a04
Compare





Fixes some minor style and ui issues: