Thanks David. We'll take a look at the BPM notation and see which widgets are missing.

do you plan on changing the import process?

currently, it takes multiple steps to import Masters, Pages, Annotations, Generator settings and Styles.

any chance that importing these elements can use checkboxes vs radio buttons so multiple elements can be imported at once?

 
thanks
 

---

Disclaimer: I am not an employee of Axure nor am I compensated by the company in any way, shape or form. Rather, I have a vested interest in its continued development as an avid user of the application on a daily-basis.

Sorry I am new to this forum, and I can't find the Post button.

Nat:

Sorry I am new to this forum, and I can't find the Post button.

There is a button "Write a New Post" on this page: http://axure.com/CS/forums/4/ShowForum.aspx

Is that what you are looking for?

dingle:

do you plan on changing the import process?

The import feature is in line for some enhancements. One thing that would be nice (like you mentioned) is combining import of the different types of elements. We are also planning to add import of variables from file to file.

Hey Victor,

Here's another thing I would find helpful for a next release that would be easy for you guys to do.

When you save the RP file, could you also have it save the view of your Sitemap?  My RP file is getting huge, I have tons of pages, and it's annoying when I open my Project, and I see all 100 pages expanded.  I find I'm often collapsing the sections so it doesn't look so overwhelming.  Of course each time I open Axure again, I often do the same thing over again.  It would be nice if the RP file would remember exactly how you had your screen laid out the last time you saved.  And maybe add an "Expand All" option for people who like to see their Sitemap expanded in full.  just a thought.

---

Daren

Thanks Daren,

This has been a pretty popular request. We're trying to get it in scope for v5.

Another thing I thought of, perhaps it's been mentioned before...  When generating the specification, it puts footnotes next to any single object that has any kind of interaction.  Often, I have various things in the wireframe, which have interactions, but I don't want to make annotations for.  Perhaps it's because I have the same button visible on the page 10 times.  (Like in a Search Results table)  I have all of these buttons functional, so they have interactions associated with each.  However, I don't want to overwhelm the reader with the exact same annotations for the other 9 buttons.  So I don't label them or put any annotations on them.  However, the specification still shows the footnotes icon for these 9 buttons that don't have any annotations and it looks confusing.

For a next release, could you either:

1.)  Only add footnotes for objects which have a label?

2.)  Or create some option when creating the Specification that says, "Only show footnotes for objects which are labeled."  Or something to that effect...

Thanks!

---

Daren

Hi Daren, Thanks. Sounds like you are looking to add a filter to the footnotes (and the rows in the table containing the interaction and annotation information). It has come up before to be able to selectively choose which widgets to show footnotes on in the specification. We'll add this to the list.

Cool.  That would probably work.

One more request...  While we're on the subject of Specification improvements, I wonder if others have already requested what I'm about to.  On the surface, it seems one of the easier ones to implement.

I end up using the "Page Notes" section QUITE a bit to give an overview of how the entire page works, etc.  Sometimes on my final spec, just the Page Notes section has almost an entire page of wording and instructions.  Unfortunately, it never looks the greatest since you can't bold or format text, or add bulleted lists or anything.

Since the formatting tool bar is already there, it would be really nice if it remained active when you had the focus inside the "Page Notes" section, and you could use it to format your text if desired.

Thanks for all your prompt replies!  Any update on the next version's potential release date?

 

---

Daren

I'd also add:

• Productivity: allow shortcuts on all commands, plus a shortcuts mapping editor if posible
• External image linking: I usually make pngs using fireworks which I annotate using axure, so whenever an image changes, I need to reimport the image. Flash does a wonderful work on this, with its library and "update" feature. It would be great to have "autoupdate" and "manual update"
• Some form of modularization among projects would be great too. For example, a common header or widget that can be updated in one location and impacts all axure projects (like an include file in a server) 

fighthefire:

Thanks for all your prompt replies!  Any update on the next version's potential release date?

Hi Daren,

We're planning to release a preview of a "Shared Projects" feature this month to get some early feedback. Shared Projects allows multiple people to work on the same Axure RP project using a check in/check out system at a page/master level. This is going to be part of a larger 5.0 release which we are planning for Q1 next year. Thanks again for all the requests and feedback.

Victor

guillermoermel:

I'd also add:

• Productivity: allow shortcuts on all commands, plus a shortcuts mapping editor if posible
• External image linking: I usually make pngs using fireworks which I annotate using axure, so whenever an image changes, I need to reimport the image. Flash does a wonderful work on this, with its library and "update" feature. It would be great to have "autoupdate" and "manual update"
• Some form of modularization among projects would be great too. For example, a common header or widget that can be updated in one location and impacts all axure projects (like an include file in a server) 

Thank you. These makes sense. For the image linking... in the interim, if you are using an image in multiple places in a file, it can save you some time by creating it as a master. Then you only need to update it once.

Here's another one for you:

Consider providing a way to globally Send to Back or Bring to Front all instances of a master. I've run into the need for both recently.

In one case I applied a background image to most of the pages in a site. To do that I needed to open each page, select the master on that page, and Send to Back. That was harder to set up, but easy to maintain, as they stay put, and are out of the way.

In the other case, I have a dynamic panel that could appear over any page of the site (it's a "Sign In" form). That's easier at first - when I initially did Add To Pages it added them all "in front of" the other elements. That's fine, but as I'm working I've found myself dropping other things in front of the Sign In panel, or I've moved it to the back to work more easily, then forgot to to Bring to Front when I was done. It would be great if, before I generate the "final" (ha ha...) version, I could bring all instances of this master to the front. As a workaround I've removed the master from all pages, then re-added it, which does the trick.

Keep up the great work on this product! I've jumped from absolute newbie to designing a very complex site in about two weeks, with very little frustration (and virtually no learning curve). The prototype has been a great tool for internal design discussions, and for presenting concepts to the client.

---

Linda Eskin

"Ask. Observe. Think. Design. Repeat."

Linda Eskin:

Consider providing a way to globally Send to Back or Bring to Front all instances of a master. I've run into the need for both recently.

Hi Linda,

Thank you for the requests. The "Place in Background" behavior for masters was intended to help with the Send to Back use case. If you right-click on a master in the masters pane, you can set the behavior to Place in Background. When you add it to a page, it will be sent to the back and locked in the position it was created. When using Add to Pages, there is a similar option. You can also right-click on a master on a page, and set it to be placed in the background.

I could see how the Bring to Front on all of a particular master would be useful. We've considered adding an action so you can bring a dynamic panel for example to the front dynamically to help with some other use cases, but it doesn't sound like that would necessarily help with yours.

Glad to hear you were able to learn to use Axure RP so quickly!