Hi Ryan,
Hi Kevin,
I totally agree with you that such a thing would be great to have, but
I simply do not have the time to do it or contribute to it in any
major
way.
Actually I was referring to me doing the non-mac ports - but I
understand :).
Then I'm a bit confused, because I thought that wxQtMovie is the Mac port? (And thus I thought the issue was making it work on Windows.) IIUC, all that would be needed to make a cross-platform framework would be to write a wrapper around wxQtMovie on Mac, and wxWMP (or whatever) on Windows. Then were you asking about collaborating on API design/wrapper functions?
In terms of making the Mac wxQtMovie port functions work correctly, I most certainly intend to follow through with that, and of course the code is wxWindows License so obviously I have no issues with sharing the code or someone improving upon it.
BTW your posts are amazingly eloquent! If you wrote a book on how to
use English better I'd most certainly buy it :).
Wow, no one's said anything like that to me before. Thanks! =)
Really, the main reason I write the way I do is that I feel miscommunication is one of the worst problems that plague any project, in fact I'd argue it's one of the core issues underscoring most every problem we face. Communication is such a natural and common thing that I feel people often don't see how important it really is and never really question whether or not they could actually communicate better. And I found that the most common factors (in my experience) that cause miscommunication are:
Note that by 'you' I don't actually mean 'you', (often it should mean 'I' - I'm just too lazy to make all this work in the third person.
1) shooting from the hip - responding immediately before 'digesting' the message, so one may end up responding to a point other than what the original poster made
2) taking it personally - many times people read between the lines to find things that aren't there, so it's good to question whether you're actually being insulted/attacked, or you just think you're being insulted/attacked. I've seen many an upset person over what was originally an honest mistake with no malice involved whatsoever.
3) thinking that others know what you mean - this is a common and honest mistake, but typically this leaves lots of ambiguity in the message and can cause lots of confusion as people interpret it in different ways
4) taking their eyes off the ball - people become so engrossed in discussion/debate that they forget what it is they were debating about and get hopelessly off-track
I've done all these things many times myself, and I ended up feeling I did more to hurt my specific goal than to help it, so when I respond to messages, I try to ask myself if I'm doing any of these things, and if so, I back off and try to think of a better and more objective way to say things. (And you'd be surprised how easy these things are to catch sometimes if you are checking for them.) It takes time, but sometimes spending an extra 20-30 mins on a message could prevent a flamewar (or at least stop it from spreading). There's only so much one can do, of course, but I hope that I'm able to express myself properly because I figure anything I can do to save others some time is time they can spend doing something more productive than arguing over something.
OK, my unsolicited rant's over, but that's really all there is to know about how I write, no book necessary - if I ever did write a book, I'd definitely write a book about programming. Or Japanese animation.
Thanks,
Kevin
···
On Sep 7, 2004, at 7:05 PM, Ryan Norton wrote: