Changes between Initial Version and Version 1 of Ticket #911, comment 12


Ignore:
Timestamp:
Sep 30, 2016, 9:53:55 AM (8 years ago)
Author:
olle

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #911, comment 12

    initial v1  
    22
    33 * Allowing a project to have its own name prefix for samples etc. is one of the more challenging tasks in providing multiple project support for MeLuDI, since choices for the original MeLuDI project were hard-coded in several places in the code.
    4  * Settings for different projects can also be stored in a number of ways:[[BR]]a. Hard-coding settings should be avoided if possible, since a change would require a new program version to be released.[[BR]]b. Direct coupling to a BASE project item would be preferable, but annotations cannot at present be coupled the latter. Otherwise such a solution would have allowed a person with administrator permission to add and configure a new project, without the need to restart the BASE server.[[BR]]c. Storing project settings in a configuration file requires an administrator to add and configure a new project, and the BASE server has to be restarted.
     4 * Settings for different projects can also be stored in a number of ways:[[BR]]a. Hard-coding settings should be avoided if possible, since a change would require a new program version to be released.[[BR]]b. Direct coupling to a BASE project item would be preferable, but annotations cannot at present be coupled to the latter. Otherwise such a solution would have allowed a person with administrator permission to add and configure a new project, without the need to restart the BASE server.[[BR]]c. Storing project settings in a configuration file requires an administrator to add and configure a new project, and the BASE server has to be restarted.
    55
    66The first version of project-specific name prefixes in MeLuDI will be based on storing the settings in a configuration file. In order to allow as much flexibility as possible for future changes, the solution will be based on the configuration file management in Reggie, where settings are stored in XML format. In Reggie the file is named `reggie-config.xml`, and will be named `meludi-config.xml` in MeLuDI.