On Jan 19, 2010, at 10:01 AM, Hans Bakker wrote: > > No problem with me Jacopo, i think that functionality will sell with > customers and therefore has a higher priority than here and there a > temporary hack...similar to the help system i have problems keeping > in....
I understand your point of view and frustration; also I agree with you that online help is a great feature (thanks for working on this, I appreciate it). However, dependency issues are a bad beast: once you create them, they root incredibly quickly as time passes and fixing them at a later point is a huge deal. We already have some of them in the framework, and we will have to fix it, but we should avoid introducing new ones. What does it mean for the help system? In my opinion we should deal with this problem in the following way: 1) remove the new dependency asap 2) save the removed code (from bi/example/webtools) in a patch and publish it in Jira so that it is available to users (we could also consider a branch, but maybe it is an overkill) 3) work on a solution for the dependency: migrating parts of the content (required by the help system) to the framework (there are definitely some parts of the Content that should stay in the framework) I hope it helps, Jacopo
