Hi Mark,
Most of what we've changed in existing aspects has been very straight-forward.
I'm reluctant to add or customize essential information (contacts, feedback
forms, help pages, etc.) in the theme layer. I'd prefer this information to be
available should we need to change themes or
Well, this is all a bit tangled.
Themes are a special case. You can develop them *anywhere*, so long
as a copy of your Theme gets put where DSpace looks for it by the time
you want to try it out. It doesn't have to be *anywhere* in the
DSpace source tree because it isn't compiled against
Jennifer,
On Mon, May 30, 2011 at 8:17 AM, Jennifer Whitney jwhit...@unb.ca wrote:
Bit late to the party but I thought I'd share our approach for keeping
XMLUI customizations separated from DSpace source. Recipe #1 has worked
well for us, so far, when we've needed to modify 1.6.2:
Bit late to the party but I thought I'd share our approach for keeping XMLUI
customizations separated from DSpace source. Recipe #1 has worked well for us,
so far, when we've needed to modify 1.6.2:
https://wiki.duraspace.org/display/DSPACE/BuildCookbook
So, for example, we've cloned the
Hi, Joseph, as you can see opinions differ on the best practice. I can tell you
that, for a long time, I tried to do theme development using Maven overlays.
However, I ran into trouble many times, when searching for a solution (or
asking for help, myself) many answers from developers will
For quick clarification:
On Fri, May 27, 2011 at 8:09 AM, Joseph joseph.rho...@gmail.com wrote:
Dear Dspace-Tech,
This is more of a general best-practices question.
Where should new themes we develop live?
1)
dspace-source/dspace-xmlui/dspace-xmlui-webapp/src/main/webbapp/themes/
Bad
Dear Dspace-Tech,
This is more of a general best-practices question.
Where should new themes we develop live?
1)
dspace-source/dspace-xmlui/dspace-xmlui-webapp/src/main/webbapp/themes/
2)dspace-source/dspace/modules/xmlui/src/main/themes/
The first is what is suggested on the Manikin Theme
Are you able to enable them in the xmlui.xconf at all?
Mark
On Fri, May 27, 2011 at 8:09 AM, Joseph joseph.rho...@gmail.com wrote:
Dear Dspace-Tech,
This is more of a general best-practices question.
Where should new themes we develop live?
1)
Hi Joseph,
Best practices recommendations will tell you to put all of your
modifications into [source]/dspace/modules, however, that isn't the most
efficient way to do things (for me atleast).
The straw that broke the camels back for me on the matter, was when I was
customizing dspace-api
Joseph,
I will say there are dramatically differing opinions on this in the
community. While I see the benefits that Peter points out, as he says it is
an approach that requires you to use tools that will aid in tracking and
merging your modifications. Peter is creating much code for
10 matches
Mail list logo
