On 26-feb-04, at 18:48, dries wrote:
That's why i (still) allways use the 'KDE-mini' type of application, this is because i wan't some gui stuff done in a simple manner.
Same here. I don't really like applications to create functionality code for me (Wizards, brr). They come out handy, sometimes, but especially if you're learning this stuff this is not the way to go.
Things i still don't understand well :
1) What is the 'real approved' method to attach my QT-designer gui to my program (now i just inherit it to the gui to the application like this :
DevEnv::DevEnv(QWidget *parent, const char *name) : MainForm(parent, name)
Yeah, I've started learning KDevelop/Qt myself (busy working on a project), and found the way this is done in KDevelop kind of weird. All of the tutorials indeed tell you to extends the GUI class, and put your code in that class. However, when you come to think of it, this creates some clean code where functionality and layout are neatly separated from each other. No need to code the GUI side (which can be boring), just create a .ui in Qt Designer and let "Automake & friends" create the .cpp file that belongs to it. Need to make a change? Open the .ui, edit it, save, and your app has a new GUI (after recompile). If you think of it, this really makes sense.
2) How can i change the complete gui in a window by clicking a button of the current gui in that window ? (functionality i want for some reason (don't ask me why)).
I remember from my Java experience that these kinds of things are done by LayoutManagers, and for your case specifically the CardLayout. You add layouts as if they were cards on a staple, and then switch between them by calling some method. Here's an url: http://docs.jcu.edu.au/qt/customlayout.html This does not seem to be the "qt-way" to do layouts, though. Hope it helps. Regards, -- tinus.