bug-gtypist
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gtypist] learn to code


From: Felix Natter
Subject: Re: [bug-gtypist] learn to code
Date: Thu, 21 Mar 2013 18:19:11 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)

geoffroy tremblay <address@hidden> writes:

> Hi there, 

hello Geoffroy,

> Thank you for gtypist I finally learned to type :D 

That's good to hear!

> I wanted to see if I could use gtypist to help me learn javascript. One
> way I though would be great is to re-type library like jquery. Did
> someone created lessons like that already?

Why not, good idea :-)

> I would be interested too if there was any other 'source code' lesson
> already made for gtypist. 

There is only ttde.typ which does something like that in the last
few lessons, but that is German only.

> If not I was trying to use the jquery source code to create a lessons. I
> installed gtypist with apt-get from debian, so I had to download the
> source code to use the ktouch2typ script,

It's included in the debian package:
/usr/share/doc/gtypist/tools/ktouch2typ.pl.gz

> but it send an error about the
> XML/Parser/PERLSAX.pm, do I need to install some pearl library for that
> to work, or to compile gtypist to start with?

It looks like you need to install the libxml-perl package.

> Also would there be any problem to use code instead of text in lessons?
> I would also like to have the comments in the lessons, for example
> Jquery has quite a lot of comment which help to understand the code. 

No, not really. It is good practice to introduce characters such as {}
before you use them in drills/speed tests. You can have a look at
ttde.typ. Comments ('#') are treated as gtypist comments only if they
are at the very beginning of the line, so you can use '#' in lesson
content everywhere.

You might want to use Emacs or vim because we have highlighting support
for these editors (preconfigured for you on Debian) :-)

Good Luck and Have Fun!
-- 
Felix Natter



reply via email to

[Prev in Thread] Current Thread [Next in Thread]