If such a thing were created, and to avoid the stated problem, all configuration would have to go into the configuration UI. on the other hand, the counter to the conflicting configuration changes is simple... if you provide a UI, those who like the UI, will tend to use it exclusively, while those who don't won't. You could also just allow it to generate the XML, and then let someone manually merge them into the config files.... I for one would like an easier way to setup the Chart of Accounts at the very least. And map an organization to accounts in the chart of accounts.
On 12/13/07, Adrian Crum <[EMAIL PROTECTED]> wrote: > Marco's recent work in Jira brought this issue to my attention: > > https://issues.apache.org/jira/browse/OFBIZ-636. > > I would like to start working on that feature. Since that issue was created, > comments have been made > in other discussions on the mailing list that may have an impact on the > implementation. > > The idea is to have a system configuration screen. David mentioned recently > in an unrelated topic > that having a UI for system-level configuration would be undesirable: > > "If you have a config UI it makes it even more difficult to manage because > if someone changes > something in the UI and someone else writing code makes a corresponding > configuration in the file > system, when the data is reloaded you might end up with a change loss > problem... and that's only one > scenario." > > At the same time, we do get requests for a configuration UI. > > So I'd like to work on this, but there is already a disagreement over whether > it should be done. > > Any ideas on how I should proceed? Does anyone see a need for such a feature? > > -Adrian > > > -- James A Barrows
