User forums > General (but related to Code::Blocks)
Which widget library do you mostly use?
hd:
Hi,
I'm kinda "choose one and live with it" type.
Although this "choose" is a very hard/slow for me.
My toolkit history:
- self made (DOS)
- TurboVision (DOS) (Borland) (Incredible but, I still have customers using my programs written with it)
- VB3 (MS) (I'm still using it for legacy projects)
- Fox (3-4 projects)
- wxWidgets (I'm using it for about five years)
I evaluated/read many of the gui libraries out there.
Wrote some projects using Fox. Then decided to use
wxWidgets.
Note:
There is another toolkit: Juce
GPL, or Commercial license
http://www.rawmaterialsoftware.com/
--
Regards,
Hakki Dogusan
Roman:
Oh, my Holy S**t! There is a toolkit FLTK - this article pointed me to it (thanx Thomas). Surely cool. I couldn't vote for it because it's absence in the list but I would do it if it were. And a fltk.org does not seem as creepy as rumors say. With just a half of brain in the head (hope i have it) it is not a problem to get the things in 5-10 mins.
I have a questions to WX elders: Could Code::Blocks be implemented using FLTK - would it be as simple (sorry, devs, just a pun probably 8)) as with WX? Or does FLTK have serious limitations?
Roman
Grom:
The main problem of lots of GUI libraries, that they don't have any native development environment. In that case there is a gap between development of GUI designer and library development. The most successful story there in Borland IDE. They created a GUI library + developer, based on that library. When wx team will understand that - our life will be easier.
As a result I am using wxDevCpp and wxFormBuilder for GUI development and compile project in Code::Blocks :shock:.
If BYO will create something useful - probably even wx team start supporting it.
The main criterion here is to create a GUI designer with few sometimes contradicting tools:
* Platform independent.
* Customizable - you will be able to add your own packages of tools.
* Automatical event handling - you will be able to add an event handlers with mouse clicking, without any troubles like in wxFormBuilder, where you have to write your own handler.
* MLU support - to see the GUI structure + MLU based development.
* XML support - to import/export your GUI. Probably the GUI designer should be written around it.
Finally if BYO will implement only first three tools - the wx palette will start grow very fast, like it was happened with Borland IDE. In borland IDE you may create a huge GUI with smallest coding.
valkenar:
--- Quote from: sethjackson on June 24, 2006, 04:19:35 pm ---QT - umm yeah, but what is this meta-compiler thingamajig I keep hearing about?
--- End quote ---
I voted QT... the meta-compiler thing bugged me at first too, until I figured out a way to integrate the meta-compilation into the codeblocks build process fairly effectively. There's a thread I posted the method in somewhere around here, but once you set it up, it's very simple.
Basically, there's a tool in the QT distribution that you want to run your headers through if they use the signals/slots mechanism. The tool creates C++ code for you to compile into your project. It would be a pain to do it manually every time, but it's pretty easy to set it up once for each header file, and then just forget about it totally.
byo:
--- Quote from: Grom on April 11, 2007, 03:43:27 am ---... If BYO will create something useful ...
--- End quote ---
I use wxSmith for everyday work, and it works. So please, don't tell that my stuff is useless. I see that it does not meet your requirements (and you keep stating that for few months now), that really makes my "work" here harder (simply because it makes me discouraged).
BYO
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version