>>>
>>>Marc
>>
>>I hate to complicate this discussion any further, but considering the framevork to be an important and big part of an app, I'd have to say that at some point, framework will cease to be general and go into things speciffic for each app, without meaning we have to begin hard coding. IOW, parts of framework probably should stay at one place and be general, but it's finding that fine line where framework gets too oriented towards a speciffic app that's tricky. I mean, some changes on framework can work beautifully at a low level, affecting all apps involved, others might cause a disasters we all fear.
>
>What you suggest is further refining between what is universal and what is specific in a framework. That sounds like good advice. I'm not rushing into it though. As I said before, my stuff needs to be cleaned up first.
>
>Marc
Yes, something like dividing your framework into general and "not so general". Should you choose to adopt this kind of solution, it might be smart to do it on future apps, as opposed to modifying your existing apps' classes, I mean what's the rush, right?
Danijel