DanielSefton wrote:I posted the diff for porting it to 1.6, but it wasn't much use.

Generally there are many people who search for ready solutions in forums and wiki.
When they don't find it, most people do it themself. They don't ask for a solutions, unless they have problems.
Even if less people use you published code - it's good for the public to have it.
Also most people read solutions without saying thanks. So how you want to know that only less people use it?
Even simple code snippets can help somebody to learn how to do something.
DanielSefton wrote:I'll post it if MyRddinson wants me to, or if anyone is desperate.
Do you think that people ask you for a solution when the people doesn't know that you have a solution?
DanielSefton wrote:Best if it comes from the horses mouth
Generally yes, but also the horse could be happy about improvements.
And other people can use it more early. Also maybe the horse doesn't talk about this.
update (addition)
A big problem for a project is, when the horse runs away.
The same problem happens with the Mogre wrapper. (using Ogre by .NET applications)
There was no documentation. Some people wanted to update and maintain the wrapper, but they didn't understand some internals and gave up after a while.
One year later the horse came back to do the job (update from Ogre 1.4 to 1.6).
Also he gave explanations to some important points.
An other point shows the power of the community.
An important SDK feature didn't exists. The horse didn't create it.
One user created a helper tool to add this feature. But he didn't published it and nobody did know about.
All 6 months I remind the Mogre people to this imporant and needed feature.
Not until then he posted his solution.
Now it's integrated to the SDK building process and everybody can use this enrichment. (Also some of them said thanks for integrating it.)
Just some thoughts about the horse ...
