[AccessD] Re: [Private] Framework Discussion - Dependent Obje cts

Hi Drew

Yes, that makes sense to me, though I don't have any tools to program
dlls. I have some very general and well proven functions which I
simply keep collected in some modules which I copy-paste into a new
project as needed - not very fancy, I know, but it works.

/gustav

> I'm in the same situation as you. I find that building a 'framework' isn't
> worth the effort, because I have to develop very diverse GUI's.  It's not a
> matter of re-using features, it's a matter of building specific features to
> handle the task at hand.

> At my full time job, however, I have found that one of the best practices I
> can stick too, is to develop applications as 'stand-alone' objects, yet
> leave room for interaction.  So if I develop a library application for our
> Drafting department, and later I develop a modeling package for the
> engineers, if I need access to the drafting library, I can just 'reference'
> the drafting department's .dll's.  Makes life a lot easier.  To me, that's
> what I call a framework.  It's not a generic thing from a functionality
> standpoint, but more of a generic thing from a usability standpoint.

> Make sense?