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] |
It's more that I think the functionality should be there than that I want it. I don't use a cb client and probably wouldn't even if one had my feature. On the other hand, if someone created one that pops up a text box when I click in the talk box of the cb that's built into the home page, and disappears when I click talk, or there were a cb client that allowed me to browse perlmonks while chatting, I think I'd use it. I don't like having cb monopolizing my time.
| [reply] |
I don't use a cb client
Yes, you do. The web interface of PM includes a chat client. Or two.
a cb client that allowed me to browse perlmonks while chatting
That's what you get by default! When you browse around the monastery, every page has
a chatterbox -- at least, if you've enabled it in your Nodelet Settings.
I use this cb client a lot, myself.
| [reply] |
Consider upgrading to something with a multitasking windowing system.
| [reply] |