New UI ideas

[mrgeorgegray]

New UI concept.

• All screens have access to the nav/menu which can be toggled to show/hide on left.
• Multiple cctrays concept
• Timing section
• Success section (choose colours, images, text) room for themes?

Other notes;

• Should clicking/touching a build expand the box to show more details about the break
• Limit the total number of trays
• Can mobile show 2 builds in a row, should this be configured in settings
• Should there be an users section, where by people could be added to be emialed, alerted if a build keeps breaking or cannot be tracked etc.

[GentlemanHal]

@mrgeorgegray Good stuff George :)

My only concern is having multiple trays under one 'tab' as features such as #38 and #42 would need to be implemented for each tray so the smaller windows might end up looking crowded, any thoughts?

Maybe instead of adding a mini window for each tray we could have the add button on the side menu and each new tray just becomes a new 'tab'?

[cowley05]

Maybe we could select the project from the box at the top left like gmail app? so the content in the views change depending on the project selected?

[joejag]

I like the idea of moving to a single page app.

I think we may end up with multiple 'monitors' which are styled differently. Sandeep has a OpenGL PoC app which he built on top of Nevergreen. It's possible we see these as a side issue instead. It's not crucial for this issue.

As @cowley05 said, can we push the individual trays to be menu items instead? That'd give us the whole screen to configure the builds. The two issues @GentlemanHal show the added features we will need to add in there.

Configuring the colours is an interesting idea. I know Jenkins sees 'green' as 'blue', but I suppose we never show green builds anyway. It's still useful as a legend.

[GentlemanHal]

@joejag Do we need to introduce a template library if we switch to a single page app? Any suggestions?

[joejag]

We currently have a double-page-app. So we have two html files that are
statically served. For the new UI George is working on we would need to
move from the model to a templating library as Chris suggests. This would
involve removing a bit of the JQuery dom manipulation in the views, which
is probably a good thing.

I like the Handlebars format. I'm not aware of anything better in this
space. Perhaps George has a preference?

J.

On Mon, Jan 26, 2015 at 5:01 PM, Christopher Martin <
[email protected]> wrote:

@joejag https://github.com/joejag Do we need to introduce a template
library if we switch to a single page app? Any suggestions?

—
Reply to this email directly or view it on GitHub
#45 (comment)
.

[GentlemanHal]

I think we should close off this issue and raise smaller more specific issues for any UI tweaking / changes we want to make.

We can then prioritise those into releases easier.

Thoughts?

[joejag]

Yeah, I believe the main work has been done now right? If so, let's closer
On 15 Feb 2015 01:16, "Christopher Martin" [email protected] wrote:

I think we should close off this issue and raise smaller more specific
issues for any UI tweaking / changes we want to make.

We can then prioritise those into releases easier.

Thoughts?

—
Reply to this email directly or view it on GitHub
#45 (comment)
.

[GentlemanHal]

We only really organised the SASS, we didn't combine the html pages so we are still serving config and monitor separately.

Perhaps we should combine them first?

[joejag]

Combining it feels like a separate task. Let's make a new issue
On 15 Feb 2015 14:59, "Christopher Martin" [email protected] wrote:

We only really organised the SASS, we didn't combine the html pages so we
are still serving config and monitor separately.

Perhaps we should combine them first?

—
Reply to this email directly or view it on GitHub
#45 (comment)
.

[GentlemanHal]

Closing this as v0.5.0 has been released and other specific issues have been opened to update the UI.