[BR_forum] Organizing Libraries
Posted: Sun May 10, 2009 8:54 am
MORE libraries or FEWER LIBRARIES?
I'm trying to reorganize my libraries because they are a mess. I'd love to find out how most of you set up your libraries. Do you use one library for screen routines and one for printing? Or possibly one general purpose library and one which is specific to different clients? I tried to do all of the above and now I can't seem to keep consistent libraries that make sense. There is a lot of overlap. I'd love the benefit of your experience.
I thought that it would make sense to have MORE libraries that were specifically tailored to narrower topics, but now I'm not sure. As many of you know, I don't have a vertical application. Each of my clients have a custom system. They COULD share some library code though, which is the point of course! But some routines will always be specific to one client. Should I just put everything in one library, including the client-specific stuff in case it might someday be used by a second client after all? Mix screen IO and printing? What to do with data-related routines? Thoughts? How do YOU determine how to structure your libraries?
-- Susan
I'm trying to reorganize my libraries because they are a mess. I'd love to find out how most of you set up your libraries. Do you use one library for screen routines and one for printing? Or possibly one general purpose library and one which is specific to different clients? I tried to do all of the above and now I can't seem to keep consistent libraries that make sense. There is a lot of overlap. I'd love the benefit of your experience.
I thought that it would make sense to have MORE libraries that were specifically tailored to narrower topics, but now I'm not sure. As many of you know, I don't have a vertical application. Each of my clients have a custom system. They COULD share some library code though, which is the point of course! But some routines will always be specific to one client. Should I just put everything in one library, including the client-specific stuff in case it might someday be used by a second client after all? Mix screen IO and printing? What to do with data-related routines? Thoughts? How do YOU determine how to structure your libraries?
-- Susan