> > 1- because it's a workaround, not a very clean design
>
> Until I see a radically better one, and a good reason *why* it should be
> introduced, it will work well.
Well I am glad to see you turning on to the one true practice of software
production: XP <g>
We all know that MVC is a pretty simple pattern and having the imports from
graphic stuff (even if lazy loaded) in the same classes that hold logic
information in memory screams "factor me!". Heck I don't need to read the
pattern doodoo thingy book to know that.
> > 3- If somebody else is doing it, you should let them.
>
<snip_on_disagreement>
hmmm... really people want to work on what they want to work. Preventing
people from cleaning your code if they want to is bad open source management
<trust_me_on_that/>
Honestly I am glad somebody is looking at it instead of holding it with a 10
foot pole. Everyone is saying "pheeeww" maybe we should factor this thing,
and I am glad.
> Convince me :-)
it's not you and me, there are tons of capable people on the list and you
have to let people work on what they want.
Listen Rickard, I have worked enough in your code to know that you are a
very capable coder, but that also sometimes... well... like everyone else,
really. So let's show some pudor and common sense and let other capable
coders take our code.
I did it with you, do it with others,
yeah, that's what love is all about..
kind regards
marc
