sample/16f877a_startersguide_lcd.jal
I hope I am not stepping on anyone's toes by joining this this thread
but I can't help by put in my 2 cents.
mattschinkel wrote:
This is discussed before, but anyway: I think we need three books:
- the tutorial book (which has numerous, independent chapters that
describe in detail both hardware and software of a specific
application.
- a starterguide, that takes people by the hand and show various
aspects of JAL to create an overview, gets them up to speed.
- a reference guide, covering all aspects of jal (and the core of
jallib if possible) in a complete way and with examples, tips and
explanation of the core and related tricks.
I read the entire discussion before. the jal tutorial book takes users
by the hand as well in the "getting started" section. More documents
can be placed in that section if needed.
Each tutorial takes the user by there hand assuming that they did the
"getting started".
I have to agree with you Matt, the Tutorials are taking the user by the
hand, the same way Bert's Book did. The problem, as I see it, is that
the Tutorials are doing things to show how an application that the
Tutorial writers are interested in. That's why I didn't learn much from
Bert's book. I had no interest in 'any' of the projects it covered.
On the other hand I found the first Tutorial by Joep and Toon very
educational. It covered the language use in accomplishing a 'task' not
a useless, to me, project. That might just be me though.
An extended language ref as previously discussed here, would cover all
aspects of the language including the hard core. The tutorials
themselves and the "getting started" gives some coding techniques.
Is there anyway we can put them both
together?sample/16f877a_startersguide_lcd.jal
It is not trivial task to create a proper startersguide. It requires
well-chosen subjects that are used to introduce the relevant aspects
in a logica sequence. Much work for one man to write, but if you split
it, you create an additonal task for an editor. I decided for the
first option: do the writing myself (supported by Toon) to see if I
can achieve the goal. And since I work on my own, I use the most easy
tool for me, which is ms-word. Not easy for colaboration but best for
the job at hand.
I'll want to finish this job and release a version in PDF (with
copyright, since I want to stay in control of this document, at least
for now).
I don't see why we should merge them with the tutorial guide, but if
you disagree, I'll be happy to discuss this with you when the document
is out.
If the current project is a continuation of your first effort, Joep, I
would be happy to help you in any way I can. I taught students in
electronic theory, Medical equipment troubleshooting and programming,
too many years ago, and found that I had good results by teaching in a
similar manner to your first Tutorial. Logical steps (tasks) made for a
faster learn curve and created more interest for the students. This
worked here in the states and in Ireland, France, and in Japan. I only
had to fail a very few students, < 4, in 3 years.
It sounds like you want to go the same direction as bert, with
specific samples that are geared towards the book. If this is the
case, maybe you should make a seperate sample/lib file for this book.
The tutorial book uses existing jallib samples.
Is there a need for two samples in the sample directory both on the
same subject such as serial?
Matt.
I'm sorry if I offended anyone. That is not my intent.
Wayne
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en.
