If you have a framework, you can build small programs or test code and save them in a project for easy retrieval the next day or week. Then you can add functionality a little at a time. Also, the framework usually provide example code, templates, and help files to get someone going in a hurry. A command window is fine, but limited, as the code go away when the window is closed. I believe its better to have test/learn code in a file that can be run and debugged.
Regards, LelandJ Ed Leafe wrote: > On Jul 9, 2007, at 12:48 PM, Leland F. Jackson, CPA wrote: > > >> Can't the basics to which you referred be learned within the >> framework, >> or as a subset of the languages used by the framework? For example >> perl, python, php, java, c#, or pick your own. >> > > It is the imposition of a framework that is the problem. There is > just so much stuff that comes along with mega environments that > newbies can get overwhelmed by. > > My choice is a command-line terminal. Hell, if you have a problem > typing commands, you've just saved yourself a lot of grief, since > programming obviously isn't for you! > > -- Ed Leafe > -- http://leafe.com > -- http://dabodev.com > > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
