From: Richard B. <bo...@bo...> - 2002-03-29 13:38:21
|
Guillaume Laurent wrote: > Not so well, it seems. I'm really thrown off by the commandExecuted/slotCommandExecuted() > mechanism. All the various slotCommandExecuted methods look like maintenance > nightmares in the making. I'm all for keeping the commands seperated from the > GUI, but not like this. Ok, obligatory bristle coming up.. Hey hey, can we hear some solutions and not just random slagging? A lot of this stuff has been discussed thoroughly and openly and has existed as code for a while already. While I haven't got a problem with changing any code or design given good reason there's no mileage in just taking potshots because you can't get your head around it first time. _I_ still can't quite get my head around it and I've been really trying for quite a while now - we'll get there in the end. I actually do think the mechanism we have is elegant and simple and there's no arguing that it works. If you've got an alternative that's more effective and simpler to implement then yes I'd like to hear it. I do feel though that at some point one has to get one's hands dirty and leave one's principles on the wall - and there's something to be said for having code, no matter how gnarly it might appear. God I feel like I now should go on and to say "be a part of the solution, not the problem". Ra ra ra. I'm a fucking cheerleader. R |