in reply to Seeking input on perl/Tk code design

How much code do the "tabs of notebook" share? If they share a lot, perhaps you'd be better off if you put the common routines into one or more modules (so that you can even reuse it in other projects).

If, on the other hand, each tab has completely separate routines, they you'd be well justified in putting each tab into it's own (or more than one) module.

I should warn you, however, that you might find moving the subroutines into modules after the app is more or less working takes (in my experience) much more work than if you did it right (and modular) in the first place. Often, it takes more effort than it would to just rewrite the thing from scratch.

  • Comment on Re: Seeking input on perl/Tk code design

Replies are listed 'Best First'.
Re: Re: Seeking input on perl/Tk code design
by blueAdept (Beadle) on Mar 19, 2004 at 17:22 UTC
    The code/logic for each tab is going to be quite different. All the tabs will be operating off of the same database connection, but each tab will be centered around a different purpose.(different tables/areas of the database)

    I'll have some administrative tabs which I'll use to update(or add/remove) items in the database, and then more tabs which will be centered around either reporting(generated on tab load) or a near real-time(refreshed) view of the data. Its basically an admin GUI - make a configuration changes on one tab, then click a few tabs over to wait for a visible effect resulting from your changes. Other than the database connection I don't think the tabs will share much code/logic.