User forums > General (but related to Code::Blocks)
Which widget library do you mostly use?
David Perfors:
I think it is a disadvantage that a toolkit doesn't use native widgets. People are used to those native widgets (especialy those who don't like to work with the computer). That is why I stopt using fltk. But indeed I like the size of it.
VCF is for me a good alternative for wxWidgets, although they are using mixed case filenames, which looks evil on *nix :P
Code Medic:
--- Quote from: mispunt on June 27, 2006, 10:33:08 am ---I think it is a disadvantage that a toolkit doesn't use native widgets. People are used to those native widgets (especialy those who don't like to work with the computer). That is why I stopt using fltk. But indeed I like the size of it.
--- End quote ---
I also believe that native widgets are better. First of all, they can provide an interface the user is used to and secondly it should be faster on highly evolved GUI systems ... but on the other side of it.. the stability and functionality are restricted by the native GUI. I guess on *nix it doesnt make any difference as the X doesnt have a high level widget system.
--- Quote ---VCF is for me a good alternative for wxWidgets, although they are using mixed case filenames, which looks evil on *nix :P
--- End quote ---
:) but... isnt mixed case naming better?.. it makes the code readable and doesnt have to stretch the length of the variable/function name (with underscores)
David Perfors:
--- Quote from: Code Medic on June 28, 2006, 08:43:41 am ---
--- Quote from: mispunt on June 27, 2006, 10:33:08 am ---VCF is for me a good alternative for wxWidgets, although they are using mixed case filenames, which looks evil on *nix :P
--- End quote ---
:) but... isnt mixed case naming better?.. it makes the code readable and doesnt have to stretch the length of the variable/function name (with underscores)
--- End quote ---
Mixed case naming in source code is better, but filenames not. On *nix you can have the file HelloWorld.c and helloworld.c. On windows you can not... IMO that is a problem which should be avoided. (this problem shouldn't be there in the first place, so hopefully Mic.... is going to change that..)
Code Medic:
--- Quote from: mispunt on June 28, 2006, 09:10:54 am ---
--- Quote from: Code Medic on June 28, 2006, 08:43:41 am ---
--- Quote from: mispunt on June 27, 2006, 10:33:08 am ---VCF is for me a good alternative for wxWidgets, although they are using mixed case filenames, which looks evil on *nix :P
--- End quote ---
:) but... isnt mixed case naming better?.. it makes the code readable and doesnt have to stretch the length of the variable/function name (with underscores)
--- End quote ---
Mixed case naming in source code is better, but filenames not. On *nix you can have the file HelloWorld.c and helloworld.c. On windows you can not... IMO that is a problem which should be avoided. (this problem shouldn't be there in the first place, so hopefully Mic.... is going to change that..)
--- End quote ---
oops.... :o how did i miss that word...!!! my eyes need a patch..!
krisz:
Hi!
I use wxWidgets. For two reasion:
- Cross platform. When I switch paltform I have no the overhead of knowing another library. (This fits the intentions of C::B as well (at least in my opinion))
- Well documented and maintaned.
I agree that using macros in a C++ code is a bit awkward but wxWidgets was desigend far before the advanced C++ language features. I think once one got a grasp of it, it would not be a big disadvantage. However the support of the STL is a bit week but it makes me no overwhelmed.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version