Flame is a user interface for creating windows installers using WIX. Writing the XML files for WIX is a huge headache, so I decided to write a tool to make it so I never had to deal with it again. Flame makes it quick and easy to create a simple windows installer including feature sets, shortcuts, registry entries, and generating GUIDs for you. Flame does NOT delve deep into the WIX functionality and doesn’t even touch patching (although it does set up your installer to work with patching later). However, even if you need a complicated install, Flame generates a great starting point.
Because everyone structures their projects a little differently, this is very difficult to test and debug. It works for the way -> I <- do things, but it might not work for the way YOU do them. Please please please send me an email or a leave a comment with any bugs or suggestions on how I can make the tool better.
Screenshots
License
Flame is released under the GPLv3. While this restricts the license on anything you create from the Flame CODE, there is no restriction on INSTALLERS generated with Flame. In other words, you can use Flame to create commercial installers without worrying about any licensing issues. For other license questions, please read the GPLv3 at http://www.gnu.org/licenses/gpl.txt
Download
Get the latest version from SourceForge
Change Log:
- 1.1.0 - Major bug fixes (February 27, 2008)
- If exit save fails, Flame shouldn’t close anymore so user can have another chance
- Fixed bug with save files that have no files
- Fixed bug with save files that have no shortcuts or registry entries
- Fixed bug with InstallDir UI type
- Added some code to work with Wix v3 - not functional yet
- Fixed bug with wixpath - can now handle paths with spaces
- Fixed bug in shortcut code making desktop shortcuts use the wrong icon index
- Updated shortcut code with a workingdirectory attribute so relative paths inside your programs should work
- Changed Wix exe output in logs to be more obvious
- Fixed bug where folders with subfolders but no files were being left out
- Fixed bug with wxs components when features had multiple word names
- 1.0.0 - Initial Release (February 24, 2008)
3 responses so far ↓
1 DexterSinister // Feb 26, 2008 at 11:38 am
Hi -
I downloaded this from SourceForge … and I can’t get it to generate an installation package, and it doesn’t create a log file for troubleshooting.
I installed using the MSI package … so I’m not sure what [if anything] I could’ve done wrong …
Any thoughts ?
Thanks,
-Dexter
2 Keeyai // Feb 26, 2008 at 12:19 pm
Hmm - it couldn’t be anything you did wrong. What DOES it do? Can you run the program? Can you create and save an installation setup? How far, if anywhere, does it get when you generate and what does it say in the log section of the application?
3 Tail Update // Aug 13, 2008 at 6:31 pm
[...] Flame [...]
You must log in to post a comment.