Hi Tom, I am really not a UI/UX person so I am all but useless for designing a Web Application or providing advice on how it should look or feel until it is done and I can use it. W.r.t your comment on re-branding, yes it would be nice for easier rebranding... but the functionality is more important than the aesthetics IMHO. OPSUI seems to throw stack traces all over the place at intermittent periods. This makes it difficult to work with reliably. I would really just like to see it work more reliably... The above is not very helpful I admit. It is however my opinion at this point in time. Lewis
On Mon, Oct 15, 2018 at 10:09 PM <dev-digest-h...@oodt.apache.org> wrote: > > From: Tom Barber <t...@spicule.co.uk> > To: dev@oodt.apache.org > Cc: > Bcc: > Date: Mon, 15 Oct 2018 16:46:33 -0700 > Subject: React based OPSUI > Hi folks, > > I’m mocking and stubbing out ideas for a React based OPSUI. > > Its not designed to reinvent the wheel, but modernise, allow easier > theming/branding, be modular for people wanting to embed specific > components into apps and so on. > > I have plans in my head for a couple of extra screens for file management, > workflow management and I’ve still got work to do on the mocks, but here’s > a Balsamiq link for people to start to mull over: > > https://balsamiq.cloud/sgp43nx/pdsiadc > > If you were designing OPSUI again, whats missing? Anything? Nothing, just > needs to throw less stack traces? ;) > > > Cheers > > Tom > > -- > > >
