From: Mark H. Wood [mailto:mw...@iupui.edu]
>3) "How can addons interject into the administrative interface?"
>
> Well, in DSpace 2.0 we'll have Spring underneath it all (as I
> understand it), and may be able to do dependency-injection tricks
> to cram new administrative UI into the existing structure. But how
> do we accomplish this in 1.x? We need a way to configure
> additional choices into the admin. pages. And if we build that.
> now, we may not have to work DI magic later.
>
> Come to think of it, maybe we ought to look at decomposing the
> existing admin. UI into features which *all* worm their way into a
> blank framework.
This is a very tightly focused question, which I think avoids the bigger
issues. I'm not an expert on xmlui, so there may be some issues in the current
configuration that would need to be addressed. But I don't see why it should be
that difficult to add new pages, or tag on features to pages with aspects.
Maybe there is an issue with modular addons contributing to the sitemap?
But there is also the question of how will multiple modules / addons co-exist?
Isn't it possible for one aspect to alter the DRI in a way that means a
subsequent aspect can't function correctly - so there would be a specific order
that those aspects need to be applied, or maybe they simply can't co-exist at
all?
If we expect to be able to simply drop in dependencies / modules / web
applications and expect everything to fit together magically, well, this is
going to be a concern...
>4) "And what do we do about the JSPUI?"
>
> 'tis a puzzlement. There are folk who know a lot more about JSP
> than I do, but I can't see any easy way forward to the modular,
> decentralized future of DSpace for JSPUI. It's just a page
> template language with lots of hair. Any ideas?
Quite right, JSP as technology fundamentally limits the possibility of modular
contributions of interface elements. In DSpace 2.0, there is a replacement that
uses Freemarker templates - these look very similar to JSP templates (although
minus all the embedded code), and can even utilise JSP tag libraries if that's
necessary.
However, these templates can be retrieved from a variety of locations - from
the web application directory, the classpath, JARs, filesystem, etc. - and in
fact, I already have examples of themes (CSS, images and some template
overrides) being supplied entirely from a JAR module that can be included as a
dependency to the web application.
So there is a distinct possibility for a new feature to supply it's own
separate pages from within it's own module. It's not going to give you
aspect-style weaving of features into pages, but then you can't always rely on
things happening magically ;)
G
------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
