YelloSoft http://yellosoft.us/ I complain about the very same thing. There hasn't been a lot of development effort for building anything cross-platform. Out of fifty LISP implementations I looked at, only a few were cross-compatible. Hardly any computer games are multiplatform. I build my own software and release it on Mac, Linux, and Windows whenever possible. It's been really easy starting with a common code base (…
Ask HN: An acceptable cross-platform GUI toolkit?
41–50 of 57 posts
Re: Ask HN: An acceptable cross-platform GUI toolkit?
#42I'm quite surprised to see that nobody has mentioned fltk ( http://fltk.org ). It is light, easy to use, and it uses a modified gpl license that allows linking against non-free code. And it has native look and feel too...
Re: Ask HN: An acceptable cross-platform GUI toolkit?
#43Re: Ask HN: An acceptable cross-platform GUI toolkit?
#44(powers firefox, songbird, miro, thunderbird, activestate commodo ....)
Re: Ask HN: An acceptable cross-platform GUI toolkit?
#45Re: Ask HN: An acceptable cross-platform GUI toolkit?
#46If you're really picky about the look-and-feel on each platform, just bite the bullet and write 3 front-ends. If you want something that looks reasonably good on major platforms, go with Qt or wx. There are a couple more options you have: XULRunner: I like this option because of the flexibility you get in creating UIs using markup and styles. You can get XULRunner built with Python support so you don't have to resort…
Re: Ask HN: An acceptable cross-platform GUI toolkit?
#47Earlier quoted context omitted.
How I wish I could forget Swing.
> How I wish I could forget Swing. Could you explain why? Last time I used Java ( years ago), Swing was supposedly replacing AWT. Swing seemed very large (certainly, judging by the page-count of all the Swing books on bookstore shelves), and required a lot of subclassing to use. When I tried it out, it was slow, to be sure, but it was also relatively easy to use. The layout managers worked well for my simple apps. I…
Re: Ask HN: An acceptable cross-platform GUI toolkit?
#48wxWidgets is "big" because it has features. Considering it meets all your other criteria (aka features), in addition to ones you'll only find out you need halfway through a project, I would look closer at it. Use wxGlade and wxPython if you want easy, C++ if you demand compiled. Use dabo ( http://www.dabodev.com ) if you are interfacing with databases.
Re: Ask HN: An acceptable cross-platform GUI toolkit?
#49I couldn't agree more that all of them have major drawbacks. We need a good, simple to use, well-designed, fast cross-platform C library.
Do you care to start doing it? Other than doing your own, I think the most sensible choice is wxWidgets, which, from my point of view, only has one big problem: the API (i.e. code doesn't look pretty, bad C++ (no exceptions), and it can take a while to compile).
Re: Ask HN: An acceptable cross-platform GUI toolkit?
#50The current Tk (8.5 and above) looks a lot better, using native widgets where possible, and Starkit makes deployment of Tcl/Tk applications a breeze. Those who forget history are doomed to reimplement it.