Re: [open-cobol-list] GUI -- wxWidgets?

[Joseph James Frantz (Aoirthoir)]

I like this idea a lot. The canvas gives us immediate GUI for now, which can be updated 
later on.

I'm ok with whatever method yall use, gtk+, qt, tcl/tk, whichever.

On Wed, Feb 18, 2009 at 10:21 AM, Ulf Dambacher <address@hidden> wrote:

Brian Tiffin schrieb:
> Hello everyone

>
> With the recent addition of libguile linkage How-To, GTK+ can also be accessed
> from the Scheme layer.  Anything on the Perl side can be accessed through the
> cob_perl side, so wxWidgets is definitely a viable option already.  I'm still
> working with Rildo's codebase to get smooth integration with Tcl/Tk
> (currently functional and samples have been posted), but I'd like to spend my
> whimsical time and attention on the GTK bindings.  There are a bag load of
> features that Glib, GDK and GTK open up.  One next step may be peeling back
> access to the GtkBuilder feature for XML UI design for those so inclined.

Hi together

I have some experience with  tk, gtk, qt and the old athena widgets and even did
my own widget set for (and natively coded in) gnu smalltalk.
For c programming and embedding in other languages I definitely recommend gtk+.
Also if you are concerned with windows/unix portability and licenses, gtk+ works
for you.

For "the old cobol coders" I think it's the best to provide folowing:
- A main window with text canvas, menubar and status line, both can be accessed
and modified via special accept/display additions, the normal display/accept
output goes to to the text canvas (maybe using a fixed font, but user
configurable lines/cols other than 80x24 chars).
This way  every cobol program gets a small X11-gui without code changes and this
could be an adaption of the current curses code to x11.

- a way to load these xml ui design files to fire up the dialogs and return the
result to a record in working storage area or by doing calls to get them.

- everything should work just with the gui builder without the need of further
linking and additional non-cobol sources.

I think 80% of the cobol users will be happy with this and its possible to code
this glue layer in short time.
And if nobody does it, I will start this. But I am currently commited in porting
my codebase to OC so It will be April until then.

/ulf

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
open-cobol-list mailing list
address@hidden
https://lists.sourceforge.net/lists/listinfo/open-cobol-list

-- 
Joseph James Frantz
(Aoirthoir)

http://www.add1tocobol.com
Regular add1tocobol meetings:
Where: FREENODE IRC
Channel: #add1tocobol
Access from the web: http://www.add1tocobol.com/chat.php
Date: Sundays
Time: 9:00am Eastern

::::::::NOTE IMPORTANT::::::::::
There has been some confusion as to the time. I believe this is because the United States uses Daylight Savings Time. On top of this the Government recently extended the dates that EDT (eastern daylight time) would run. So to be sure that you make it at 9am Eastern, I have this link:

http://www.timeanddate.com/worldclock/city.html?n=179

That shows the time in New York City at the moment of viewing. It also explains the current UTC offset for the Eastern Zone in the United States. Simply compare the current time that site states, with your current time and you will know how far off we are from you.
::::::::::::::::::::::::::::::::

We're there all of the time, even when we do not have a meeting. Stop on by for Open Cobol Support and chat.