There are plenty of other CB Clients. Why not learn from their sources and take a crack at implementing this functionality in your own client?
--Solo
--
You said you wanted to be around when I made a mistake; well, this could be it, sweetheart.
| [reply] |
There are enough CB clients. Implementing my idea in a current client should be pretty quick and easy. If someone wants to use my idea in their client and tells me how to create a plug-in or at what points in the script to add the code, I'd consider creating this feature, but from past experience, I have reason to believe that the client's author wouldn't like my code and would rewrite it anyway.
| [reply] |
But certainly you could review the codebases, see which you like best, extend that one yourself, then submit a patch to the author or ask the author about a version fork.
The current author doesn't have to *like* your code, necessarily. Code that is written is almost always more useful than code that is unwritten. If people find a thing useful and functionally correct, it will be used despite any aesthetic ugliness.
Besides, even if the client author would want to rewrite your patch, why should you care? You just want the functionality, does it really matter whether your exact code provides the functionality, or provides the blueprint?
| [reply] |