>All I'm saying is, Zoner's the local DCF hacker, and if somebody else
>codes a function, he'd have to be the one to integrate it with our
>install, and if somebody else had coded it, chances are he would
>refuse to do so in favor of coding it himself, which he might or might
>not actually get around to doing.

I'm not an asshole - some of the features in this copy of DCF didn't originate from me. I have incorporated hacks from other people - when they're well written and make sense. But it does mean that I have to maintain them, and possibly port them forward when we upgrade. So I don't just toss in any old thing.

>In this case, I can be fairly confident in saying that he won't
>implement anything new on these boards as they now stand, since DCF
>6.0 is out of date. He'd have to upgrade to whatever's current, then
>start hacking that.

Which is one reason I was trying to get my new dev box running today, so I could patch DCF 6.2.1 to be compatible with the hacks we're using and upgrade the forums. Unfortunately, as Gryph knows, it appears the CPU, and possibly the MB, of my new box is toast. And, in trying to trouble shoot it with Jer, it looks like we fried *his* CPU and/or MB.

Tomorrow I'll go to a local repair shop and see if we can sort this mess out.

But, yes, since - one way or another - we'll be upgrading from 6.1 to 6.2.1 RSN, and 6.2.1 has a lot of changes, I'm not willing to add new hacks to 6.1 at this point since I'd only have to recode them into 6.2.1.

>I'd like to see the "reply in new thread" function too, but I've
>learned long since the negative value of hounding Zoner about things.
>It gets them not, and possibly never, done.

True - I have a negative reaction to nagging. If it annoys me it turns me off on the whole project.

But I have a laundry list of things to deal with in 6.2.1 just to port 6.1 hacks over. Then I can look at this - I don't think it will be too hard to do. And it is something I thought of myself a long time ago. I'd been waiting for 6.2 - which was delayed. And it shipped with too many open issues - so I waited for 6.2.1. Which was repeatedly delayed. The whole time going "Well, I know that if I start working on this in 6.1, David will release 6.2.1 the day I finish..."

-MegaZone, megazone@megazone.org
Personal Homepage http://www.megazone.org/
Eyrie Productions FanFic http://www.eyrie-productions.com/
See what I'm selling on eBay