I confess I much prefer tabs, because they show up as one character
per indent level which minimizes counting, the tab widths are
adjustable in most editors, and they are not nearly so prone to off-by-one
errors like having three or five spaces instead of four somewhere.
On Mon, Mar 07, 2011 at 03:12:50PM -0500, bT wrote:
Hi Again,
Another note on the editor you use. Some also can do auto indent which is
nice, but having to write your own and doing your own indent, forces you to pay
attention to your code.
the scripting language to learn is Python and it has many versions,
including writing using window commands or WX Python or WXPythong.
Python is an indent language. You must indent loops and such or an error
will occur.
Learning that language forces you to indent each block of code. It is a
nice way to get yourself into good practices. Pygame or Py Game is used for the
sounds and such. It just has that nice ring to it because it is good for
writing games and getting good keyboard/mouse controls along with sound.
Just use a 4 space method for each level of a block for indents. Some
people use tab but spacing allows you to check your code by going up or down
each line and find out where the start of the line is and what it is aligned
with. By doing this it allows you to also go over your code.
It is just a suggestion and each person is use to there own ways and it
depends on what you are doing and your needs.
Bruce
Sent: Monday, March 07, 2011 11:46 AM
Subject: Re: WE scripting class #3 in a few minutes
Hi Bruce: What editor are you using that has line numbers? Chip is using the
Office Product line which I don't have.
Rick USA
----- Original Message -----
From: "Chip Orange" <[email protected]>
To: <[email protected]>
Sent: Monday, March 07, 2011 8:11 AM
Subject: RE: WE scripting class #3 in a few minutes
> ok Bruce! great idea.
>
> Chip
>
>
> -----Original Message-----
> From: bT [mailto:[email protected]]
> Sent: Sunday, March 06, 2011 11:44 PM
> To: [email protected]
> Subject: Re: WE scripting class #3 in a few minutes
>
>
> Hi Chip,
>
> thanks for the info. I added my sapi45class and noticed the one error
> on
> line 347where wscript was for the sapi4 sleep method. So, since WE does
> not
> require the wscript and no object available, I added the on error resume
> next and tested for err.number = 424 and just called the sleep method and
> it
> works.
>
> So, my first test inside we worked fine despite the little hitch which
> I
> cured.
>
> The little things inside we scripting that is different. Learn by doing
> as they say.
>
> Bruce
>
> Sent: Sunday, March 06, 2011 9:49 PM
> Subject: RE: WE scripting class #3 in a few minutes
>
>
> fyi, the audio classes archive has been updated from tonight's class and
> is
> at:
>
> http://acorange.home.comcast.net/scripting
>
> Chip
>
>
> -----Original Message-----
> From: Chip Orange [mailto:[email protected]]
> Sent: Sunday, March 06, 2011 6:54 PM
> To: [email protected]
> Subject: WE scripting class #3 in a few minutes
>
> just a reminder: today we'll actually get past some of the background and
> write some small programs.
>
> Chip
>
> If you reply to this message it will be delivered to the original sender
> only. If your reply would benefit others on the list and your message is
> related to GW Micro, then please consider sending your message to
> [email protected] so the entire list will receive it.
>
> GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can
> manage your list subscription at http://www.gwmicro.com/listserv.
>
--
Doug Lee, Senior Accessibility Programmer
SSB BART Group - Accessibility-on-Demand
mailto:[email protected] http://www.ssbbartgroup.com
"While they were saying among themselves it cannot be done,
it was done." --Helen Keller
