Thanks, Mark! This is a big help. Rick is right: none of this is so esoteric that a competent technician cannot easily learn it. My problem is that is all so unfamiliar and with such a different paradigm that at first everything I do is wrong. There is so much to learn besides the specific task at hand. There is, however, only one way to learn to swim and that is to get into the water.
Like many others, I have three innate horrors: stepping on something, like I almost did, writing bugs that others see, which I do all too frequently, and looking stupid, which is, I guess, unavoidable. I pulled down the 3.2 source tree to a directory structure (not svn) and I am now looking through it. If I can write Autocoder I can surely apprehend this code. When I think I have the understanding, I will work on the task asking for a file in each directory explaining the contents. At least when I finish that I will understand the structure of the project. As far as defining a mission: ooRexx is a general-purpose programming language with OO syntax that is interpreted in the manner of Java and the .NET languages and which may be installed on nearly every modern execution platform. In its simplest form it is a very flexible scripting language and in its full form, with BSF4REXX, GTK+, FTP, and RDBMS connectivity, it is an ideal Enterprise programming tool for functional tasks as well as for "glue" in the heterogenous environments which have become common. It is easier to understand and simpler to write than C++, having had little of the committee politics, and it is actively maintained and enhanced to meet the emerging challenges of our industry. It can be surrounded with a full complement of development tools and for a small to medium-sized shop it can provide strong productivity gains and ROI over proprietary toolsets. For large, Enterprise environments it can mesh with the other elements of the environment and still provide the same benefits as it does in the smaller shops. Prototyping is only one small part of its advantages; Open Object Rexx is a programming tool whose depth and breadth is unmatched by similar but more narrowly-focused tools. -----Original Message----- From: Mark Miesfeld [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 01, 2008 22:32 To: Open Object Rexx Developer Mailing List Subject: Re: [Oorexx-devel] Socket.cls and StreamSocket.cls On Wed, Oct 1, 2008 at 8:55 PM, Dan Carter <[EMAIL PROTECTED]> wrote: > Rick has a point. As usual. <grin> > Now, if someone will just give me the userid and password I need to > actually enter the repository and look at it in Tortoise, I will > proceed. The message box is attached. You don't need a user name and password to just check out the source, only to commit back into the repository. I only use the command line version of svn, so I am hazy on what is needed for TortiseSVN. With the command line version you would just name the portion of the repository you wanted to check out: E:\work.ooRexx\3.x>svn co https://oorexx.svn.sourceforge.net/svnroot/oorexx/main/trunk my.source A my.source\oorexx.ver A my.source\unix-like-build.txt A my.source\rexxapi A my.source\rexxapi\server A my.source\rexxapi\server\QueueManager.cpp A my.source\rexxapi\server\APIServer.cpp A my.source\rexxapi\server\platform A my.source\rexxapi\server\platform\unix A my.source\rexxapi\server\platform\unix\APIService.cpp A my.source\rexxapi\server\platform\unix\rxapid.in A my.source\rexxapi\server\platform\Makefile.am A my.source\rexxapi\server\platform\windows A my.source\rexxapi\server\platform\windows\rxapi.rc A my.source\rexxapi\server\platform\windows\APIService.cpp A my.source\rexxapi\server\platform\windows\rxapi.ico A my.source\rexxapi\server\QueueManager.hpp The 'co' (check out) command is all on one line. With tortoiseSVN, right click inside a directory (in Windows Explorer) where you want to download to. Pick SVN Checkout from the menu, picture attached. Fill in the "URL of Repository" field with the information. In my command line example it would be: svn co https://oorexx.svn.sourceforge.net/svnroot/oorexx/main/trunk Fill in the "Checkout directory" with where you want it put, in my example it would be: E:\work.ooRexx\3.x\my.source and go. You can also browse the repository in a web browser by going to: http://oorexx.svn.sourceforge.net/viewvc/oorexx/ -- Mark Miesfeld ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
