ebryn/bugzilla-ember

Bugzilla frontend written in Ember.js

bugzilla-ember's Issues

Figure out license

Login modal is no longer centered

I think this was introduced in ad36a7a

cc @edwardoriordan

Move to grunt-based build

Handle bug load errors

For example: http://bugzilla.erikbryn.com/#/bug/326633

Improve comments display

From @andreasgal: "I think you should show the first comment (description) and the last 10 comments by default. In the middle you can skip them and show an "expand" clickable if you want. Usually people want to see the description and the last comments."

style attachments table and page

• borders, text-align, etc.
• zebra table

Improve data change animation

Aliases aren't being displayed upon initial render, which is causing them to flash.

Store user credentials in session cookie?

Right now refreshing the page causes the user credentials to be lost since we're currently only keeping them in memory.

It'd probably be better to get a token from the API server instead.

Look into using node-sass to remove the Ruby dependency

https://github.com/andrew/node-sass

Initial Design Discussion

Just copying and pasting in an email:

I started a gdoc (https://docs.google.com/document/d/17nuso2FWZ2seghJ2AL8dJ0clgo-qNKU7Pp7xnvLl70U) noting down ideas and projects that people mentioned in irc.

I don't know if we really need to wireframe at this stage. When we are ready to change up the UI in larger ways they will be useful. If they help you think though go for it!

Thinking over the past few days re visual design I have been thinking that for a tool like bugzilla we should go for a what I am going to call 'classic HTML' (sorry!) aesthetic - something like the https://www.gov.uk/designprinciples. The priority should be helping people getting their work done. Aiming a something classic rather then super contemporary seems approbate for this kind of tool. Welcome other opinions.

In terms of technologies Janush from chatting to people we can be very aggressive in terms of browser support and using new features. Personally I would be interested in seeing what kind of UIs we can build using things like flexbox, calc and other new CSS stuff. People were mentioning using topcoat which looks cool and am open to (though I am not sure who much it gives us). Will definitely create a branch and play around with it though. In terms of jquery the ember experts would know better then me but I would imagine that ember has its own best practices surrounding where you manipulate the dom so we would need to be aware of that.

From my point of view in the short term I see the design as being

1. based on iteration rather then reinvention
2. focused on making things look cohesive but without worrying overall branding
3. has the short term goal of being the skin we would use if we used bugzilla