User forums > Using Code::Blocks
WxFormBuilder ...WxSmith
buntunddu:
Using WxGlade 0.5 and Codeblocks from 13.th April (Svn 3849)
on (K)ubuntu edgy 6.10
buntunddu:
Ok, i figured it out.... and i added the generated files into an empty wxwidgets project...
however..the compiler just gives me a lot of erros (yep, i checked the option generate c++ code :) )
I ill maybe give another go in some days...
When someone had similar problems plz post..
If i get it to work ill wirte again in some days..
RJP Computing:
--- Quote from: buntunddu on April 15, 2007, 04:10:38 pm ---Hi!
I just wanted to know, if anyone really can work fast, efficient and productive with
WxFormbuilder or even with WxSmith... cuz i cannot....
--- End quote ---
Yes, I can use wxFormBuilder fast and effiently.
There I will answer with an answer that is just as vague as the question. :)
What are your problems with wxFormBuilder and wxSmith? Exactly.
My guess is that you are not coding a full application, you are just coding a simple dialog to show a couple pieces of data. I mean no disrespect. There is nothing wrong with that, but why ask the question in this way? Why not ask for a GUI builder that can be used to generate simple user interfaces? I believe there is the right tool for the job.
If you are talking about wxSmith and wxFormBuilder being bloated then I have know idea where you are coming from.
Do you want help making wxFormBuilder or wxSmith work for you? Or are you happy looking at another designer?
buntunddu:
guessed almost right :).
However, i want to learn to code plattform independent applications in c++,
so i started learning with wxdevc++ (so im still a bloody beginner).
And for me, is is very important to get familiar with one IDE, and that its
easy to port applications right form the start.
Since im using linux quite a lot, it would be nice if it's plattform independent too, so
code::blocks is the first choice.
So finally, so exact intentio of my question was not to say, the wxsmith or wxformbuilder are cra...,
BUT:
i wanted to know and hear from somebody that this tools can be (with some practice of course)
very effectiv, and its just a matter of practice and learning, getting fast and effective with these tools.
So if you say now, there are very useful, then i at once start learning with these tools and get comfortable with them,
without fearing the learning with these tools is in vain, and in some month after learning and coding with wxformbulder
or wxsmith nobody could tell my, that it would be impossible to code as comfortable with codeblocks and wxsmit etec. then
with wxdevc++.
Im a bit used to lazarus, so at the beginning it IS a difference using wxsmith or wxformbulder,because its just..... different :).
Im sure ill get used to it, and if you can build applications easily with them, i can learn it too.
So thx for the answer! Im very satisfied with that, cuz i like codeblocks very much, so now i can
keep on learning without any doubts using linux, and knowing i cant do too wrong :)
So as you already figured out. At the moment im playing around with bulding some guis, building and compiling them on linux and windows,
just to see which ide suits me best. And id just want to get wxsmih and wxformbuilder working for me
My exact problems so far were using the right sizers and choose spacers on the right spot , to get the objects in the right positions.
Grom:
I am writing GUI since 1993 :shock:. The first my GUI was written in Pascal with Turbo Vision :lol: for MS DOS, when I was a school boy.
Today all wx designers have a lot of problems. The most promising future have only two: wxFormBuilder and wxSmith.
wxDevCpp will never win, because it was designed with Delphy. To have a good developer you have to use that developer for that developer development. On the other hand you attempt to make a model of the nature behavior of components, raise than using them with their "characters" and "troubles". The best and most successful example is Borland's IDE. That is why a large piece of my GUI was created with wxDevCpp, only because 2 years ago was nothing better.
If BYO will make something similar to wxFromBuilder + his features or wxFormBuilder will add BYO's futures then that engine won. Both engines are very close to the nice end. Meanwhile, BYO added new cool feature - we can add custom controls with full functionality and made a big step ahead. The only one reason why I don't use wxSmith - because it doesn't have wxGrid, which is critically important in my projects. If I will find time I will add wxGrid control to the wxSmith to start using it.
So my suggestion - to use all developers together in the same project :wink:, in the places where they more efficient.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version