I'm not sure how many of the committers relish the idea of reading through about 1,000 lines of completely uncommented code and trying to understand what it all means. And that on a wiki page, rather than in their favourite editor where they would have syntax colouring and could jump around at will, from definition to usage, etc., to help understand it. Add to that almost 40 updates to the wiki page in the last 10 days, and there's even less incentive to start looking at it, fully expecting a flurry of updates before they've got much beyond the first paragraph.
I would suggest that you finish your work on it first, then put the code somewhere that people can download and bring up in their editor, and have a wiki page that explains what you're trying to do and that points to the code download. That's much more likely to get people looking at it, at least in my opinion. -- Martin Cooper On Fri, 11 Mar 2005 08:29:19 -0800, Dakota Jack <[EMAIL PROTECTED]> wrote: > Thanks, Frank. I posted this code in response to Ted's suggestion > that this is the way to go to establish a dialogue with the committers > on code. > > > -- > "You can lead a horse to water but you cannot make it float on its back." > ~Dakota Jack~ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
