Ed Leafe wrote:
I've run into a lot of people who use tabs but who convert to spaces
for "public consumption" because of the pressure to use spaces.
We should encourage them not to do that.
There are certain things I miss about spaces, such as lining up
continued lines so it "looks good",
Keep in mind that what "looks good" in your monospaced font looks
terrible in my proportional font.
Using proportional fonts for source code is a different argument
entirely. At least with mono fonts it has a chance of looking good.
I guess it wouldn't be too hard to have AppWizard convert leading tabs
to spaces as one of the final steps when writing out a generated file.
I guess we'd also have to allow the user to specify the number of
spaces, since some people like 3, others 8, etc.
Maybe have a small checkbox tucked away at the bottom of the
next-to-last page with small type that says "Use spaces instead of
tabs". If they check that, show another page that allows them to set the
spaces-per-indentation value. You might also add a witty remark about
the inferiority of spaces for indentation, but I'll understand if you
don't. ;-)
cb.Caption = "Tabs rule! But check this box if you disagree."
Is this a worthwhile endeavor? If we do it in AppWizard we'll probably
be asked to do it elsewhere too, such as in the class designer, report
designer, etc. etc.
We aren't generating code anywhere else. The Class Designer creates
a .py file; users can type whatever code they like in the editor, using
spaces or tabs.
You don't choose the indentation for the def statements for methods?
--
pkm ~ http://paulmcnett.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
