Thanks Thomas for your big reply<div><br></div><div>I have seen it after I&#39;ve written my last reply.</div><div><br></div><div>The first thing is, the rule of proofreading twice is one of the lowest level to achieve quality.</div>
<div>The question wether it must be enforced by software or not. If it would be easy to configure this problem will be solved. The default setting should be software control enabled.</div><div><br></div><div>The solution we had with horizontal and vertikal layot (nearly the same as a fork) was not the best at all - you mentioned the problems correctly. The new solution to incorporate as an integral part of the system is perfect. Using horizontal on a pivot 24&quot; monitor and vertical on 22&quot; widescreen is  perfect. </div>
<div><br></div><div>The next thing.  OK your not the guy who decides when a code update goes alive, but if you could tell everbody that there is a code change to come in the near future, because you&#39;ve finished your work for the next update, together with an information what is new or what will change, would help to inform the people in advance that something will happen. Frustration will be minimised by that. A link in the scriptorium to the information would be enough. The information should be in english, because we are laking french speakers, but even german will fit :) </div>
<div><br></div><div>One of the things we are really missing are programmers with good kowledge of js. We will have a look at your idea within the bugzilla 20817#c7 an may come up with a lot of questions.</div><div><br></div>
<div>I could understand your frustration, because of the &#39;&#39;dictating&quot; local admins. I m sure that I am one of these bad guys.   </div><div><br></div><div>But we  have to cope with the frustration of our community members, when things don&#39;t work the same way they are used to, or when the aren&#39;t allowed to proofread any more. And things like that su...  If there is information in advance, i could say didn&#39;t you read the scriptorium, instead of searching for the reasons. After some research - uups there was an update, I for my person need in such a situation someone to blame it on, especially if this is not the first time for this special extension. Hopefully understandable.</div>
<div><br></div><div>We should find a way of cooperating. I think when the information flow increases, and you give us hints (preferably in advance) how we can achieve our goals with your new releases, we could have a much better climate. A lot of good things in your extension will not be recognised, because of the things were are upset</div>
<div><br></div><div>And I agree ThomasV it would be more than foolish working on a fork - and loosing the future enhancements - or on a new proofread extension (Version 3). There is an existing system which works (except for our principal differences) really well. And one configurable extension for all is the only usefull system.</div>
<div><br></div><div>And if you can tell me names of js specialists which are <b>active</b> administrators on <a href="http://de.ws">de.ws</a> I would be really happy.</div><div><br></div><div><br></div><div>greetings</div>
<div><br></div><div>joergens.mi</div><div><br></div><div><br></div><div><br></div>