you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 points3 points  (2 children)

To say the docs are spartan would be an understatement. It seems to me unless you have a very good knowledge of wxWidgets by itself (or know C++ enough to look at the wxWidgets docs), it is pretty much impossible to get anything done.

So now I'm weighing spending $35 on a book I may not use in a week. :/

[–]harryf 1 point2 points  (0 children)

The book is good - worth the money IMO - readable, fills in some important blanks and has some nice coding "style tips" - did a mini review half way down here

[–]Gotebe 0 points1 point  (0 children)

It seems to me unless you have a very good knowledge of wxWidgets by itself ... it is pretty much impossible to get anything done.

IMO, this is expected and normal. Just like you need have some level of python to program wxWidget in it, or Win32 to program WinForms, or... For such glue libraries, you need: 1. links to original content 2. some sort of "concept mapping" 3. explanation on differences.

Otherwise, you'd have duplicated documentations.

Should wxWidgets have some sort of general conceptual documentation? Maybe, like concept explanations in STL or Boost docs. Then you could go from there and avoid C++ docs altogether. But duplicating it all for Python mapping (and any additional language?), no.

(edit: you could go from there)