[
https://issues.apache.org/jira/browse/SOLR-14414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17089526#comment-17089526
]
Marcus Eagan commented on SOLR-14414:
-------------------------------------
[~janhoy][~dsmiley] and others, I've attached a new video because I have
thought through the collection portion of the UX (in my sleep actually) in a
way that makes sense. I'm obviously still working through many things, like
grokking the new Angular form API, limiting results, and lots of styling.
In this way, users don't have to go all the back to the left menu and change
most of the viewport to navigate through different screens of the same
collection. Navigating between collections is also easier in this way.
Ultimately, I would want to support really seamless results traversal and even
pagination and so that users can dig in. I have big plans for the analysis
screen as well, which is personally my favorite. I think the changes to the
collection screens will be the biggest productivity and accessibility
improvement for developers and users of Solr worldwide.
I've pushed this code up into the PR for this issue. At some point soon after
the community comes to consensus, and this is accepted, I will loop in a few
old pals that will lend a hand where they can.
As for releases, I'd be enthusiastic about supporting new releases from the
Solr Admin UI indefinitely until others ramp up on maintenance or other
community members step up to assist in this area.
> New Admin UI
> ------------
>
> Key: SOLR-14414
> URL: https://issues.apache.org/jira/browse/SOLR-14414
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Admin UI
> Affects Versions: master (9.0)
> Reporter: Marcus Eagan
> Priority: Major
> Attachments: QueryUX-SolrAdminUIReboot.mov
>
>
> We have had a lengthy discussion in the mailing list about the need to build
> a modern UI that is both more security and does not depend on deprecated, end
> of life code. In this ticket, I intend to familiarize the community with the
> efforts of the community to do just that that. While we are nearing feature
> parity, but not there yet as many have suggested we could complete this task
> in iterations, here is an attempt to get the ball rolling. I have mostly
> worked on it in weekend nights on the occasion that I could find the time.
> Angular is certainly not my specialty, and this is my first attempt at using
> TypeScript besides a few brief learning exercises here and there. However, I
> will be engaging experts in both of these areas for consultation as our
> community tries to pull our UI into another era.
> Many of the components here can improve. One or two them need to be
> rewritten, and there are even at least three essential components to the app
> missing, along with some tests. A couple other things missing are the V2 API,
> which I found difficult to build with in this context because it is not
> documented on the web. I understand that it is "self-documenting," but the
> most easy-to-use APIs are still documented on the web. Maybe it is entirely
> documented on the web, and I had trouble finding it. Forgive me, as that
> could be an area of assistance. Another area where I need assistance is
> packaging this application as a Solr package. I understand this app is not in
> the right place for that today, but it can be. There are still many
> improvements to be made in this Jira and certainly in this code.
> The project is located in {{lucene-solr/solr/webapp2}}, where there is a
> README for information on running the app.
> The app can be started from the this directory with {{npm start}} for now. It
> can quickly be modified to start as a part of the typical start commands as
> it approaches parity. I expect there will be a lot of opinions. I welcome
> them, of course. The community input should drive the project's success.
--
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
