From: Chris M. <ch...@cl...> - 2003-10-31 21:31:32
|
Sean Dockery wrote: >>It's easier to criticize than get involved, so I'd just like >>to push for a little bit more understanding. You have a valid >>complaint, but understand the behind-the-scenes and know that >>if you want something changed, you have the opportunity to >>do it. >> >> > >I was just pointing out the humour in the irony. > Ah, humor. There's nothing I love better than getting defensive on someone who already agrees with me. D'oh! >It wasn't my intention to >complain. If you look at the want-devel and want-interest mailing lists, >you will see that I am trying to contribute to the project--though I've only >started to used want over the past couple weeks. I'm not offended whether >or not this is how you intended your statement; > > So we won't be starting up a cat-fight here, then? :-) >I just want to make sure >that you know that I'm not a complainer--I'm a fixer. A brutally honest >fixer. :-) > That's cool. Just wanted to put in my $0.02 for Getting Involved. >But lack of a release plan means that there are no goals to which >the project aspires over time. The community itself is at fault for not >contributing. > True, but this walks the line of, "If nobody's contributing, maybe there's no real need." I certainly can't say which it is. For me and DUnit it's that I have no need of anything more right now. That said, I've been there before and gone on to have benefitted from other contributions when I wasn't aware of the need (like the addition to F8-execute only the current test -- very nice). >Being fairly new to the want >community, I don't want to gut the source code without the support of at >least two or more of the committers. Otherwise, I fear my contributions >won't be integrated and I might as well write my own ant-clone for personal >use because future releases of want will diverge from my version anyway. > > Early in the DUnit project I made changes to the GUIRunner by subclassing the whole thing and running that personal version. That is risky, as you say, to keep up with future versions, but it was an option that got me going faster, and then I had something substantial to show Juanco, and that's how I helped get into the fold. FWIW... >1) If dunit can be compiled under Delphi for .NET, will want become >irrelevant for the fact that you could run dunit tasks natively from nant? > > I think it could -- but this is really going to be decided by the community of coders. If there's not enough distinction, and not enough room for 2 of the same thing, then nant may supercede want. I myself don't know if it's that important to have an answer (or a guess) beforehand. I just want to get stuff done, and I'll use whatever tool best works for me at the time. (And for me right now, for builds, is Ruby :-) >2) Will nunit be capable of calling Delphi for .NET code directly? > As I understand it, yes. Delphi for .NET will compile into .NET assemblies. Once something is a .NET assembly, the original source code is irrelevant -- any assembly can work with any other assembly. >If so, >does this make dunit irrelevant for future versions of Delphi? > > Well, Delphi for Win32 will still need DUnit, right? -- Chris http://clabs.org/blogki |