Cool, going through the list:
1. More theme's are cool. More stuff to maintain but if they are useful,
it's usually worth it.
2. Cool.
3. Just like the checkboxes, cool.
4. Cool.
5. Not clear how this is used but okay. Makes me wonder if we should find
a way to just make it N and stop worrying about how many there are?
6. See #1. At some point, if we solve the problem described on a fork of
earlier thread with Jacob where it is easier to get a theme, maybe we can
just add more example theme's and minimize the overhead of adding new
themes. Still not sure how to solve the root issue. <smile/>
7. Is this just another control that's text is set to the
WixBundleVersion? If so, cool.
8. Okay. I don't think the default theme's look good enough in the grand
sense of the word but small improvements I suppose put us in the right
direction.
9. Let's cover this in another thread. I would like to understand better.
10. Let's cover this in another thread. I would like to understand better.
11. Okay, you can't call these "custom actions". People will often think
they should be changing machine state, which they definitely should not be
doing. I'm also curious what scenarios these are used for? Can we start a
separate thread.
12. That sounds quite useful. I could have used that recently myself.
So, I think the bulk of the items are pretty obvious. Let's discuss items
10, 11, 12 in more detail.
Neil, have you already signed the assignment agreement? If not, and you're
interested in pushing any of these forward, let's start that process soon.
On Mon, Feb 18, 2013 at 3:07 PM, Neil Sleightholm <[email protected]>wrote:
> 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
> [email protected]****
>
> ** **
>
>
> ------------------------------------------------------------------------------
> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wix-devs
>
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
