[Adium-devl] Module Refactorization

[disposable at infinitenexus.com]

I'm all for it, but I disagree with the line
"Remember that refactoring is most likely to be successful when you  
are adding a feature or fixing a bug. This should be the main focus  
of the refactoring!"

It implies the need to 'add something' to justify the refactoring -  
refactoring doesn't need to be justified, it improves code clarity  
and if nothing breaks, meets its requirements.

- brian 'bgannin' ganninger


On Jan 29, 2007, at 9:45 AM, Colin Barrett wrote:

> On Jan 28, 2007, at 7:13 PM, Andreas Monitzer wrote:
>
>> Hi,
>>
>> I talked to some devs, why my original mail about the module
>> refactorization project went unanswered, and the reply was that
>> reading though the whole log was too cumbersome.
>>
>> So, I drew the consequences and wrote up the wiki page the log was
>> talking about:
>> http://trac.adiumx.com/wiki/ModuleRefactorization
>>
>> I welcome any feedback! Feel free to make any (productive) changes to
>> it!
>>
>> andy
>
> It looks really good, Andy.
>
> I've added a couple things to the process. I think we can really get
> the ball rolling here. Before we go a whole lot further though I would
> welcome Evan's comments on the whole idea.
>
> Everyone else, feel free to weigh in, even if you have nothing to say
> other than +1. Consensus is very important for a (rather large)
> undertaking like this. I don't mean to scare with words like "large
> undertaking," though. I suspect that in many portions we will have
> something like 80% code reuse. In some of the more ugly spots that may
> dip down, but on the whole, we are mostly going to be doing an audit
> and writing unit tests.
>
> THIS IS NOT A REWRITE!!! (at least, it *shouldn't be*).
>
> -Colin
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com
>