I would rather mirage2 be a regular (compiled) xmlui theme. I rarely add
new JS libraries, and when I do, I can include them via <script src>. For
CSS/JS minification, you could use a service like cloudflare cdn to serve
compiled/cached versions of your sites. I guess, the old flow allowed me to
change the theme, copy it to /dspace/webapps/theme/, and I could refresh my
browser. All instant. Having to do a full redeploy to test theme changes,
is a pain. So, for our local work, we'll probably stick with forking the
mirage2 maven theme to compiled regular theme, just for a simpler process.
If you really wanted to build a great UI using modern web frameworks. I
would focus on building off of REST API. What are you going to do, fix
cocoon?
________________
Peter Dietz
Longsight
www.longsight.com
pe...@longsight.com
p: 740-599-5005 x809
On Fri, Nov 14, 2014 at 10:02 AM, Tim Donohue <tdono...@duraspace.org>
wrote:
> Robin and all,
>
> Regarding the "optional modules": It seems like in 5.0, we have to move
> forward with these modules as "optional". At least to me, it seems like
> it'd require a lot of work/time to make Mirage2 required -- plus it
> drastically lengthens the time it takes to build DSpace (unless you
> preinstall all of Mirage2's dependencies).
>
> But, for the longer term, I definitely agree we should rethink this
> idea. With 5.0, this was our first experience making any modules
> "optional", and we've obviously hit some snags in the release process
> because of this. Going forward (for 6.0 and beyond), we may want to
> consider whether we even want to allow for optional modules...or if
> anything that is "optional" should really just be a separate project in
> GitHub (similar to the plan for LNI). In that situation, users can
> choose to optionally download and install these extra modules into their
> DSpace.
>
> Just some initial thoughts here,
>
> Tim
>
> On 11/14/2014 4:03 AM, TAYLOR Robin wrote:
> > Hi all,
> >
> > Was away yesterday so just read the notes from the developer meeting.
> With regards to our Maven optional modules, rather than finding a way to
> accommodate them in our Pom's should we maybe be looking to not have
> optional modules? The expectation is that the LNI will be dropped for the
> next release so that currently just leaves Mirage2. Personally I think a
> number of the features that Mirage2 introduced, such as the use of SCSS and
> the management of Javascript, are going to become standard for many web
> applications. So it may be that we should move towards integrating these
> features into other themes, meaning that Mirage2 could just become another
> theme and no longer need to be optional.
> >
> > Cheers, Robin.
> >
> > Robin Taylor
> > Main Library
> > University of Edinburgh
> >
>
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
> _______________________________________________
> Dspace-devel mailing list
> Dspace-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-devel
>
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
