|
I
worked with a product set that had branding. It was implemented using a
DLL plug-in model. The graphics were linked into the DLL from a resource
file and the DLL also contained things like the product name, support contact
details, website URL etc etc. Producing a new brand involved copying the
relevant graphics into a resource, editing the string constants in the DLL
project file and compiling.
The
relevant brand was embedded in the registration code and at startup the program
loaded all the relevant DLLs (special filename extension) in turn looking for
the right one (brand name returned from branding DLL matched brandname returned
from registration decoding function). Using this method you can implement
almost any option you want with control over the security. This was
a commercial shrink-wrap application so we wanted a single CD-image that had all
brand DLLs on it with the relevant one selected at install time. If you
write different CD images for each reseller you could have different branding
DLL's with the same filename.
This
was a few years ago and we didn't use skinning so can't help you with that
one.
Wes
|
_______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi
