From graphics-request at octave dot org Fri Dec 17 03:44:41 2004 Subject: Re: Octave GUI API: Proposal. From: Ole Jacob Hagen To: graphics at octave dot org Date: Fri, 17 Dec 2004 10:42:11 +0100 Hi. Nice that this is a scope of interest. ;-) I hope you are planning a toolkit-independent GUI layer? How will you achieve this? Example that user can decide whether he will use gtk, Qt or wxWindows to mention some. I'm aware that Qt is a commercial software on Windows, but there is an alternative. This alternative is Qt-package developed by kde-cygwin project at sourceforge. They are porting the Qt/X11 to Windows. I've contributed some code to the OpenGL module. I've compiled and build this qt-3 package natively on Windows with MSVC, so my Qt-applications runs without cygwin/X11. They are not linked to cygwin.dll either. ;-) I believe kde-cygwin project will release a binary that doesn't require any compilations, so users don't need to use MSVC. You can always compile with mingw, if this is prefered. We are also planning to make a octave-internal graphics object handler, but have made a Props package to Oplot, which is an external library that comes with Oplot. This package is using callbacks, when a property has changed. If we have the same goals we could help eachother out, I guess. Cheers, Ole