We’re still trying to get to the bottom of the “TargetInvocationException” error. This build just adds a small change so the bug report sends some additional information about where that error is coming from.
If you’ve seen that error, we’d appreciate it if you installed this version and submitted the bug report the next time it happens.
We’re getting closer to a full featured beta and want to get these bugs out of the way too.
That last build (5.6.0.2544) had a pretty big issue initializing the Wireframe and Objects menu. We fixed that in this build.
Fixed: - Shortcuts for the Wireframe and Objects menu are not right and may be causing initialization issues
We’ll keep a running list of known issues in this build here.
Priority 1 bugs: - Startup / New File (TargetInvocationException): Error when starting the app creating a new file. - UriFormatException opening certain files.
We’ve just posted an update to Axure RP for Mac 5.6.0.2544 to fix the Priority 1 bugs in 5.6.0.2533.
Fixed: - Rich text error when generating prototypes: This happened on specific files and we’re able to repeat it (thanks to a sample file from a customer). - Reset View: Using View->Reset View threw an error. - Deleting root level pages: Deleting pages in the sitemap at the root level (like Home) caused an error. - Accented characters caused an error
CSV generation and some minor UI tweaks were also added to this release. We’ve been getting a lot of great feedback and we’re working on them, but most have not been included in this release.
Like before, we’ll keep a running list of known issues in this build here.
Priority 1 bugs: - New File: Error when starting the app creating a new file. We put in a fix for this but are not able to repeat the error. Please let us know if it shows up in this build. - UriFormatException opening certain files. - Shortcuts for the Wireframe and Objects menu are not right and may be causing initialization issues. A new build will be up shortly to repair this (1/5/10 12:43PM PT)
The first 24 hours has been a lot of fun. Thanks for all the great feedback and bug reports. Loving all the UX tips too. Keep em’ coming!
We’re planning to keep an up-to-date list of the more critical bugs and missing features here. Please continue to submit bugs through the app and by email to support@axure.com.
Priority 1 bugs: - Rich text error when generating prototypes: This happens on specific files and we’re able to repeat it (thanks to a sample file from a customer). Still working on finding the source. - Reset View: Using View->Reset View throws an error. - Deleting root level pages: Deleting pages in the sitemap at the root level (like Home) causes an error. - New File: An error happens occassionally when starting the app which creates a new file. You can get past the error but an error dialog appears. - Accented characters cause an error
Axure RP for Mac Alpha aka MAxure is now available for download here.
We didn’t quite make it to Beta before the end of 2009, but we’re really excited to show you where we’re at and start getting your input (and help!). We’re targeting end of Q1 2010 for the final release.
What to expect: Most of the Axure RP 5.6 features are available along with some UI enhancements including a new properties pane and redesigned interactions dialog. There are still some features missing including shared projects, CSV generation, search & replace, print, spell check and zoom.
We’ve successfully created some prototypes in MAxure using core features like dragging and dropping widgets, adding annotations and interactions, and generating prototypes. But we are still running into new bugs regularly. Specification generation works and the .docx files can be opened in Word 2004 with the compatibility pack. You can find directions for installing the compatibility pack here.
The files are compatible with Axure RP 5.6 on the PC, which is a nice backup if you run into any issues.
This alpha version expires February 28, 2010. A valid alpha/beta will be available until the final release of 5.6 for Mac, so your work will not be interrupted.
How can you help? Please submit bug report dialogs that pop-up in the application. Any information that might help us repeat an error is really helpful. We’re also looking for usability issues that are Mac specific (like Cmd+Q shouldn’t increment the footnote number). You can send those to support@axure.com along with any bugs and requests.
What’s next: We’ll continue to release Alpha/Beta builds until the final release and post known issues here. You can keep track of updates here, on our blog or by following us on Twitter. And we’re also in progress with 6.0. Who needs to sleep? :)
Last month, Victor gave a sneak peek of MAxure at the Ask Axure session of AxureWorld. Ezra Schwartz was kind enough to convert and publish all of the sessions from the event. Skip ahead to 26:55 in the video to see MAxure. You can check out other recorded sessions from AxureWorld at www.axureworld.com.
Wondering how development is going? Come and see for yourself. We will be giving a sneak peek of MAxure during the Ask Axure session this Saturday 10th at AxureWorld.
As we’re converting dialogs, we’re also looking for opportunities to improve them. One feature that uses a lot of dialogs (ahem… maybe too many) is building interactions.
Currently, the Interaction Case Properties dialog has two modes: basic and advanced. The basic editor is nice because you can see all the available actions right away and can add actions with one click. The advanced editor is nice because you can add as many of a type of action as you like and order them as needed.
The goal is to combine the benefits of the basic and advanced modes into one AND reduce the number of nested dialogs.
Here is a video of a prototype (created in Axure RP) of a proposed new design for the Interaction Case Properties dialog.
Figuring out how to build MAxure was definitely a challenge given our two main criteria:
1. MAxure has to share a majority of its code with Axure RP for Windows 2. MAxure has to be able to deliver a Mac experience
The first is important to reduce development time, but also to keep future development efficient. Having to maintain separate code for each new feature or fix going forward would not be good. And the second is… well… you know why the second is important.
Axure RP is built mostly in C# on the Microsoft .Net 2.0 Framework. Thanks to the wonderful folks at the Mono project, we were able to run the non-UI related code from Axure RP on Mac with minimal effort.
As for the UI, that was a whole other ballgame. Getting a UI element as complex as the wireframe pane to work on both platforms from a single code base was not an easy task. We first removed all Windows-specific controls and replaced them with custom “Windowless” controls. Then a (magic) drawing layer was developed so that the same C# code could render and function on both Windows and Mac. This layer also handles themes so a control can look and behave different on each platform. Very cool stuff and amazing to see it come to life.
The added flexibility from creating custom controls is also giving us an opportunity to make enhancements while we convert, which will work on both Windows and Mac. How great is that?
We’re going to make sure that MAxure is built well and is architected so that Axure RP on both Windows and Mac can and will continue to improve together.
- Victor, PM
P.S. A quick thanks to Aaron at Big Nerd Ranch for providing great Mac OS training.
Thanks for the great response to the screenshot in our last post. We’re excited that you’re excited! One question coming up a lot is how licensing will work once MAxure is released. Some companies charge more for the Mac version of their software. Others charge the same but ask you to buy a different license for each OS. We’ve decided to keep it simple. Here’s how our licensing works today:
“Each license can be used by the same person on two PCs (or Mac through virtualization).”
Once the Mac version is released, here’s how the licensing will work:
“Each license can be used by the same person on two PCs, two Macs, or one PC and one Mac.”
We’re basically going to continue with the same licensing but let you choose to install on PCs, Macs, or one of each.
Because licenses come with 12 months of free updates, many of you will be able to use your current Axure RP license for the Mac version for no additional cost. If your license has expired for updates, you can renew your license for $149.
For new customers, a single user license is $589 (and $539 each for 5+ licenses) and comes with 12 months of updates.
As always, if you have any questions or concerns, feel free to send us an email to contactus@axure.com or send a tweet to @axurerp.
…Until next time!
P.S. We’re hoping to have something to show customers before the end of the year.