Welcome to Axure Community Site Sign in | Join | Help
in Search

Code: Axure

  • WinFX Coming of Age

    It's been mentioned on several blogs already, but Microsoft, yesterday, announced another CTP (an acronym for Community Technical Preview, which is itself a fancy name for an unstable beta).  The exciting thing about this one is that it's feature complete.  From this point forward, all your WinFX code will work with only minimal changes in the final version.  I had modeled some simple applications with earlier WinFX CTPs, but haven't tried to create more complex applications because the xaml format changed from CTP to CTP, and a couple times, it took me a while to figure out all of the breaking changes.  No more.  As I understand it, Microsoft has comitted to not make any significant breaking changes from this point forward.

     

    I'm really excited about WinFX.  It's going to allow us (developers, designers, product managers and the like) to build richer applications quicker. Here's an example of how we might be able to take advantage of its capabilities in Axure RP.  One of the things we're really concerned about when desigining Axure RP is screen real estate for the wireframe designer. With the toolbars on the top; the sitemap, mastermap and widget library on the left; and the annotations and interactions on the right, space is at a premium.  WPF gives us some new features that can help address this.  One is that it supports partial transparency.  An idea we had is that we could make the right sidebar partially transparent so you could see the wireframe through it.  Then when you move over to the annotations or interactions to edit them, the sidebar could become opaque.  Another feature is one that Microsoft Expression Interactive Designer (a long name for a product codenamed Sparkle -- get it: Flash, Sparkle) uses.  Sparkle lets you zoom in to and out of the sidebar on the right.  What this means is that rather than hiding the content of the sidebar when you make the width of the bar smaller, you can keep all of the content visible by scaling it. This could be a useful feature for the right bar in Axure RP too. Implementing this in WPF is as easy as setting a few properties.  In Win32, it's nearly impossible.  If you're interested, you can take a look at sceenshots of Sparkle here; the workspace zoom slider on the upper right is what lets you make the sidebar smaller or larger.

     

    On top of all this, WPF lets you do this in the browser too!  Anything you can do graphically with WPF in desktop applications, you can now do with browser applications.  Fancy Excel-like grids: check, beautiful animations: check, scalable ui: check.  But beware... to quote Uncle Ben (of Spiderman and not long-grain rice fame) "With great power comes great responsibility".

     

    Lest I sound like a shill for the folks in Redmond, there are definitely a few caveats:  First there's the WinFX Framework itself, an approximately 30MB download.  This would increase the size of the Axure RP Installer from 25 megs to 55 megs.  Unfortunately, as I understand, WinFX won't even be installed by default on Windows Vista (a whole other can of worms best left for another article).  Also, if security isn't done properly, users (corporations, especially) might feel compelled to deactivate WinFX in the browser just like they do for ActiveX controls today.  Fortunately on this front, security should be better than in Microsoft products past.  Don Box (an architect for the WCF, the networking part of WinFX) said that only 19 of 1123 source code files had "unsafe" code.  That means that less than 2% of the WCF code now has to be checked for (now famous) buffer overrun attacks that have become so commonplace.  2% is much easier to harden than 100%.  I haven't seen any numbers about the safety of WPF code, though.  Last but certainly not least, all of us have tons of code built in Win32 and HTML.  Porting that won't be easy either.  Axure RP Pro 4 supports nearly everything that Axure RP 2 did and we probably won't move to WinFX until we're sure that we will be able to continue to support it.

     

    I should also add that WinFX obviously isn't the only rich application framework out there.  There are a bunch of upcoming AJAX frameworks (indeed, more still to write about) and Mozilla and Safari are banding together to make an SVG-based application framework.  If you take nothing else from this long-winded article, let it be this: for all of us building applications (yes: developers, designers, product managers and the like), exciting times lie ahead.

    What do you think?

  • Moving to .NET 2.0

    If you're reading this, you probably noticed the new beta of Axure RP 4. We've made a bunch of changes since Beta 1, and, for the most part, this beta is feature complete. One of the big changes in this release is that we updated the version of the .NET framework required from version 1.1 to 2.0. We did not make this change lightly. We came to this decision after running a number performance tests. We discovered that file saving was 65% faster, file loading sped up almost 20%, spec generation improved 5%, and exporting files to images nearly doubled in speed. On top of that, .NET 2.0 uses less system memory. Not bad for a simple upgrade.

    One of our primary focuses for Axure RP 4 has been performance. We really wanted to make everything faster and make it use less memory at the same time. Upgrading the .NET framework furthered both these causes.

    I'll probably talk more about .NET 2.0 in the future, but I just wanted to let you know why we made the switch.

    As always, keep the feedback coming!
  • Hello, World!

    Greetings! Let me introduce myself. I'm Martin Smith, the Software Architect for Axure RP. We're coming up on the 4th version (and finishing the 4th year of Axure itself) and initially, I'd like to blog about some of the technical and design decisions that we made for Axure RP, version 4 specifically. To start, here's a listing of some of the technology we use to build Axure RP:
    • Microsoft .NET Framework -- Axure RP is built on .NET and Windows Forms.
    • Microsoft Word -- We create specifications by automating Microsoft Word (versions 2000 and later).
    • HTML/Javascript -- We build prototypes out of plain HTML + Javascript. No reader required.
    • CSV -- We can generate your page notes and annotations into a CSV file.
    This is not exhaustive, but these are the topics I'll be writing about in the coming posts. Also, If you would like to hear about something in particular relating to Axure RP, contact me and I'll try to write about it. In the meantime, keep letting us know what you think about the Axure RP 4 Beta.

This Blog

Syndication

Tags

No tags have been created or used yet.