On 12/10/2010 12:40 PM, Bruno Busco wrote:
Or, maybe those certain things should not be enabled by default. Maybe move
them to a specialpurpose location, which then extends the
framework/application components with additional menu/screen entries.
We could also manage a patch committed to the SVN that is used for the demo
server.
The patch should be applied on the demo only and disable whatever we like.
Sure, having a patch applied after a checkout is good. But that patch
would have to be updated as svn changes; this is bad.
The urls we are discussing generally wouldn't be useful in a
production environment, but you would want them during development.
This goes for everyone who would be wanting to use ofbiz, then
eventuatlly deploy. So, a general purpose solution should be
designed, not a one-off that is only used by the demo instances.
