Re: SIP-7 New Admin UI

Thanks Jason for updating the SIP-7 page. I think further updates to the page will follow soon with more information. I have prepared a presentation in favor of the POC ( https://github.com/apache/solr/pull/2605) where I go through the basic theory and show how a component with Kotlin and Compose

Re: SIP-7 New Admin UI

Perfect! Yeah, I think getting SIP-7 updated is a big step as it'll let folks catch up on where things stand and on the "big picture" decisions. Thanks for the PR link - will take a look shortly! On Tue, Jul 30, 2024 at 11:59 AM Christos Malliaridis wrote: > > Nothing easier than that, and prob

Re: SIP-7 New Admin UI

Nothing easier than that, and probably a better idea than referencing a branch that may be deleted at some point. Here are the updated links: - Github pull-request - Dev Docs for getting started

Re: SIP-7 New Admin UI

> *For the implementation* I'd like to know from the committers how > comfortable they feel with the code base for the new UI. Input about code > complexity, code readability and suitability of the framework in the > overall Solr project would be helpful to decide whether we could proceed > with th

Re: SIP-7 New Admin UI

With the input and feedback from the virtual meetup I'd like to wrap up the current progress with a couple of references: *Figma Design* I have created a Figma design (WIP) that

Re: SIP-7 New Admin UI

+1 for Kotlin; I've used it in the past and was fond of the experience. I'm sad we don't use it in our Gradle files. But take this with a grain of salt: I don't *intend* to work on the UI to be honest so my opinion of the tech there doesn't matter much. I suppose I might end up touching it if I w

Re: SIP-7 New Admin UI

I appreciate the vote for Kotlin Jan! I hadn’t really thought about the argument that if our base is primarily Java centric devs, that Kotlin versus React might be an easier route…. > On Jul 16, 2024, at 11:56 PM, Christos Malliaridis > wrote: > > Thanks for your reply too, Jan. You mention

Re: SIP-7 New Admin UI

Thanks for your reply too, Jan. You mention important points. > If frontend devs are to maintain it and we want to attract frontend professionals, then stick to industry standard React or similar. This is something that troubled me a lot. Following the industry-standards would probably be the saf

Re: SIP-7 New Admin UI

> - What technology stack would you consider and why? > - Would you consider a web-based / javascript-based framework easier to get > started with, or a JVM-based / kotlin-based UI framework? I consider these related. And it boils down to who will maintain the Admin UI app. If frontend devs are t

Re: SIP-7 New Admin UI

Thanks for the quick reply Eric. :) The first question is indeed focused on personal preferences. I included it to get a rough idea with what people might compare the current state and answer the other questions, so that it gets clearer from where each one is coming from and what their expectation

Re: SIP-7 New Admin UI

I’m going to pull out your questions and inline my answers: - What technology stack would you consider and why? - I think this is an almost impossible thing to answer as it tends to be based on people’s individual preferences. For example, if I was to build an Admin tool from scratch th

Re: SIP-7 New Admin UI

Thanks for the references David, those are very insightful to me. I am definitely not the first one coming up with these ideas, that's for sure. I think the fact that there are multiple third-party frontends for Solr shows how important the UI is to the users and it should push us even more to do

Re: SIP-7 New Admin UI

An admin UI can definitely be plugged in. Here is one: https://github.com/yasa-org/yasa And you would not be the first to consider a desktop client. There is one of those too: https://solr.search-navigator.org/ On Tue, Jul 9, 2024 at 9:37 PM Christos Malliaridis wrote: > > Thanks for your input

Re: SIP-7 New Admin UI

Thanks for your input, votes and feedback so far, I appreciate it. The security concerns are justified and are something I am currently looking into. With a rewrite it will be easier to take that into account and consider alternative options that could also enhance security, too. For example, I am

Re: SIP-7 New Admin UI

Disabling certainly is helpful, but... there's the risk it gets enabled, it will still contribute to the footprint that vulnerability scanners have to cover. If it's something that can be enabled/disabled or removed from the full distro, and added to the slim distro if desired, that would be even

Re: SIP-7 New Admin UI

RE security; disabling it would suffice and if I recall is already supported. On Tue, Jul 9, 2024 at 3:09 PM Gus Heck wrote: > > Also +1 ... "in the same repo and alongside" is how the last migration was > done IIRC. The big plus of this is as it's developed to a point of partial > utility you ca

Re: SIP-7 New Admin UI

Also +1 ... "in the same repo and alongside" is how the last migration was done IIRC. The big plus of this is as it's developed to a point of partial utility you can put a link in the old UI to try out the new UI and get feedback and make testing much easier. One thing that might be nice if we can

Re: SIP-7 New Admin UI

I agree with Jason on everything. Thank you so much for putting this much work into something with so much baggage in the community! I'm a huge +1 here, and love the things I saw in your screenshots on Slack. - Houston On Mon, Jul 8, 2024 at 2:23 PM Jason Gerlowski wrote: > Hey Christos, > >

Re: SIP-7 New Admin UI

Hey Christos, Sorry for the delay responding here - lots of context to read up on! Firstly, thanks for the huge effort you've put into writing this all up! Quite the thorough job, and it's really helpful to enable us non-UI folks to follow along haha. If I understand things correctly, there's a