Originally Posted by
lewis
well, I suppose its stupid to only allow 2mins to create a poll...
Usually people create polls when opening the thread and not after a meditation in a bathroom...
What if you really have to go to the bathroom!?
Do it before opening a thread with a poll...
About the issue with Designer. I think Designer is there for you to use it. It generates a very good code, you won't be able to write a better one yourself. And using it doesn't mean you don't know how to code a widget manually, but saves a lot of time.
Maybe my opinion will sound a bit too strong, but I think that lame people are not the ones using Designer (because "real programmers code everything themselves"), but the ones not using it. Otherwise we'd be all stuck with binary code, perforated cards or in the best case assembly.
To be honest I am thinking of writing a set of macros which would relieve me of writing the same standard things all the time (what a waste of time it is), like:
#include <QWidget>
#include <QApplication>
int main(int argc, char **argv){
wgt.show();
return app.exec();
}
#include <QWidget>
#include <QApplication>
int main(int argc, char **argv){
QApplication app(argc, argv);
QWidget wgt;
wgt.show();
return app.exec();
}
To copy to clipboard, switch view to plain text mode
It'd be better to write for example:
#include <QWidget>
Q_START
wgt.show();
Q_END
#include <QWidget>
Q_START
QWidget wgt;
wgt.show();
Q_END
To copy to clipboard, switch view to plain text mode
There are many things like the one above... Qt already has some nice things like forever() or foreach() and of course Tulip (although real h4x0rs would say they always implement their own vectors or lists... because using COTS solutions is lame ).
Bookmarks