SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-Programming Mailing List Archives

Return to [ 16 | January | 2006 ]

<< Previous Message <<


Date: Mon, 16 Jan 2006 20:21:11 PST8
From: Sheridan George <s-geo@usa.net >
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com
Subject: SCOUG-Programming: Pushing ahead

Content Type: text/plain

Lynn H. Maxson wrote:
> Greg,
>
>

current standard of 2 hours. Thus at the moment for all the
> previous reasons I would favor VIM over jEdit and Python over
> VIM.
>
If VIM is simple enough to understand and then to modify but "stout" enough to do the job then let's
use it.

Any use of Python is good by me.

Python has an editor that comes in the Windows distribution (also, Unix/X Window Systems). It
requires Tkinter, a graphics program, that had been ported to OS/2 but but dropped (
http://mail.python.org/pipermail/patches/2001-November/006470.html ) because it doesn't work any
more. The reason why may be Tkinter also requires TCL and TK (
http://gnosis.cx/publish/programming/charming_python_b2.html ) and those ports haven't been kept up.

I still think our first task should be to develop a list, or maybe specifications if you insist, of
all the things we need (editor - other than well known editing functions and packaging our
specialized source commands and sending them to a DBMS, what else must it do?; DBMS - any special
things it must do?; compiler - I know it will probably have to be multi-pass, maybe draw source code
from the DBMS [or maybe that is the editor's function also] but what else?; glue functions, ect.) to
put this system together. I feel we are in a swamp without a map.

Sheridan

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".

For problems, contact the list owner at
"postmaster@scoug.com".

=====================================================


<< Previous Message <<

Return to [ 16 | January | 2006 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.