Re: Next steps for Solr Admin UI - request for in-depth discussion

2018-04-17 Thread Upayavira
On Mon, 16 Apr 2018, at 6:53 PM, Alexandre Rafalovitch wrote: > > It really depends on what your goal is: a refreshed UI or getting rid of > > AngularJS > > I think that's an interesting question. Do we _know_ how a refreshed > UI could be better than what we have now? > *) Better mobile UI was o

Re: Next steps for Solr Admin UI - request for in-depth discussion

2018-04-16 Thread Alexandre Rafalovitch
> It really depends on what your goal is: a refreshed UI or getting rid of > AngularJS I think that's an interesting question. Do we _know_ how a refreshed UI could be better than what we have now? *) Better mobile UI was one suggestion *) Reviewing it myself, I feel that there is lack of clarity

Re: Next steps for Solr Admin UI - request for in-depth discussion

2018-04-15 Thread Upayavira
Jan, The plus of the Angular upgrade path that I saw you mention elsewhere was that you could have both old and new Angulars running in the same app, and migrate slowly. That would work for a change of backend, using the same styling. It really depends on what your goal is: a refreshed UI or getti

Re: Next steps for Solr Admin UI - request for in-depth discussion

2018-04-15 Thread Shawn Heisey
On 4/15/2018 11:13 AM, Jan Høydahl wrote: Upayavira, moving from jQuery to AngularJS took the approach of building a clean parallel  code base, with the downside of years of maintaining two UIs. Do you see any better approach this time around? I'm onboard with writing a whole new UI in a more

Re: Next steps for Solr Admin UI - request for in-depth discussion

2018-04-15 Thread Jan Høydahl
Just to be clear, Angular is now also built on components, transpiled and a rich toolset, including debugger, unit testing, end-to-end tests, CLI with scaffolding for adding new components/services etc. Building using components will also help prepare the new UI for a plugin architecture where

Re: Next steps for Solr Admin UI - request for in-depth discussion

2018-04-15 Thread Upayavira
On Sat, 14 Apr 2018, at 4:40 PM, Alexandre Rafalovitch wrote: > Hello, > > The relevant JIRA is SOLR-12196, but we felt this deserved a greater > discussion. > > Basically, our Admin UI is currently using AngularJS (1.x) as its > Javascript framework. That particular library has reached its >

Next steps for Solr Admin UI - request for in-depth discussion

2018-04-14 Thread Alexandre Rafalovitch
Hello, The relevant JIRA is SOLR-12196, but we felt this deserved a greater discussion. Basically, our Admin UI is currently using AngularJS (1.x) as its Javascript framework. That particular library has reached its evolutionary end long time ago and is about to stop being supported all together.