Makes sense to me. What is the best case scenario? A light-weight
javascript toolkit dependency (probably distributed w/ OSCAR)? Maybe
no external dependencies?
Another heavy dependency that would be nice to remove is mysql and/or
postgres (OSCAR base uses one and jobmonarch uses the other). A NoS
Hi Stephen,
> we do want to ensure that the installation can still take place offline too.
Yes, I totally missed the necessity of the offline installation. That brings me
to think about making the OSCAR CLI more usable.
All the gui should be integrated with the OSCAR CLI so that we can reduce all
that is an interesting thought...
we do want to ensure that the installation can still take place offline too.
s.
Stephen L. Scott, Ph.D. voice: 865-574-3144
Oak Ridge National Laboratory fax: 86
Hi guys,
I am wondering if anyone is interested in having a new gui for OSCAR. I am
thinking about a web interface for the OSCAR installation.
We have brought this idea at GSoC before and I am not sure if it actually is
implemented somehow or not.
Currently OSCAR uses perl-Qt and perl-Tk and w
