Quote from: PhyrePhoX on 16 / August / 2008, 10:57:42whim: i dont think that it'll work, besides you would increase build-time significantly, or i just didnt understand you correctly You could also use svn export to extract the distribution media (readme's etc). You can force whichever EOL style you want, and if you use the working copy form, it should be quite quick.
whim: i dont think that it'll work, besides you would increase build-time significantly, or i just didnt understand you correctly
I would suggest take latest svn export, apply linux linebreak with dos2unix for all files (besides readme.*, keep it readable for regular windows user) and commit changes back. Let's start with trunk, test it and than change braches too.This will cause some pain, but developer could apply same linebreak to there local syn export to reduce different to there source before compare or committing...Also it maybe a good idea to apply tidy to get a clean structur.... This require to custom tidy to our needs...This may cause additional pain... but some glitches made by tidy are easier to correct than the hole source...Project leader should make a decision about what linebreak and code layout should be used and than apply these changes to source once.I think, this is afford would be very usefull. Devs should not wait, otherwise this will get worse as chdk source expands!Every Windows dev should have a good texteditor like pspad, ultraedit, notepad+ or else installed anyway, so theres no problem using linux linebreak on windows. Don't be lazy .Maybe i'm wrong... just my 2 cent.
Its not just the line endings.Take a look at the tabs/indents. Its all hosed up as well.Some of the modules are really tough to read.There are different tab widths, indention widths, and some folks use spaces with no tabs at all.(I've struggled/fought with this issue on projects many times over the past 20+ years)I think much of this caused by most people assuming or wanting to force shift/indention widths to be equal to their tab width.Over the years I see so many people change their tab settings in order to change the look of their indentations.This is a horrible practice.The proper way is to set the indention/shift width separately from the tab width.Decent editors will allow this.Some folks think that they avoid the problem by not using tabs. But in fact they ruin the formatingas well because they align what they see on the screen to the tabs indention width set up in their editor.If their tabwidth was set differently from the one assumed by the file, their new text will not line upwith the existing text that used hard tabs.To me, hard tabs are 8. Period! Indents can be anything you want.Even though I abhor the practice of changing the tab width to somethingother than 8, at a minimum I'd like to see the tab width locked down to 1 valueor at least use the vi modelines to set the tab widths automatically.Those that checkin files with screwy misaligned indents, should be spanked 3 times with a wet noodle. Just my 0.02--- bill
svn help export
--native-eol ARG : use a different EOL marker than the standard system marker for files with the svn:eol-style property set to 'native'. ARG may be one of 'LF', 'CR', 'CRLF'
astyle.exe --brackets=attach --convert-tabs --indent=spaces=4 --exclude="readme.txt readme" --recursive
Started by whitis Feature Requests
Started by plschwartz Feature Requests
Started by jimdrake Hotwire! Hardware Mods, Accessories and Insights
Started by KC5TRB Script Writing
Started by Dave92F1 « 1 2 » General Discussion and Assistance
