An old topic: Would it be better to hide some buttons when the nutupane is displayed?
A piece of early feedback received during the foreman and katello merge evaluation was that there are cases when the katello UI gets very cluttered with buttons. Attached are two screenshots of adding repositories to a content view. Being slightly distracted this evening (streaming Firefly and promoting content to Production ;), I found myself creating new content views instead of adding repositories.
It seems like a small thing, but hiding some buttons when an item is selected may be helpful to distracted sysadmins.
CV.png is before scrolling down to find repos CV2.png
···
--
@thomasmckay
–
“The leader must aim high, see big, judge widely, thus setting himself apart form the ordinary people who debate in narrow confines.” ~ Charles De Gaulle
“Leadership is about making others better as a result of your presence and making sure that impact lasts in your absence.” ~ Harvard Business School
I agree with you Tom. I can see how after you scroll down, a user can easily click "Create New View" without reading carefully and assume he is adding repositories.
···
----- Original Message -----
From: “Tom McKay” thomasmckay@redhat.com
To: “Kyle Baker” kybaker@redhat.com, “Eric Helms” ehelms@redhat.com,
“Walden Raines” wraines@redhat.com
Cc: foreman-dev@googlegroups.com
Sent: Monday, November 17, 2014 1:20:28 AM
Subject: [foreman-dev] revisiting topic of nutupane buttons
An old topic: Would it be better to hide some buttons when the nutupane is
displayed?
A piece of early feedback received during the foreman and katello merge
evaluation was that there are cases when the katello UI gets very cluttered
with buttons. Attached are two screenshots of adding repositories to a
content view. Being slightly distracted this evening (streaming Firefly
and promoting content to Production ;), I found myself creating new
content views instead of adding repositories.
It seems like a small thing, but hiding some buttons when an item is selected
may be helpful to distracted sysadmins.
CV.png is before scrolling down to find repos CV2.png
–
@thomasmckay
–
“The leader must aim high, see big, judge widely, thus setting himself apart
form the ordinary people who debate in narrow confines.” ~ Charles De Gaulle
“Leadership is about making others better as a result of your presence and
making sure that impact lasts in your absence.” ~ Harvard Business School
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
An alternative solution could be to update the panes so that the action
buttons associated with the pane are not lost when a user scrolls.
The downside of hiding the primary buttons (e.g. Create New View) from
the user is that it makes it more painful for a user that might want to
create multiple objects one right after the other. I have done that in
the past and the mode of create/submit/close is more painful than simply
create/submit. That said, I do not know if that is a common use case or
if others would find that behavior annoying. 
thanks,
Brad
···
On 11/16/2014 06:20 PM, Tom McKay wrote:
> An old topic: Would it be better to hide some buttons when the nutupane is displayed?
>
> A piece of early feedback received during the foreman and katello merge evaluation was that there are cases when the katello UI gets very cluttered with buttons. Attached are two screenshots of adding repositories to a content view. Being slightly distracted this evening (streaming Firefly _and_ promoting content to Production ;), I found myself creating new content views instead of adding repositories.
>
> It seems like a small thing, but hiding some buttons when an item is selected may be helpful to distracted sysadmins.
>
> CV.png is before scrolling down to find repos CV2.png
>
>
>
> An old topic: Would it be better to hide some buttons when the nutupane is
> displayed?
>
> A piece of early feedback received during the foreman and katello merge
> evaluation was that there are cases when the katello UI gets very cluttered
> with buttons. Attached are two screenshots of adding repositories to a
> content view. Being slightly distracted this evening (streaming Firefly
> and promoting content to Production ;), I found myself creating new
> content views instead of adding repositories.
>
> It seems like a small thing, but hiding some buttons when an item is
> selected may be helpful to distracted sysadmins.
>
> CV.png is before scrolling down to find repos CV2.png
>
+1
just for reference, attached how we hide information in foreman currently,
including buttons, pagination etc.
It would also be nice to align btn colors 
Ohad
···
On Mon, Nov 17, 2014 at 1:20 AM, Tom McKay wrote:
–
@thomasmckay
–
“The leader must aim high, see big, judge widely, thus setting himself
apart form the ordinary people who debate in narrow confines.” ~ Charles De
Gaulle
“Leadership is about making others better as a result of your presence and
making sure that impact lasts in your absence.” ~ Harvard Business School
–
You received this message because you are subscribed to the Google Groups
“foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
>
> >
> > An old topic: Would it be better to hide some buttons when the nutupane is
> > displayed?
> >
> > A piece of early feedback received during the foreman and katello merge
> > evaluation was that there are cases when the katello UI gets very cluttered
> > with buttons. Attached are two screenshots of adding repositories to a
> > content view. Being slightly distracted this evening (streaming Firefly
> > and promoting content to Production ;), I found myself creating new
> > content views instead of adding repositories.
> >
> > It seems like a small thing, but hiding some buttons when an item is
> > selected may be helpful to distracted sysadmins.
> >
> > CV.png is before scrolling down to find repos CV2.png
> >
>
> +1
>
> just for reference, attached how we hide information in foreman currently,
> including buttons, pagination etc.
> It would also be nice to align btn colors
>
> Ohad
>
I believe the color compromise has already been implemented and foreman has not yet implemented its side.
···
----- Original Message -----
> On Mon, Nov 17, 2014 at 1:20 AM, Tom McKay wrote:
–
@thomasmckay
–
“The leader must aim high, see big, judge widely, thus setting himself
apart form the ordinary people who debate in narrow confines.” ~ Charles De
Gaulle
“Leadership is about making others better as a result of your presence and
making sure that impact lasts in your absence.” ~ Harvard Business School
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
>
>
> >
> > >
> > > An old topic: Would it be better to hide some buttons when the
> nutupane is
> > > displayed?
> > >
> > > A piece of early feedback received during the foreman and katello merge
> > > evaluation was that there are cases when the katello UI gets very
> cluttered
> > > with buttons. Attached are two screenshots of adding repositories to a
> > > content view. Being slightly distracted this evening (streaming Firefly
> > > and promoting content to Production ;), I found myself creating new
> > > content views instead of adding repositories.
> > >
> > > It seems like a small thing, but hiding some buttons when an item is
> > > selected may be helpful to distracted sysadmins.
> > >
> > > CV.png is before scrolling down to find repos CV2.png
> > >
> >
> > +1
> >
> > just for reference, attached how we hide information in foreman
> currently,
> > including buttons, pagination etc.
> > It would also be nice to align btn colors
> >
> > Ohad
> >
>
> I believe the color compromise has already been implemented and foreman
> has not yet implemented its side.
>
I'm not aware on this, afaiu this was the opposite decision, but instead of
fighting, why would you want foreman to change ? whats lacking? what would
be improved?
thanks,
Ohad
···
On Mon, Nov 17, 2014 at 2:34 PM, Tom McKay wrote:
> ----- Original Message -----
> > On Mon, Nov 17, 2014 at 1:20 AM, Tom McKay > wrote:
–
@thomasmckay
–
“The leader must aim high, see big, judge widely, thus setting himself
apart form the ordinary people who debate in narrow confines.” ~
Charles De
Gaulle
"Leadership is about making others better as a result of your presence
and
making sure that impact lasts in your absence." ~ Harvard Business
School
–
You received this message because you are subscribed to the Google
Groups
“foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send
an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> I'm not aware on this, afaiu this was the opposite decision, but instead of fighting, why would you want foreman to change ? whats lacking? what would be improved?
Is foreman using patternfly? Wouldn't that go a long way to solve these UI consistency issues?
Cheers,
Walden
···
----- Original Message -----
From: "Ohad Levy"
To: "foreman-dev"
Sent: Monday, November 17, 2014 9:29:04 AM
Subject: Re: [foreman-dev] revisiting topic of nutupane buttons
On Mon, Nov 17, 2014 at 2:34 PM, Tom McKay thomasmckay@redhat.com wrote:
----- Original Message -----
On Mon, Nov 17, 2014 at 1:20 AM, Tom McKay thomasmckay@redhat.com > wrote:
An old topic: Would it be better to hide some buttons when the
nutupane is
displayed?
A piece of early feedback received during the foreman and katello merge
evaluation was that there are cases when the katello UI gets very
cluttered
with buttons. Attached are two screenshots of adding repositories to a
content view. Being slightly distracted this evening (streaming Firefly
and promoting content to Production ;), I found myself creating new
content views instead of adding repositories.
It seems like a small thing, but hiding some buttons when an item is
selected may be helpful to distracted sysadmins.
CV.png is before scrolling down to find repos CV2.png
+1
just for reference, attached how we hide information in foreman
currently,
including buttons, pagination etc.
It would also be nice to align btn colors
Ohad
I believe the color compromise has already been implemented and foreman
has not yet implemented its side.
I’m not aware on this, afaiu this was the opposite decision, but instead of
fighting, why would you want foreman to change ? whats lacking? what would
be improved?
thanks,
Ohad
–
@thomasmckay
–
“The leader must aim high, see big, judge widely, thus setting himself
apart form the ordinary people who debate in narrow confines.” ~
Charles De
Gaulle
"Leadership is about making others better as a result of your presence
and
making sure that impact lasts in your absence." ~ Harvard Business
School
–
You received this message because you are subscribed to the Google
Groups
“foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send
an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups “foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> > I'm not aware on this, afaiu this was the opposite decision, but instead
> of fighting, why would you want foreman to change ? whats lacking? what
> would be improved?
>
> Is foreman using patternfly? Wouldn't that go a long way to solve these
> UI consistency issues?
>
IMHO lets not mix things, we are talking about btn positions and hiding
parts on master - details views ?
foreman upstream patternfly PR reached an impasse, we can try to revive it
regardless.
Ohad
···
On Mon, Nov 17, 2014 at 4:59 PM, Walden Raines wrote:
Cheers,
Walden
----- Original Message -----
From: “Ohad Levy” ohadlevy@gmail.com
To: “foreman-dev” foreman-dev@googlegroups.com
Sent: Monday, November 17, 2014 9:29:04 AM
Subject: Re: [foreman-dev] revisiting topic of nutupane buttons
On Mon, Nov 17, 2014 at 2:34 PM, Tom McKay thomasmckay@redhat.com wrote:
----- Original Message -----
On Mon, Nov 17, 2014 at 1:20 AM, Tom McKay thomasmckay@redhat.com > > wrote:
An old topic: Would it be better to hide some buttons when the
nutupane is
displayed?
A piece of early feedback received during the foreman and katello
merge
evaluation was that there are cases when the katello UI gets very
cluttered
with buttons. Attached are two screenshots of adding repositories to
a
content view. Being slightly distracted this evening (streaming
Firefly
and promoting content to Production ;), I found myself creating new
content views instead of adding repositories.
It seems like a small thing, but hiding some buttons when an item is
selected may be helpful to distracted sysadmins.
CV.png is before scrolling down to find repos CV2.png
+1
just for reference, attached how we hide information in foreman
currently,
including buttons, pagination etc.
It would also be nice to align btn colors
Ohad
I believe the color compromise has already been implemented and foreman
has not yet implemented its side.
I’m not aware on this, afaiu this was the opposite decision, but instead of
fighting, why would you want foreman to change ? whats lacking? what would
be improved?
thanks,
Ohad
–
@thomasmckay
–
"The leader must aim high, see big, judge widely, thus setting
himself
apart form the ordinary people who debate in narrow confines." ~
Charles De
Gaulle
"Leadership is about making others better as a result of your
presence
and
making sure that impact lasts in your absence." ~ Harvard Business
School
–
You received this message because you are subscribed to the Google
Groups
“foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it,
send
an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google
Groups
“foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send
an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
