Dodger wrote:
[...]
That's f$*%ked up!
[...]
What, are you writing a book on WxPerl and don't want any free
competition or something?
[...]
Looking up the C++ apis and going with a general knowledge
that "It's pretty much the same, even if I don't quite understand C++
anyway" is crap.
I encourage everyone else to ignore this posts on this subject that
claim it's not worth the effort
... no need to come down on the guy for stating his opinion mate ;-)
There's always a cost-benefit analysis to be considered in these cases.
Clearly it would be nice to have Perl specific docs, but you weigh that
against the cost of someone having to invest the time & energy to do
that and the fact that people *can* struggle through with the C++ docs now.
I agree with you that it probably _is_ worth the effort. Johan
disagrees. He's entitled to. And I don't deny your right to disagree
with him either, but no reason to make him feel his views are invalid :-)
and now, more than ever, I want to
put some together, at least regarding stuff I've done.
That's cool. Hopefully if a bunch of people can contribute a little it
won't be the horrible slog some people fear it would be.
Roode, Eric wrote:
As I write documentation, to whom can I send it so
that it'll get posted on the project page?
I think this has still gone unanswered...
Would a wiki be the easiest way to coordinate people on this? Or would
that be too unstructured?
By the way, have y'all seen the doxygen-based wxWidgets docs, new for 2.9?
http://docs.wxwidgets.org/trunk/classwx_html_window.html
Pretty nice ey? There seems to be a bit on their wiki about the process
of using doxygen. Maybe it could be an option for wxPerl. Of course,
it's another technology to have to go and familiarise with before
actually /doing/ anything :-p
-- Ryan
