[
https://issues.apache.org/jira/browse/SOLR-12276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076333#comment-17076333
]
Upayavira commented on SOLR-12276:
----------------------------------
So as [~erickerickson] said, the UI was originally written in JS using a
library called Sammy. Then new frameworks came along. I converted the Sammy
code to AngularJS. It halved the lines of code, which was a good thing, but it
kept the UI essentially the same - the intent was to make it more maintainable,
not to fundamentally rethink it.
It wasn't clear at that time that React was gonna win the race. In hindsight,
that would have been a better choice. But hey ho.
As to improving it, there's two approaches. Firstly, what's been described
above: create a proposal, discuss it, etc (I'd call that a 'bureaucratic
approach). Or there's what I'd call a geek approach: knock something up. Show
us what we could have. If it is any good, and solves problems the UI has, then
there's a good chance it'll get accepted.
I think it makes sense to have the UI served outside of Solr itself. Perhaps as
a separate webapp (from same Jetty?) As this simplifies a lot of issues - it is
just another client for Solr, not blessed in any way.
I was expecting to put a lot of work into the UI after rewriting it in
AngularJS, but life took an unfortunate turn and derailed me. Now I don't make
any use of Solr at all, but happy to share thoughts/perspective if it is useful.
> Admin UI - Convert from "AngularJS" to "Angular"
> ------------------------------------------------
>
> Key: SOLR-12276
> URL: https://issues.apache.org/jira/browse/SOLR-12276
> Project: Solr
> Issue Type: Improvement
> Components: Admin UI
> Reporter: James Dyer
> Priority: Minor
> Labels: Angular, AngularJS, angular-migration
> Time Spent: 1h
> Remaining Estimate: 0h
>
> With SOLR-12196 it was noted the current Solr Admin UI runs AngularJS (1.x),
> which is to be End-of-Life later this year. Various options were proposed
> for what to do next. One option is to keep the existing functionality but
> migrate to a newer UI framework. This ticket is to migrate the existing UI
> to Angular (2+).
> See [this readme
> file|https://github.com/jdyer1/lucene-solr/tree/feature/angular-conversion-solr-admin/solr/webapp].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
