> ... I think even SDK users can/should use the framework code both as > additional documentation and as example/howto code "properly" with > Qooxdoo. > > For that it will help to at least have consistent EOL style in all files > (and I guess any current existing differences, if any, should be > considered > a bug).
This is taken care of as we run through all relevant framework files before packaging up the SDK. > It might (!) be useful to provide two different SDKs, one with Unix and > one > with Windows kind of eol style. We had this before (I think until early 0.8.x releases), but many people (me included!) were happy that we got rid of platform-specific packages. I think it's simply not worth it. > And for this it would certainly be useful to have SVN handle the variants > by > using the 'native' eol handling as Derrell already pointed out (and again > I > think any deviations from the SVN native propery should also be considered > bugs and fixed). Again, I think it's not worth it. eol-style:native is a nice feature, but maintaining it throughout the framework seems to be a drag. And what for? Most people I know working with SVN don't even notice the eol style of the files. Why should "deviations from the SVN native property" be considered a bug? As a matter of principle? I don't see a good reason why this should be an issue. T. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
