This past week, the Red Hat katello developers gathered in Raleigh, NC to discuss past releases and future tech directions. A brief topic touched was UI style.
There are a category of bugs and complaints against katello/foreman that the vertical screen waste (whitespace areas that push useful details too far down the page) needs to be reduced. Based on ideas tossed about, a quick hack to katello's pages was demonstrated. As I watched it seemed that the changes were very much in line with foreman's look and feel. One was an option to hide the left hand master list when viewing details. Another was to get rid of infinite scroll and move to a paged model. Grouping of actions into a dropdown instead of individual buttons. Finally, there seemed to be some pages that would benefit to the vertical tabs like the org/loc pages have.
As we look forward to the coming releases over the next year, would now be a good time to get the UI devs together to discuss strategy on UI tech and implementation? Is there someone that would be willing to investigate this? (Perhaps start a github RFC.)
Thanks!
···
--
@thomasmckay
>
> This past week, the Red Hat katello developers gathered in Raleigh, NC to discuss past releases and future tech directions. A brief topic touched was UI style.
>
> There are a category of bugs and complaints against katello/foreman that the vertical screen waste (whitespace areas that push useful details too far down the page) needs to be reduced. Based on ideas tossed about, a quick hack to katello's pages was demonstrated. As I watched it seemed that the changes were very much in line with foreman's look and feel. One was an option to hide the left hand master list when viewing details. Another was to get rid of infinite scroll and move to a paged model. Grouping of actions into a dropdown instead of individual buttons. Finally, there seemed to be some pages that would benefit to the vertical tabs like the org/loc pages have.
>
> As we look forward to the coming releases over the next year, would now be a good time to get the UI devs together to discuss strategy on UI tech and implementation? Is there someone that would be willing to investigate this? (Perhaps start a github RFC.)
We're discussing how it's best to come around this and basically we're
stuck deciding a way to package assets (more than 1 will be a PITA). RFC
incoming soon I guess.
As for the UI tech, I think the point of http://patternfly.org/ is
precisely to provide the guidelines we should use. Granted we don't
fully do it yet, but it'd be the goal.
···
On 05/09, Tom McKay wrote:
Thanks!
–
@thomasmckay
–
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.
–
Daniel Lobato Garcia
@dLobatog
blog.daniellobato.me
daniellobato.me
GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato
