> I'm not sure who you've been talking to, but that's not the position or
> conception of the Tools group. Phil Shoemaker was just talking about
> making the tools as cheap as possible, preferably free.
This was prior to the 'Tools' group being public. Things have
changed, since the inception/adoption of POSE and prc-tools, and that's a
good thing, but at the same time, we still both have our respective
communities to support.
> But we have no intention of releasing all of the source code (in some
> cases, we can't, because we license it from other companies).
That's understandable, and I don't think anyone is asking you (or
Palm) to violate any existing licensing agreements with partners or OEMs.
> Thanks for the compliment. And while I don't want to denigrate the
> support of "the community" over the years, the amount of work
> contributed from that sector really doesn't amount to much.
I've had to deal with this too, most recently today in a long
flaming email about the frequency of releases of Plucker. Someone else
replied with a great analogy, something about ".. people all leaning on
their shovels and lamenting how the hole isn't being dug fast enough.."
Lots of complaints, not many contributions, myself (on POSE)
included, so I don't exclude myself from the guilty parties.
> I get more questions about "Why doesn't Poser 3.3 work with FLTK
> 1.1b<whatever>" than I do about anything else.
Many of the complaints I see are related to people trying to stitch
together various versions of fltk with the latest POSE. Perhaps more strict
requirements of the dependancies would cut that down, and if you vary from
the list of required versions, you're on your own to patch/build/report
bugs.
This stuff doesn't write itself, most people don't realize that.
> I keep waiting for just ONE developer to transition past that to
> actually making the appropriate changes and submitting them (along with
> a configure script that lets Poser use both FLTK 1.0 and 1.1).
Let me try to make a nudge on the list.
/d
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
