crossposted to sci.electronics.design,alt.os.linux.slackware
please manage followups intelligently, thanks.

Kinda OT for either group, but these two are my primary hangouts,
because as we all know this is where the smart people are, and I'm
hoping some of it might rub off. ;-) Anyway, the reason for
the post is that I've decided to take on learning C++ so I can
either get in on some Linux CAD development or write one of my
own, using what's probably going to be OpenCascade.
http://www.opencascade.org.

Well, I've finally studied enough C++ that I can read the source
files and tell what does which and who goes where, mostly. I
can run one of their demos - actually, a couple of them, which
are very, very rudimentary - I can put a box and a cylinder
on a window by command line, and I can start their GUI demo,
which is one empty form with default menus.

So, I'm sitting here, scratching my butt, thinking, since
I've looked at QT enough to figure out that it's just an
interface, I'll still have to learn C++, that I'd like to
load up their gui demo and incorporate their point-by-point
demo, and I'll be able to draw pictures and stuff. It'll
still take some reading to figure out how to generate QT
..ui and .pro files from existing programs, and I thought,
the ideal thing would be a source-level debugger, where I
could just step through the thing and watch what happens
when it does, for example,
---------------------
int main ( int argc, char* argv[] )
{
QApplication a( argc, argv );

QString resDir = ApplicationWindow::getResourceDir();

QTranslator strTrans( 0 );
strTrans.load( "string.qm", resDir );
a.installTranslator( &strTrans );

QTranslator iconTrans( 0 );
iconTrans.load( "icon.qm", resDir );
a.installTranslator( &iconTrans );

QObject::connect( &a, SIGNAL( lastWindowClosed() ), &a,
SLOT( quit() ) );

ApplicationWindow* mw = new ApplicationWindow();
mw->setCaption( QObject::tr( "TIT_SAMPLE" ) );
mw->setIcon( QPixmap( resDir + QString( "/" ) +
QObject::tr( "ICON_SAMPLE" ) ) );
mw->show();

return a.exec();
}
-------------
I can see what happens when it does these operations. What's
really tantalizing is that this is clearly done in Qt, and it
came from OpenCascade. So maybe if I just tell it to load it
up, I'll be able to see. Maybe I should check QT and see if it's
got a debugger, which I was going to do anyway, but wanted to
come and crow about
1) I'm gonna RTFM
B: I actually know what all this stuff means!

Cheers!
Rich

Hi,

Rich Grise schrieb:

> please manage followups intelligently, thanks.

I only read here, so...

> .ui and .pro files from existing programs, and I thought,
> the ideal thing would be a source-level debugger, where I
> could just step through the thing and watch what happens
> when it does, for example,

KDevelop has a builtin debugger.
If you work with large data structures such as lists, you might also
want to take a look at ddd.
I only program in C, but both should work with C++, too.

Juergen

On Monday 20 September 2004 06:16 am, Juergen Frieling did deign to grace us
with the following:

> Hi,
>
> Rich Grise schrieb:
>
>> please manage followups intelligently, thanks.
>
> I only read here, so...
>
>> .ui and .pro files from existing programs, and I thought,
>> the ideal thing would be a source-level debugger, where I
>> could just step through the thing and watch what happens
>> when it does, for example,
>
> KDevelop has a builtin debugger.
> If you work with large data structures such as lists, you might also
> want to take a look at ddd.
> I only program in C, but both should work with C++, too.
>
Yes, thanks. Someone else suggested KDevelop, and I'm currently
engaged in apropos RTFM, as time permits. ;-)

Thanks again!
Rich