If you haven't done so already, read up on Design Patterns before designing the framework. re-usability is not a bad thing, if done right in the beginning.

>Hi everybody
>
>(Hi Dr. Nick)
>
>So I'm working on this app, actually, a new generation of about a half dozen apps.
>
>The current version of these half dozen apps share framework libraries, and I use a handful of 3rd party utilities.
>
>After all the years of writing and maintaining these apps, I'm going to replace them.
>
>And I'm fairly convinced that the old way I did things, maximum re-usability, very strong reliance on data driven functionality, is the wrong way to do things.
>
>I think that I'm not going to re-use any code between projects, and cut the 3rd party portions of the app mostly out of the picture, with the exception of Stonefield Data Toolkit, natch.
>
>But that's what I'm thinking. Reverting to the old days of straight ahead code with very little frills and minimalist class hierarchies.
>
>I think that in the end this will be easier to maintain over the next few years, and eliminate alot of the headaches that come with re-using code.
>
>A major change of style for me, but I think my old habits and ideas about code are ripe for replacement at this juncture.
>
>Thoughts?