I'm somewhat open to other suggestions, as I'm right at the beginning of the project. I know Angular, and like it. I've looked at a couple of others, but have found them to be more of a collection of disparate components and not as integrated as Angular.
However, if folks want to have a discussion on competing frameworks, I'm at least prepared to listen!! Note - the design goal is to make it as easy for *Java* developers to work with. Folks who are typically back-end developers, thus the framework must isolate the developer from UI quirks as much as possible, and handle have some form of design abstraction. Upayavira On Tue, Dec 23, 2014, at 10:09 AM, Alexandre Rafalovitch wrote: > Semi Off Topic, but is AngularJS the best next choice, given the > version 2 being so different from version 1? > > Regards, > Alex. > ---- > Sign up for my Solr resources newsletter at http://www.solr-start.com/ > > > On 23 December 2014 at 06:52, Upayavira <u...@odoko.co.uk> wrote: > > Hi, > > > > I've (hopefully) made some time to do some work on the Solr Admin UI > > (convert it to AngularJS). I plan to do it on a clone of the lucene-solr > > project at GitHub. > > > > Before I dive too thoroughly into this, I wanted to see if there were > > any best practices that would make it easier to back-port these changes > > into SVN should I actually succeed at producing something useful. Is it > > enough just to make a branch called SOLR-5507 and start committing my > > changes there? > > > > Periodically, I'll zip up the relevant bits and attach them to the JIRA > > ticket. > > > > TIA > > > > Upayavira
