[jira] [Commented] (SOLR-12196) Prepare Admin UI for migrating to Angular.io
[
https://issues.apache.org/jira/browse/SOLR-12196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439138#comment-16439138
]
Upayavira commented on SOLR-12196:
--
{quote}If I had the knowledge, I'd be interested in helping with a rewrite. I
just don't know enough about javascript or css to tackle a job like that.
{quote}
Then learn it :) It is great fun! I'm not a front-end developer by any means, I
just learned what a colleague pointed me at. And there is structure there in
the JavaScript land that wasn't there before that lends itself to back-end
developers.
Go do a react tutorial or two. The CSS stuff we would defer to a graphic
designer. In the end, it is just programming. I might be able to muster the
time to put together a framework and build system onto which others can hang
pages, especially if we already had a design put together.
> Prepare Admin UI for migrating to Angular.io
>
>
> Key: SOLR-12196
> URL: https://issues.apache.org/jira/browse/SOLR-12196
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Admin UI
>Reporter: Jan Høydahl
>Priority: Major
> Labels: Angular, AngularJS, angular-migration
> Fix For: master (8.0)
>
>
> AngularJS is soon end of life, it [enters LTS in july
> 2018|https://docs.angularjs.org/misc/version-support-status], whereupon it
> will only receive fixes to serious bugs. Solr uses AngularJS 1.3 (the latest
> AngularJS will be 1.7).
> This issue is *not* for upgrading to Angular5/6, but to start preparing the
> existing UI for easier migration later on. See
> [https://angular.io/guide/upgrade].
> This JIRA will likely get multiple sub tasks such as
> * Change to [Folders-by-Feature
> Structure|https://angular.io/guide/upgrade#follow-the-angularjs-style-guide],
> i.e. mix html, css, js in a folder based on feature
> * Use a [Module
> Loader|https://angular.io/guide/upgrade#using-a-module-loader] like
> [Webpack|https://webpack.js.org/]
> * Use [Component
> Directives|https://angular.io/guide/upgrade#using-component-directives]
> (requires first move from AngularJS 1.3 to 1.5)
> The rationale for this lira is recognising how central the Admin UI is to
> Solr, not letting it rot on top of a dying framework. Better to start moving
> step by step and [perhaps write all new views in Angular
> 5|https://angular.io/guide/upgrade#upgrading-with-ngupgrade], than to fall
> further and further behind.
> This effort of course assumes that Angular.io is the path we want to go, and
> not React, VueJS or some other new kid on the block :)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12196) Prepare Admin UI for migrating to Angular.io
[ https://issues.apache.org/jira/browse/SOLR-12196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438382#comment-16438382 ] Shawn Heisey commented on SOLR-12196: - bq. that we do a component-based design which makes it possible for Solr plugins / contribs to provide Admin UI menus and screens I really like that idea. Allowing modules to handle their own UI will make maintaining the core UI easier and give module developers more capability. If I had the knowledge, I'd be interested in helping with a rewrite. I just don't know enough about javascript or css to tackle a job like that. > Prepare Admin UI for migrating to Angular.io > > > Key: SOLR-12196 > URL: https://issues.apache.org/jira/browse/SOLR-12196 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: Admin UI >Reporter: Jan Høydahl >Priority: Major > Labels: Angular, AngularJS, angular-migration > Fix For: master (8.0) > > > AngularJS is soon end of life, it [enters LTS in july > 2018|https://docs.angularjs.org/misc/version-support-status], whereupon it > will only receive fixes to serious bugs. Solr uses AngularJS 1.3 (the latest > AngularJS will be 1.7). > This issue is *not* for upgrading to Angular5/6, but to start preparing the > existing UI for easier migration later on. See > [https://angular.io/guide/upgrade]. > This JIRA will likely get multiple sub tasks such as > * Change to [Folders-by-Feature > Structure|https://angular.io/guide/upgrade#follow-the-angularjs-style-guide], > i.e. mix html, css, js in a folder based on feature > * Use a [Module > Loader|https://angular.io/guide/upgrade#using-a-module-loader] like > [Webpack|https://webpack.js.org/] > * Use [Component > Directives|https://angular.io/guide/upgrade#using-component-directives] > (requires first move from AngularJS 1.3 to 1.5) > The rationale for this lira is recognising how central the Admin UI is to > Solr, not letting it rot on top of a dying framework. Better to start moving > step by step and [perhaps write all new views in Angular > 5|https://angular.io/guide/upgrade#upgrading-with-ngupgrade], than to fall > further and further behind. > This effort of course assumes that Angular.io is the path we want to go, and > not React, VueJS or some other new kid on the block :) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12196) Prepare Admin UI for migrating to Angular.io
[
https://issues.apache.org/jira/browse/SOLR-12196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438377#comment-16438377
]
Jan Høydahl commented on SOLR-12196:
Ok makes sense. Could even be that some Solr users (companies) are willing to
sponsor such an effort with some time from their own UI designers or frontend
developers. Feel free to check the temperature on the dev (and solr-user?) list
and we can return to this Jira with whatever conclusion the discussion may give.
One wish from me, no matter what framework we choose, is that we do a
component-based design which makes it possible for Solr plugins / contribs to
provide Admin UI menus and screens. One acid test for this could be to move all
DIH UI code from {{webapp/}} to {{contrib/dataimporthandler/}}.
> Prepare Admin UI for migrating to Angular.io
>
>
> Key: SOLR-12196
> URL: https://issues.apache.org/jira/browse/SOLR-12196
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Admin UI
>Reporter: Jan Høydahl
>Priority: Major
> Labels: Angular, AngularJS, angular-migration
> Fix For: master (8.0)
>
>
> AngularJS is soon end of life, it [enters LTS in july
> 2018|https://docs.angularjs.org/misc/version-support-status], whereupon it
> will only receive fixes to serious bugs. Solr uses AngularJS 1.3 (the latest
> AngularJS will be 1.7).
> This issue is *not* for upgrading to Angular5/6, but to start preparing the
> existing UI for easier migration later on. See
> [https://angular.io/guide/upgrade].
> This JIRA will likely get multiple sub tasks such as
> * Change to [Folders-by-Feature
> Structure|https://angular.io/guide/upgrade#follow-the-angularjs-style-guide],
> i.e. mix html, css, js in a folder based on feature
> * Use a [Module
> Loader|https://angular.io/guide/upgrade#using-a-module-loader] like
> [Webpack|https://webpack.js.org/]
> * Use [Component
> Directives|https://angular.io/guide/upgrade#using-component-directives]
> (requires first move from AngularJS 1.3 to 1.5)
> The rationale for this lira is recognising how central the Admin UI is to
> Solr, not letting it rot on top of a dying framework. Better to start moving
> step by step and [perhaps write all new views in Angular
> 5|https://angular.io/guide/upgrade#upgrading-with-ngupgrade], than to fall
> further and further behind.
> This effort of course assumes that Angular.io is the path we want to go, and
> not React, VueJS or some other new kid on the block :)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12196) Prepare Admin UI for migrating to Angular.io
[ https://issues.apache.org/jira/browse/SOLR-12196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438072#comment-16438072 ] Alexandre Rafalovitch commented on SOLR-12196: -- My feeling is that "if not now" will be "close to never". Because it was a huge effort to move it to Angular 1 and some bits were not even finished for very long time (ever?). So, let's say another 3 years before anybody will raise this conversation with the same amount of "sunk costs" as right now. As to how/who, yeah, that's the big issue. Has been, it seems for a long time. I am interested in learning React but I am not a frontend dev myself to take a lead. And certainly not a visual designer, which is the hairy part... But my feeling is that maybe it is worth asking on the dev list as a tradeoff discussion. > Prepare Admin UI for migrating to Angular.io > > > Key: SOLR-12196 > URL: https://issues.apache.org/jira/browse/SOLR-12196 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: Admin UI >Reporter: Jan Høydahl >Priority: Major > Labels: Angular, AngularJS, angular-migration > Fix For: master (8.0) > > > AngularJS is soon end of life, it [enters LTS in july > 2018|https://docs.angularjs.org/misc/version-support-status], whereupon it > will only receive fixes to serious bugs. Solr uses AngularJS 1.3 (the latest > AngularJS will be 1.7). > This issue is *not* for upgrading to Angular5/6, but to start preparing the > existing UI for easier migration later on. See > [https://angular.io/guide/upgrade]. > This JIRA will likely get multiple sub tasks such as > * Change to [Folders-by-Feature > Structure|https://angular.io/guide/upgrade#follow-the-angularjs-style-guide], > i.e. mix html, css, js in a folder based on feature > * Use a [Module > Loader|https://angular.io/guide/upgrade#using-a-module-loader] like > [Webpack|https://webpack.js.org/] > * Use [Component > Directives|https://angular.io/guide/upgrade#using-component-directives] > (requires first move from AngularJS 1.3 to 1.5) > The rationale for this lira is recognising how central the Admin UI is to > Solr, not letting it rot on top of a dying framework. Better to start moving > step by step and [perhaps write all new views in Angular > 5|https://angular.io/guide/upgrade#upgrading-with-ngupgrade], than to fall > further and further behind. > This effort of course assumes that Angular.io is the path we want to go, and > not React, VueJS or some other new kid on the block :) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12196) Prepare Admin UI for migrating to Angular.io
[ https://issues.apache.org/jira/browse/SOLR-12196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438005#comment-16438005 ] Jan Høydahl commented on SOLR-12196: It would be great with a re-imagined Admin and a brand new framework :) But as I wrote initially, are we rigged for such a huge job now? In my head it is more realistic with byte-size improvements as laid out in this Jira with the goal of getting to Angular5 (still much work but less than React?). Keep the same design. Even keep parts of the UI as-is using ngUpgrade? Then do visual and logical re-design step by step after that. If we have the will, skill and capacity to start from scratch with React and re-design then I won't vote against, but I don't see how/who? > Prepare Admin UI for migrating to Angular.io > > > Key: SOLR-12196 > URL: https://issues.apache.org/jira/browse/SOLR-12196 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: Admin UI >Reporter: Jan Høydahl >Priority: Major > Labels: Angular, AngularJS, angular-migration > Fix For: master (8.0) > > > AngularJS is soon end of life, it [enters LTS in july > 2018|https://docs.angularjs.org/misc/version-support-status], whereupon it > will only receive fixes to serious bugs. Solr uses AngularJS 1.3 (the latest > AngularJS will be 1.7). > This issue is *not* for upgrading to Angular5/6, but to start preparing the > existing UI for easier migration later on. See > [https://angular.io/guide/upgrade]. > This JIRA will likely get multiple sub tasks such as > * Change to [Folders-by-Feature > Structure|https://angular.io/guide/upgrade#follow-the-angularjs-style-guide], > i.e. mix html, css, js in a folder based on feature > * Use a [Module > Loader|https://angular.io/guide/upgrade#using-a-module-loader] like > [Webpack|https://webpack.js.org/] > * Use [Component > Directives|https://angular.io/guide/upgrade#using-component-directives] > (requires first move from AngularJS 1.3 to 1.5) > The rationale for this lira is recognising how central the Admin UI is to > Solr, not letting it rot on top of a dying framework. Better to start moving > step by step and [perhaps write all new views in Angular > 5|https://angular.io/guide/upgrade#upgrading-with-ngupgrade], than to fall > further and further behind. > This effort of course assumes that Angular.io is the path we want to go, and > not React, VueJS or some other new kid on the block :) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12196) Prepare Admin UI for migrating to Angular.io
[ https://issues.apache.org/jira/browse/SOLR-12196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16437447#comment-16437447 ] Alexandre Rafalovitch commented on SOLR-12196: -- >From all I have read, the migration from Angular 1 to later version is a real >piece of re-engineering as well. In that sense, migrating to React or Vue are >probably the projects of similar complexity. My vote would probably be for React as there are still more integrations with it and more possibilities (native mobile UI with React Native!?!). And given the amount of work, I wonder if that's also a good time to collect larger level ideas on what UI should look like, given the prominence of Javascript and availability of self-descriptive and management Solr APIs. > Prepare Admin UI for migrating to Angular.io > > > Key: SOLR-12196 > URL: https://issues.apache.org/jira/browse/SOLR-12196 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: Admin UI >Reporter: Jan Høydahl >Priority: Major > Labels: Angular, AngularJS, angular-migration > Fix For: master (8.0) > > > AngularJS is soon end of life, it [enters LTS in july > 2018|https://docs.angularjs.org/misc/version-support-status], whereupon it > will only receive fixes to serious bugs. Solr uses AngularJS 1.3 (the latest > AngularJS will be 1.7). > This issue is *not* for upgrading to Angular5/6, but to start preparing the > existing UI for easier migration later on. See > [https://angular.io/guide/upgrade]. > This JIRA will likely get multiple sub tasks such as > * Change to [Folders-by-Feature > Structure|https://angular.io/guide/upgrade#follow-the-angularjs-style-guide], > i.e. mix html, css, js in a folder based on feature > * Use a [Module > Loader|https://angular.io/guide/upgrade#using-a-module-loader] like > [Webpack|https://webpack.js.org/] > * Use [Component > Directives|https://angular.io/guide/upgrade#using-component-directives] > (requires first move from AngularJS 1.3 to 1.5) > The rationale for this lira is recognising how central the Admin UI is to > Solr, not letting it rot on top of a dying framework. Better to start moving > step by step and [perhaps write all new views in Angular > 5|https://angular.io/guide/upgrade#upgrading-with-ngupgrade], than to fall > further and further behind. > This effort of course assumes that Angular.io is the path we want to go, and > not React, VueJS or some other new kid on the block :) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12196) Prepare Admin UI for migrating to Angular.io
[ https://issues.apache.org/jira/browse/SOLR-12196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428448#comment-16428448 ] Upayavira commented on SOLR-12196: -- I don't have a major investment in Solr at this time, but I am certainly game to follow on and add what bits I might. Whilst I am far from a front-end developer, I have recently played with Webpack and React with some success. The transition from the old JS UI to Angular was made simpler because of how Angular manages its (whole page) templates. React breaks things down into smaller components, and whilst this could be better in the long run in terms of component reuse, it means that a conversion could be a substantial piece of work. I like your idea of breaking the task down into smaller steps. > Prepare Admin UI for migrating to Angular.io > > > Key: SOLR-12196 > URL: https://issues.apache.org/jira/browse/SOLR-12196 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: Admin UI >Reporter: Jan Høydahl >Priority: Major > Labels: Angular, AngularJS, angular-migration > Fix For: master (8.0) > > > AngularJS is soon end of life, it [enters LTS in july > 2018|https://docs.angularjs.org/misc/version-support-status], whereupon it > will only receive fixes to serious bugs. Solr uses AngularJS 1.3 (the latest > AngularJS will be 1.7). > This issue is *not* for upgrading to Angular5/6, but to start preparing the > existing UI for easier migration later on. See > [https://angular.io/guide/upgrade]. > This JIRA will likely get multiple sub tasks such as > * Change to [Folders-by-Feature > Structure|https://angular.io/guide/upgrade#follow-the-angularjs-style-guide], > i.e. mix html, css, js in a folder based on feature > * Use a [Module > Loader|https://angular.io/guide/upgrade#using-a-module-loader] like > [Webpack|https://webpack.js.org/] > * Use [Component > Directives|https://angular.io/guide/upgrade#using-component-directives] > (requires first move from AngularJS 1.3 to 1.5) > The rationale for this lira is recognising how central the Admin UI is to > Solr, not letting it rot on top of a dying framework. Better to start moving > step by step and [perhaps write all new views in Angular > 5|https://angular.io/guide/upgrade#upgrading-with-ngupgrade], than to fall > further and further behind. > This effort of course assumes that Angular.io is the path we want to go, and > not React, VueJS or some other new kid on the block :) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12196) Prepare Admin UI for migrating to Angular.io
[ https://issues.apache.org/jira/browse/SOLR-12196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428335#comment-16428335 ] Jan Høydahl commented on SOLR-12196: Not sure if this is realistic if we don't have a dedicated frontend committer who can lead the effort. I know enough of JS, HTML and Angular to find my way around Admin UI and do small stuff, but doing major restructuring would benefit from someone who have done it before... Hope to get some input into this thinking from [~upayavira], [~steffkes], [~erickerickson]. The [ngUpgrade|https://angular.io/guide/upgrade#upgrading-with-ngupgrade] approach looks attractive as we can migrate one view at a time, assuming that our app is large enough for it to be a major undertaking to do it all-in-one-step. So this Jira I guess is to take us to a position where it would be possible to even think about such a move :) > Prepare Admin UI for migrating to Angular.io > > > Key: SOLR-12196 > URL: https://issues.apache.org/jira/browse/SOLR-12196 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: Admin UI >Reporter: Jan Høydahl >Priority: Major > Labels: Angular, AngularJS, angular-migration > Fix For: master (8.0) > > > AngularJS is soon end of life, it enters LTS in july 2018, whereupon it will > only receive fixes to serious bugs. Solr uses AngularJS 1.3 (the latest > AngularJS is 1.7). > This issue is *not* for upgrading to Angular5/6, but to start preparing the > existing UI for easier migration later on. See > https://angular.io/guide/upgrade. > This JIRA will likely get multiple sub tasks such as > * Change to [Folders-by-Feature > Structure|https://angular.io/guide/upgrade#follow-the-angularjs-style-guide], > i.e. mix html, css, js in a folder base don feature > * Use a [Module > Loader|https://angular.io/guide/upgrade#using-a-module-loader] like > [Webpack|https://webpack.js.org] > * Use [Component > Directives|https://angular.io/guide/upgrade#using-component-directives] > (requires first move from AngularJS 1.3 to 1.5) > The rationale for this lira is recognising how central the Admin UI is to > Solr, not letting it rot on top of a dying framework. Better to start moving > step by step and [perhaps write all new views in Angular > 5|https://angular.io/guide/upgrade#upgrading-with-ngupgrade], than to fall > further and further behind. > This effort of course assumes that Angular.io is the path we want to go, and > not React, VueJS or some other new kid on the block :-) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
