> So an alternate approach might be to develop an Eclipse plug-in
> to add the data store with automatic invocation of the GCC or
> Watcom compilers.
>
Not having used Eclipse but having read a fair amount about it, I sure would like to look at
building a plug-in to accomplish the data store stuff instead of mucking around in an editor. I
understand great effort has been expended to make plug-ins relatively simple to code.
I like jEdit very much. I use all of the time for Python and what little Java programming I do.
But, even before I knew it was 2000 pages of Java code, I thought it would be way too complex to
easily modify. It does a lot more than we want. We are trying to lessen the amount of stuff that
has to be/can be done.
Might I point out that this discussion is exactly why I suggested we need to make a road map of what
we must do. Let's start with an ordered list of all the things we must accomplish and then start
tackling those items.
I have more to say but it will have to be later. I'm being rushed out the door.
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 <<
>> Next Message >>
Return to [ 14 |
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.