Re: VC++ 6.0 To .NET

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

"Giovanni Dicanio" <giovanni.dicanio@xxxxxxxxxx> wrote in
news:OxMWkTs#HHA.3548@xxxxxxxxxxxxxxxxxxxx:

I've tried wxDev-C++ and it is a fragile *toy*: the opposite of the
concept of robust quality tool. The GUI designer is broken. The IDE is
something of the pre-VC6 era: maybe Notepad would be even better.

I'm not a big fan of IDE's, except for the debugger. I want my own
editor, not the one imposed on me by the compiler vendor. I do very
little editing of code in VS.

Form builders are useful. I really like wxFormBuilder for designing my
layout. It works well with wx's sizer-based elements.

The MFC objects, AFAICT, are all fixed-size items that are locked to a
position in a dialog. There's some nod to sizability based on fonts.

However, I don't like wxWidgets. For example, the documentation is
really *poor*.

I needed to have a custom grid with radio buttons inside a cell. Then
I went to wxGrid documentation, and I just read a dummy sample here:

http://www.wxwidgets.org/manuals/2.6/wx_gridoverview.html#gridoverview

the really interesting examples are just ... "Yet to be written..."?!??

What kind of professional style is that??

I don't trust an undocumented library, with no serious IDE support.

BTW: Have you any idea about how to put three radio buttons into a
cell of a wxGrid? :)

I've learned never to trust documentation. When documentation is obtuse
(and MS' is far from perfect: just look at Samba's development history,
working from bad specs) I often use the source as my documentation when
I'm not sure how something works. I'm just glad I have MFC sources when I
have to work with it. I get very frustrated working with libraries that
don't provide me with source. I'm at the mercy of the vendor docs, which
are both poor and incomplete.
.

Quantcast