From: Hiroo H. <hir...@co...> - 2005-02-03 06:28:57
|
Hi, Joachim> Please have a look at the changes whether they are OK. Basically I agree with you. You replaced original> Preferred indentation level is 4. by follows; new> <p><strong>Important:</strong> Use an indentation level of 4 This is stronger than before. I hesitated to force synth driver developers the indentation level. I did not change indentation of synth drivers except for Kawai K4. I did it for Kawai K4 with Brian's approval, because it is a reference driver. I'd like to hear the comments from others. new> and a "tab stop"/ "displayed tab width" value of 8.<br> new> The reason for this is compatibility with:</p> new> new> <ul> new> <li>... Emacs in Java mode which replaces 8 blank spaces to 1 tab if possible.</li> new> <li>... Unix command line tools like cat, less, tail, ...</li> new> <li>... viewcvs, the CVS browser that SourceForge uses.</li> new> </ul> Emacs is extremely flexible and has no problem for any style. Instead of that, "notepad" for Windows is another good example. The point is that there are many widely used tools which supports only displayed tab width 8. We have no choice here on a group project like JSynthlib project. And it is the default setting even for tools which can change the setting. (I forgot the default setting of Eclipse. It might be an exception.) We can just say "don't change the default setting." new> The JSynthLib team recommends the use of <a new> href="#setupEclipse">Eclipse</a> which is able to support this new> settings.<br> Do we? I personally strongly recommend Eclipse, but I don't want to do it as the JSynthLib team. I'd like to let developers to use any tool he likes. I believe there is no tool which cannot set the display tab width to 8. new> Text editors that also support these settings are new> e.g. <a href="http://www.jedit.org/">jEdit</a> and <a new> href="http://scintilla.sourceforge.net/SciTE.html">SciTE</a> new> which are both open source and availabe for Linux, Mac OS X and new> Windows like Eclipse. I don't think we need this info here. Let's put this on the section "What do I need in order to add support for a new synthesizer?" And seeing the balance of whole this chapter, it may be better to move the part starting "The reason for this is ..." to FAQ chapter and to make a link to it from here. -- Hiroo Hayashi |