[kepler-dev] Fwd: How to add a new module with recent build?

[Chad Berkley]

Hi Anne,

David forwarded your question to me.  The uiMenuMappings file is now 
handled by the configuration system and the default configuration is 
located in kepler/gui/resources/configurations/.  You'll note that there 
are a few different versions for different locales and languages.

You can change that file at startup for your module using the 
configuration override system.  You can see this page: 
https://kepler-project.org/developers/teams/framework/configuration-system-documentation/ 
for information on how to do that.  There are also a couple modules that 
currently use this functionality.  Take a look at 
https://code.kepler-project.org/code/kepler/trunk/modules/reporting/src/org/kepler/module/reporting/Initialize.java 
for a good example on how to override configuration options.

Let me know if you have any other questions.

Chad


On 10/11/10 11:54 AM, David Welker wrote:
>
>
> ---------- Forwarded message ----------
> From: *Ngu, Anne Hee Hiong* <angu at txstate.edu <mailto:angu at txstate.edu>>
> Date: Thu, Oct 7, 2010 at 8:18 AM
> Subject: RE: [kepler-dev] How to add a new module with recent build?
> To: David Welker <david.v.welker at gmail.com
> <mailto:david.v.welker at gmail.com>>
>
>
> Thanks.  I got it working now following your instruction.
>
> On a side note, it used to be possible to override the
> uiMenuMapping_en_US.xml in Kepler by just creating the same directory
> structure in own module with my additional menu entry.
> Since moving to Kepler 2.0, I found the system won't load my own copy of
> uiMenuMapping file. Is this a bug or a new feature?
>
> Anne
> ________________________________________
> From: David Welker [david.v.welker at gmail.com
> <mailto:david.v.welker at gmail.com>]
> Sent: Wednesday, October 06, 2010 9:24 PM
> To: Ngu, Anne Hee Hiong
> Cc: kepler-dev at kepler-project.org <mailto:kepler-dev at kepler-project.org>
> Subject: Re: [kepler-dev] How to add a new module with recent build?
>
> Hi Anne,
>
> If you want to have the CP module detected without making a new suite,
> but by editing modules.txt, you can just delete current-suite.txt or
> change the value to "unknown." The thing is, as the system currently
> stands, if current-suite.txt is specified, then in case of a conflict
> between the contents of that suite and modules.txt, the contents of
> the suite are used. So, if you want to just edit modules.txt manually
> without making a new suite, you have to make sure that current-
> suite.txt does not contradict it. This can be done by simply deleting
> it, or changing the contents to "unknown" (either course of action is
> functionally identical).
>
> -David
>
> On Oct 6, 2010, at 3:24 PM, Ngu, Anne Hee Hiong wrote:
>
>  > With the most recent checkout (two days ago) of Kepler, I cannot get
>  > my own module to compile and run  using the usual "ant run" command
>  > in the build-area directory.
>  >
>  > For example, I created  my own module called CP a year ago and I
>  > used to be able to get it compiled and ran by adding an entry at the
>  > top of the list in the  modules.txt file.
>  > Now, the system cannot detect my module.
>  >
>  > I notice that with the new build, there is an additional file called
>  > current-suite.txt,  do I need to do something with the current-
>  > suite.txt?
>  >
>  > Hope someone can enlighten m eon  how to use the new build to
>  > include a new module.
>  >
>  > Thanks,
>  > Anne
>  >
>  > _______________________________________________
>  > Kepler-dev mailing list
>  > Kepler-dev at kepler-project.org <mailto:Kepler-dev at kepler-project.org>
>  > http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>
>