View Single Post
Old May 23rd, 2004, 07:24 AM
planoie's Avatar
planoie planoie is offline
Friend of Wrox
Points: 16,481, Level: 55
Points: 16,481, Level: 55 Points: 16,481, Level: 55 Points: 16,481, Level: 55
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
Join Date: Aug 2003
Location: Clifton Park, New York, USA.
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts

Welcome to the mean and dirty world of application customization!

Unfortunately, depending on what kinds of things you need to customize, you have to write a lot of conditions. I work with applications that are heavily customized and I find that probably 60% of the code in the application is simply for the customization and only 40% is actually *doing* something. That's the nature of the beast.

As Hal mentioned, if this is a distributed application you might want to avoid the use of simple-to-modify setting. An option could be to have some kind of flag/setting that is embedded into the application code so you can do a customized build of the app in a way that a user couldn't change it.

One piece of advice I will give: Work with a single application that is built to handle customization. It might be a little harder at first, but when you start having to add features or fix bugs, it's MUCH easier to manage in a single (though more complex) application.

Work smarter, not harder