In this example I have made a Timer with start, stop and reset functions based on my previous example of how we can use a dynamic panel for scripting re use and control.
I won’t go into how it works, as it is the same technique as mentioned previously, so just take a look for your selves at the live example or Download the Axure 6 dynamic panel action controller Timer 02 source file (74KB)
While creating this example I came across a “bug” which, I think, I’ve seen previously when developing with Javascript many years ago, I have fixed this in the example but I also left the other example for your interest. (Note: I strongly believe this is still a javascript issue rather anything to do with Axure).
Recap on the initial ideas I thought this technique may be interesting for;
- Action controller (to support ideas of prototype maintainability and easy modification)
- Timer (to provide a sense of external events – real time social apps or billing apps)
- Listener function – suggested by @mrjeffharrison – (perhaps to use for enabling buttons on a form based on complex validation checks – could be built on a combination of the first two examples*)
*I will try and make time to post an example of the Listener function, time permitting.
Love to hear your thoughts on these examples!
Follow the responses to this post through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
Same example with design http://www.axuregames.com/archives/retro-stopwatch-in-axure-rp-5-6/
Hi Axure Games, thanks for adding a really good example of a Timer made in Axure 5.6, I think it really shows the difference between 5.6 and 6 very very well.
The approaches we have both used result in very similar end results – Looking at your RP file it reminds of the numerous work arounds, hacks and clever tricks that had to be used just to model this type of thing (just looking at the number of items on screen under the timer graphicss is amazing).
Thankfully Axure 6 makes it far easier to implement this type of thing now with a lot less effort which should be the goal of prototyping – do more and do it quicker which should translate into having more time and freedom to try ideas out, prototype, validate and change / refine – which is the whole point of prototyping.
The examples I am posting are about building better prototypes (faster, richer, and that are hopefully more maintainable and extendable) as prototyping as an activity should be able to focus on idea communication not functional development.
Thanks for posting your link – loving some of the things you have put together, awesome! shuddering to think how much time it took in earlier version of Axure, great effort!
Best regards,
Richard
control