[
https://issues.apache.org/jira/browse/SOLR-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259455#comment-14259455
]
Jack Krupansky commented on SOLR-5507:
--------------------------------------
This issue has gotten confused. Please clarify the summary and description to
inform readers whether the intention is:
1. Simply "refactor" the implementation to make the code more maintainable and
extensible.
2. Add features to the existing UI to cater to advanced users.
3. Revamp the UI itself to cater to new and novice users.
4. Replace the existing UI or supplement it with two UI's, one for novices
(guides them through processes) and one for experts (access more features more
easily.)
IOW, what are the "requirements" here?
I'm not opposed to any of the above, but the original issue summary and
description seemed more focused on the internal implementation rather than the
externals of a new UI.
> Admin UI - Refactoring using AngularJS
> --------------------------------------
>
> Key: SOLR-5507
> URL: https://issues.apache.org/jira/browse/SOLR-5507
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Priority: Minor
> Attachments: SOLR-5507.patch
>
>
> On the LSR in Dublin, i've talked again to [~upayavira] and this time we
> talked about Refactoring the existing UI - using AngularJS: providing (more,
> internal) structure and what not ;>
> He already started working on the Refactoring, so this is more a 'tracking'
> issue about the progress he/we do there.
> Will extend this issue with a bit more context & additional information, w/
> thoughts about the possible integration in the existing UI and more (:
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
