Yes, there are plans to add designers to Votive. It's been on my list for a
while, but unfortunately my spare time has been rare the past few months. I
think the first designers will probably be very basic and rudimentary (I'm
thinking of registry and file/directory editors), but eventually more will
come. The challenging part will be to create the architecture for supporting
designer extensions. So, for example, somebody writes a Wix extension to
work with Media Center. They could also write an editor for that same
extension and have it plug into Votive automatically once the extension is
referenced from the wixproj. All sorts of cool ideas, but it'll probably be
a while before they're in at the rate I'm going, unfortunately.
Anyway, thanks for your suggestions. It's stuff that's already on my radar,
but it's good to know that other people want it, too.
Justin
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jared Ashman
Sent: Friday, June 08, 2007 9:47 PM
To: Christopher Painter
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Future of Votive?
Not sure about the Votive information, but if you pass -gg to heat as an
option it will generate guids for you instead of inserting the
"PUT-GUID-HERE" message.
On 6/8/07, Christopher Painter <[EMAIL PROTECTED]> wrote:
I've been playing with Votive and I really like the way it plugs into VS and
uses MSBuild. My installs are primarily InstallShield based, and they will
remain that way, but I would like to break some of the xcopy type logic out
into seperate merge modules and let developers maintain them.
My developers looked at Votive and basically said that they have no
intention of entering raw xml to maintaing the dir/file trees associated
with these merge modules.
Will Votive ever have a Right Click | View Designer feature? The perfect
tool for me would take the VS features the Votive already has and give a vey
simple drag and drop approach to directory structure creation similar to the
way VDPROJ does it.
The tool would need to automaically generate relative path file links and be
very careful to not let developers do stupid things. We are trying to
support minor upgrades so features like `deprecate file` to cause
transitive style puncturing of components would be really good.
I tried playing with heat but my developer don't want to have to use the
command line and they want to be able to easily add and remove from the tree
as needed.
Eitherway I have a question about heat.... I notice that it sets components
to Guid="PUT-GUID-HERE" and uses absolute paths instead of relative paths in
the Source attribute. When you import a large directory structure, whats
the easiest way to update those? It seems very annonying to have to go
through hundreds of these to get an WXS file that will properly work.
_____
Looking for a deal? Find great prices on flights and hotels
<http://us.rd.yahoo.com/evt=47094/*http:/farechase.yahoo.com/;_ylc=X3oDMTFic
DJoNDllBF9TAzk3NDA3NTg5BHBvcwMxMwRzZWMDZ3JvdXBzBHNsawNlbWFpbC1uY20-> with
Yahoo! FareChase.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
