I think it's essential. I'd be interested in contributing - after I finish
the ooDialog Guide of course.
Off the top of my head, there seem to me to be three fundamental things
about ooRexx that newbies should learn first and they are:

(1) oorexx is "typeless" (of course it isn't - but when you've spent your
life having to declare types for utterly everything - int, long, float,
double, struct, hex, char, string, decimal (if you're lucky), etc. etc. -
ooRexx is either seriously weird or it's utterly wonderful. 

(2) Objects (of course) - ooRexx is probably the most oo language I've met
(which is good) but it's also procedural when you want it to be (e.g. in
methods). And there's a great selection of structured programming constructs
(e.g. I just love "do over").

(3) Strings - and the superb ooRexx functions (ok methods) for string
manipulation. Beats most (all?) other languages into a cocked hat.

Of course there's much much more - but the above three things are, I
suspect, essential first steps (or at least among the set of essential first
things). 

Pity there's no development environment. This could well put people off at
first. Needs thought about how to present it. Notepad plus a Command Prompt
will appear really Mickey Mouse - a huge leap backwards - to a newbie. 

--
Oliver Sims

 

-----Original Message-----
From: David Ashley [mailto:[email protected]] 
Sent: 17 September 2012 19:40
To: ooRexxDevel
Subject: [Oorexx-devel] ooRexx Getting Started Document

All -

After much deliberation on my part I believe that we need a new major
document that, for lack of a better title, I am calling "Getting Started". I
would like for this to be a complete tutloial of getting and using ooRexx
for the novice beginner. I think there is a huge audience for this document
if we can make it so that it can get the beginner started using ooRexx from
the object oriented perspective from the very beginning.

Using objects is such a huge leap for most casual programmers that they just
drop the whole idea of using ooRexx before they even get started.
So we need to give them some help in the form of a tutorial that starts with
simple object oriented concepts and builds on that base.

This document, once it has the basic outline established, could grow with
time with many people contributing to the it. There are many concepts to be
explained and it would need to have a great many simple examples.

So what does everyone think? I am willing to get it started and propose a
basic outline. I certainly do not have the whole idea for this in my head
and we would need to hash out an outline that everyone can agree with.

Let me know how you feel about this idea.

David Ashley


----------------------------------------------------------------------------
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat
landscape has changed and how IT managers can respond. Discussions will
include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to