GUI development / image processing library

[Marek]

Hi Pablo,

 That means project must start using libjpeg, libtiff and libfftw.
You may as well start using it to read jpeg and tiffs (instead of
imagemagick
as it was in ptopengui) (if you're not using them already).


This may also mean good-bye to platforms other than unix (linux) and
windows.
So at that point why not start using GTK instead of wxWindows?

I would like to start participating in that project but I would like to know
the arguments for using wxwindows against other and more popular
cross-platform
gui framework (like GTK).

>From what I understand wxWindows doesn't come with
most linux flavors (doesn't come with Slackware 9 and I couldn't find a
package for it).
On top of it hugin already uses XRC which is a contrib to wxwindows and
requires
getting another packages (or compiling it manually)
So basicly to use it on any platform one would have to install wxWindows
(which
requires 60 (!) MB of space according to this page
http://www.wxwindows.org/manuals/2.4.0/wx7.htm#requirements ). The only plus
of it
over gtk is that it exists on Mac (if hugin would compile there anyway)
(I just don't know if gtk exists on mac).

With gtk hugin would run smoothly on windows and linux - on windows it could
come with couple of dlls in its home dir, and every linux distro contains
gtk
libraries now. there's also a nice gui designer - glade. It creates a lot of
files
and very complicated makefiles, but one could use it just to generate gui
and create
makefiles on one's own. It also contains similar capability to XRC through
libglade.
It has a much larger community than wxwindows (and therefore support).

What are the advantages of using wxWindows over other gui toolkits?

--
Marek

> -----Original Message-----
> From: ptx-bounces at email-lists.org [mailto:ptx-bounces at email-lists.org]On
> Behalf Of Pablo d'Angelo
> Sent: Sunday, June 01, 2003 7:24 AM
> To: PTX mailing list
> Subject: GUI development / image processing library
>
>
> Hi!
>
> I'm currently putting some functionality into the control points tab,
> like the selection of control points.
>
> This will show how the gui can work together with the model (in a
> complicated case ;)
>
> I'm also adding my template matching code. One thing I'm missing (also
> with QT) is advanced image processing operations. wxwindows doesn't even
> have a greyscale image type.
>
> I've started to use VIGRA
> http://kogs-www.informatik.uni-hamburg.de/~koethe/vigra/
> for some functionality. It is basically a STL for images.
> It comes with many useful operations (I might need some of them
> in the future), and can easily work on top of existing image classes.
>
> It is released under an Artistic like license. Basically I only need the
> image processing stuff right now, which is just a bunch of
> headers (because
> its all template based). Importing and exporting images (for debugging ;)
> requires a lib, but I can use the wxwindows functions for it
> instead. It can
> therefore be included into our source without requiring the user to
> install vigra on the system.
>
> I hope its ok to include the lib. Is the Borland c++ compiler
> is reasonably up to date and supports the current c++ template features?
>
> ciao
>   Pablo
> --
> http://wurm.wohnheim.uni-ulm.de/~redman/
> Please use PGP