I would like to investigate whether the extended WiX BA
(http://wixextba.codeplex.com/) should be integrated in to the WiX source or
left standalone. If it is integrated should it be as a second BA or the
features merged in to the standard BA.
These are the enhancements and some suggestions on how to integrate them:
1. Resized HyperlinkLicense and RtfLicense so they are the same size as
the default WiX UI - this is useful if you need to show an MSI internal UI.
>Could be made extra theme types within the standard BA or just replace the
>current ones.
2. Add welcome message to HyperlinkLicense install page.
>Could become the standard.
3. Add support for Radio buttons on the option and install pages.
>Can be integrated without affecting the current code.
4. Add support for checkboxes on the install page (they are already
supported on the options page).
>Can be integrated without affecting the current code.
5. Add support for second directory folder on the option page.
>Can be integrated without affecting the current code. (This feature should
>probably support 'n' directories but is that really useful.)
6. Add Hyperlink2Theme theme (and example) that supports a larger logo on
the install page (see images on Codeplex project page).
>Could be made extra theme types within the standard BA.
7. Added install version number to HyperlinkLicense install page.
>This could be put in the standard BA or made optional.
8. Reformat the RtfLicense to have flat licence textbox.
>Can be integrated without affecting the current code as this is just cosmetic;
>I think it looks much better than the standard theme.
9. Add preprocessor instruction to create an auto increment version (like
the C# AssemblyInfo format 1.0.*)
>This should probably be part of the standard preprocessor extensions.
10. Support for Bundle self-updates
>Can be integrated without affecting the current code although it is based on
>having a website determine whether an update is available. This may not be
>generic enough; I think it is better for this logic to be on a web server
>rather than hard coding it in the installer.
11. Support for custom actions in the extension UI.
>Can be integrated without affecting the current code. The idea behind this is
>that creating the install variables can be quite complex using Variable and
>RegistrySearch, these CAs allow you to write C++ code to setup the installer
>variables.
12. Support for disabling controls based on conditions.
>Can be integrated without affecting the current code.
It would be quite a lot of work to split these out as separate forks so for my
benefit it would be better to apply them as several features per fork.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com<mailto:n...@x2systems.com>
------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
