>;-- On Fri, 03 Aug 2007 12:48:57 -0000 skirkpatrick_nc wrote --
> I've written a couple of small projects using DB alone. The only
>; issue I have with DB is the debugging aspect. Yes, it uses gdb
> just fine but it's not integrated with the editor, it's essentially
> accessible through a console. While you can do all your debugging
> through it, it's much easier to set and see breakpoints in the
> editor and there's no variable watch area. ; The debugging interface
> is excellent in Eclipse and you can get integration with CVS or
> Subversion along with other editors/tools. If DB had better
> debugging integration, I would be hard pressed to show a better
> toolset.
>
I believe even Julian would agree with you on that point!;)
> My original question had more to deal with how do people who use DB
> for design and another tool for development integrate the two? Use
> DB to generate XRC files only? ; Generate the base C++ files and not
> the makefile (Eclipse won't automatically update an outside
> makefile)? ;Do you use DB to create the event handlers and the
> other tool to flesh them out?
When I start a new project, I will typically start in DB (usually, with a
wxFrame). I add all the controls I think I'll need to accomplish the ends of the
application and add the extra variables and event handlers I will need. Now,
with the latest DB, I also add helper functions, something I used to do outside
of DB. Then, as is most often needed, I add whatever extra dialogs/frames I will
need to handle user input, usually precipitated by an event such as a button
press or a value change in data entry controls.
This amounts to about 90% of the GUI and a good 50-70% of the code. I do a build
in DB, just to make sure I've got everything working ok wxWidgets wise.
Then, depending on the size and amount of coding, I use either Visual Studio or
EditPad Pro for hand coding. If the hand coding requires a lot of formatting
and/or a lot of search and/or replace, I will use EditPad Pro as it's much
better for editing than either Visual Studio or DB (but then, I don't expect my
IDE's to be all around full blown text editors, just a utilitarian ones).
I then do another build with DB. If all goes well (about half the time it does,
the other half is my fat-fingering in the hand coding), I'm done!
If, however, there are problems and they aren't readily obvious, I open the
project in Visual Studio (using the project files DB has generated and I've been
using for DB builds) and do my debugging there.
Pretty much, I really only use Visual Studio for debugging. I use DB for most of
the heavy duty work.
Once built on the Windows platform, I fire up Ubuntu and generate a makefile in
DB there for GCC. 98% of the time, it just builds and I fly with it. The other
2% is mostly little compiler gripes that I fix there if they're not too
extensive. Else, I make note of the complaints, re-open the project source files
in EditPad Pro, and globally search for the instances where the GCC compiler
didn't like a certain construct or two (or three...). The mods are fast and easy
in EditPad Pro, it has excellent regular expression search and replace
(alternatively, if you prefer a non-commercial editor, Vim is pretty good,
too!;).
And that is a thumb-nail sketch of a typical project. Most all of the time is
spent in DB. The code it generates is clean and (usually) builds with no problem
on all platforms. The culprit is my own coding that frequently rubs one compiler
or the other the wrong way!:-<
Most all of the source files and all of the project/make files are generated by
DB. Julian really has the build process well handled in DB, about as flexible as
one can get with an automated tool. I've had some minor difficulties with
.vcproj files (and some with solution files not being readable by Microsoft's
version detector), but Julian is quite amenable to addressing these problems if
the circumstances of the problem and what needs to be changed are well laid out.
HTH:
thx,
Dave S.
MSGTAG has notified the sender that this message has been successful
ly sent.
.
