Re: Using DB and Eclipse together

--- In anthemion-devtools%40yahoogroups.com">anthemion-devtoolsyahoogroups.com, "Boris Becker"
<beckerde...> wrote:
&gt;
> >From: "skirkpatrick_nc" <skirkpatrick...>
> >
>; >I have to say that of all the wxWidgets designers I tried out, DB is
> >the nicest and supports more widgets than the others. It's only
>; >drawback is that gdb support is not integrated with the editor as it
> >is in Code::Blocks. I see a lot of references, including Julian's, of
> >using DB for the designer and then using VC++ for project management,
> >writing all the rest of the code, and debugging. I am in the process
> >of setting up a development system to be used by my company under both
>; >Linux and Windows and it seems that Eclipse would be the best
>; >replacement for VC++. Does anybody have any experience with making DB
> >and Eclipse work well together?
> >
>;
> They work well together. DB for design, Eclipse for building the
> application.
> You have to use cygwin under windows and the native gcc compiler under
> Linux.
&gt; You will be able to use the debugger in both platforms (gdb).
&gt; But I think you will have better results with Code::Blocks, wich
works the
> same under both platforms. In this case, I would recommend DB for
design and
> wxWidgets build and C::B for building and debugging your
applications. You
> have the full source code of C::B to see how they do certain things
using
> wxWidgets.
>
> regards
>
> Domingo Becker
&gt;
> __________________________________________________________
> Latinos en EE.UU: noticias y artículos de interés para ti
> http://latino.msn.com/noticias/latinoseneeuu
>

>&gt;They work well together. DB for design, Eclipse for building the
application.

???
I don't understand the advantage here. DB builds for any compiler and
any platform that wxWidgets is on. So, why have a separate tool to do
builds?

And then, why introduce yet another tool (which does essentially the
same job as DB, only not as well and not as stably), Code::Blocks?
Tinkering around with the Code::Blocks source may be interesting for a
hobbyist, but for production builds (which is what the OP is talking
about) it leaves a lot to be desired, not the least of which is good
full time support.

As for using gdb, you can use it on any platform with DB.

As for building with GCC on a Windows platform, Cygwin is not a
requirement, MinGW does just fine (it uses GCC). But, still, DB
addresses Cygwin, too.

DB is the only all around GUI design/build tool for wxWidgets extant.
You really don't need anything else to design, build, and run
applications on any platform. And it operates the same on all of them.
I've tried all the other wxWidgets design/build tools (some only
design and some only build), and more than one time. There is not one
that has the scope, stability, and depth and breadth of platform
integration that DB has. So, if you're using Code::Blocks with DB, you
just don't understand how to use DB.

jmtcw:

thx,
Dave S.

Messages in this topic (0) Reply (via web post) | Start a new topic

.

--- In anthemion-devtools%40yahoogroups.com">anthemion-devtoolsyahoogroups.com, "ddotedotsdot&quot;
<dsilvia...> wrote:
&gt;
> --- In anthemion-devtools%40yahoogroups.com">anthemion-devtoolsyahoogroups.com, "Boris Becker&quot;
> <beckerde> wrote:
&gt; >
>; > >From: "skirkpatrick_nc" <skirkpatrick>
&gt; > >
>; > >I have to say that of all the wxWidgets designers I tried out, DB is
> > >the nicest and supports more widgets than the others. It's only
>; > >drawback is that gdb support is not integrated with the editor as it
> > >is in Code::Blocks. I see a lot of references, including
Julian's, of
> > >using DB for the designer and then using VC++ for project management,
> > >writing all the rest of the code, and debugging. I am in the process
> > >of setting up a development system to be used by my company under
both
> > >Linux and Windows and it seems that Eclipse would be the best
>; > >replacement for VC++. Does anybody have any experience with
making DB
> > >and Eclipse work well together?
> > >
>; >
> > They work well together. DB for design, Eclipse for building the
> > application.
> > You have to use cygwin under windows and the native gcc compiler
under
> > Linux.
&gt; > You will be able to use the debugger in both platforms (gdb).
&gt; > But I think you will have better results with Code::Blocks, wich
>; works the
> > same under both platforms. In this case, I would recommend DB for
> design and
> > wxWidgets build and C::B for building and debugging your
>; applications. You
> > have the full source code of C::B to see how they do certain things
&gt; using
> > wxWidgets.
> >
> > regards
> >
> > Domingo Becker
&gt; >
> > __________________________________________________________
> > Latinos en EE.UU: noticias y artículos de interés para ti
> > http://latino.msn.com/noticias/latinoseneeuu
> >
>;
> >>They work well together. DB for design, Eclipse for building the
> application.
>
> ???
> I don't understand the advantage here. DB builds for any compiler and
> any platform that wxWidgets is on. So, why have a separate tool to do
> builds?
>
> And then, why introduce yet another tool (which does essentially the
> same job as DB, only not as well and not as stably), Code::Blocks?
> Tinkering around with the Code::Blocks source may be interesting for a
> hobbyist, but for production builds (which is what the OP is talking
> about) it leaves a lot to be desired, not the least of which is good
>; full time support.
>
> As for using gdb, you can use it on any platform with DB.
>
> As for building with GCC on a Windows platform, Cygwin is not a
> requirement, MinGW does just fine (it uses GCC). But, still, DB
> addresses Cygwin, too.
>;
> DB is the only all around GUI design/build tool for wxWidgets extant.
> You really don't need anything else to design, build, and run
> applications on any platform. And it operates the same on all of them.
&gt; I've tried all the other wxWidgets design/build tools (some only
>; design and some only build), and more than one time. There is not one
> that has the scope, stability, and depth and breadth of platform
> integration that DB has. So, if you're using Code::Blocks with DB, you
> just don't understand how to use DB.
>
> jmtcw:
&gt;
> thx,
>; Dave S.
>

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.

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?

Messages in this topic (0) Reply (via web post) | Start a new topic

.

I prefer to use C++ coded dialogs.
Almost everything will be done by DB, it generates clean and readable code.
The interface and event handlers with DB.
Sometimes, I need a dialog from one project in another one. Then I use the c++ source generated by DB in the other project, or I separate the dialog in a library of useful common dialogs.
The only situation when I use other tool is for debugging and library creation.
In Eclipse, you would add the generated c++ files manually to the project it manages. This is the only task I would let Eclipse do.
By the way, I don't use Eclipse anymore.

regards
Domingo Becker

Messages in this topic (0) Reply (via web post) | Start a new topic

.