|
Are you guys
planning on using this feature as the main selling point of your software? If
not then I suggest not to get too carried away with it. What we're
currently doing is keeping the branding and personalization feature of our
software fairly light (corporate logo, sounds and splash-screen). We try to avoid using skins
mainly because we want to promote our
own brand. Furthermore, if you start to use skins, animation,
watermark images, etc then you might have to put in extra effort to make
your software usable in other
countries. Make sure you are aware of the localization
and accessibility issues when selecting
third party components. Also accessibility is a big issue if you guys are selling to the
US. Federal
organizations in the US will not
accept software that are not 508 compliant; more to consider :) As I said we keep our branding feature fairly light but we still cater for larger organizations that wants a more customized look and feel (this work we do inhouse).
regards Allan. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Jollie Sent: Monday, 28 June 2004 11:17 a.m. To: [EMAIL PROTECTED] Subject: [DUG] Re-branding and skinning Hi, we have a client / server app where we want to provide the option to resellers of our s/w and services, to re-brand to their look and feel. I’m starting with the basics – changes to splash screen and about box. Further down the track we might get into colour schemes and customized buttons. For the moment, I think we’ll keep control of it and do the re-branding ourselves in each instance.
Has anyone done this sort of thing? Any recommendations on flexible methods to do this? Security issues? (e.g. don’t want malicious skinning). Are skinning components such as DirectSkin or Delphi VCL Skin worth using?
Cheers, Dave |
_______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi
