--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Q3: IE wouldn’t be supported anymore, I know this could be a show-stopper for banking users, where (unfortunately) Microsoft + IE is a *must have* combination for desktops.
Q6: Will the new UI be only a "rewrite" or also UI/UX redesign?
Q1: Is this effort intended to be a “technology refresh” to get rid of GWT with something more modern but keeping the current Gerrit UX?
Q2: Why Polymer and not AngularJS? Dariusz presented AngularGerrit [1] last year and seemed promising!
Q3: IE wouldn’t be supported anymore, I know this could be a show-stopper for banking users, where (unfortunately) Microsoft + IE is a *must have* combination for desktops.
Q4: Are we planning as well to design the UX in a way that could be easily “re-branded” with custom CSS? (currently it is quite a challenge with GWT-based UX)
Q5: Did you evaluate possibility of extending Polymer UI using
plugins? Do you even consider having extension points for plugins in
the UI?
On 23 Oct 2015, at 22:58, Andrew Bonventre (Bons) <andy...@google.com> wrote:Q1: Is this effort intended to be a “technology refresh” to get rid of GWT with something more modern but keeping the current Gerrit UX?Ideally the UX would improve as a result of the project.
Q2: Why Polymer and not AngularJS? Dariusz presented AngularGerrit [1] last year and seemed promising!Component-based authoring that will eventually become native behavior is the goal. Polymer exists to use Web Components now, with the goal being less JavaScript in the future, not more. Also, native support means bigger performance gains.
Q3: IE wouldn’t be supported anymore, I know this could be a show-stopper for banking users, where (unfortunately) Microsoft + IE is a *must have* combination for desktops.Shawn already answered this. Polymer’s JS polyfills support a subset of IE, with Edge on board with the Web Component spec.
Q4: Are we planning as well to design the UX in a way that could be easily “re-branded” with custom CSS? (currently it is quite a challenge with GWT-based UX)Polymer has a very nice styling story: https://www.polymer-project.org/1.0/docs/devguide/styling.html and theming is something we are taking into consideration.
Q5: Did you evaluate possibility of extending Polymer UI using
plugins? Do you even consider having extension points for plugins in
the UI?We don’t want to break the current JS API, which GWT uses for the current plugin system. Plugins are definitely on our radar given Polymer’s ability to dynamically import custom elements/styles.
Sounds like there are a few people interested in this. Would it be worth having a presentation at the upcoming Gerrit summit?
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
I'm even later to the party, I couldn't find any new topics about this new UI searching the archive so I'll comment here. I'm a new Gerrit user (used GitHub, mostly before) and this topic made me very hopeful, I hope this is still an ongoing effort. IMO Gerrit really needs a new UI.
--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to a topic in the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/repo-discuss/AuvsRmXChz8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to repo-discuss...@googlegroups.com.
Work is still in progress. You can see the current state deployed on gerrit-review already [1].