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

Suggestions for Future Releases

Last post 14 minutes ago by Stéphane Bergeron. 190 replies.
Page 12 of 13 (191 items)   « First ... < Previous 9 10 11 12 13 Next >
Sort Posts: Previous Next
  •  11-18-2008, 3:55 AM 3689 in reply to 3687

    Re: Suggestions for Future Releases

    Hi victor,

    thanks for a swift reply.

    4. "populate with defaults" button might do the trick, but you could also consider having a checkbox in the SelectListEditor, when creating a new Selectlist, saying "use top as default" or something like that.

    7. That is a possibility and that is what we do now. But somehow I would like it all to be collected in the RP file.

    10. Of course. Mystically, I forgot about this feature when I wrote it on my wishlist.

    11. I'm not sure if no. 11. has been mentioned before but would it perhaps be something you would consider for a future release?

    also, one thing I forgot to mention though I am aware that it has been said before: Annotations in spreadsheet form. This would give a very nice overview and the possibility of quickly annotate alot of elements. In my opinion, a much better user experience.


    Thanks

    Kris
  •  11-18-2008, 9:43 PM 3693 in reply to 3689

    Re: Suggestions for Future Releases

    Hi Kris,

    11 does make sense and I can see how it can save you a lot of time. In the meantime, you can consider creating separate generator configurations for each department. You can create more configurations using Generate->More Generators and Configurations.

    Also, in the dialog you'll see an option to generate a CSV report. That report is essentially a spreadsheet of the annotations. This is one-directional currently. There isn't a way to import changes made to the spreadsheet back to Axure RP.

  •  11-19-2008, 6:21 AM 3695 in reply to 3693

    Re: Suggestions for Future Releases

    Creating separate generators is definitely a solution. This didn't occur to me before.

    Thanks a lot!

  •  11-19-2008, 4:47 PM 3707 in reply to 2221

    Re: Suggestions for Future Releases

    This forum needs to be better organized. I never know where to reply :)

    I just started playing with a new service called Protonotes at http://www.protonotes.com. This seems like a natural fit for Axure (until Axure develops some fancy schmancy commenting features). The only problem is that it requires injection of some code into the html <head> element.

    It would be pretty sweet if there was a way to embed some code in the <head> of all documents in a project. It could be part of the HTML prototype generation. 

    Bonus points if you cut a deal with Protonotes so all we have to do is fill in our group id and Axure automatically generates the required code.

    Keep up the good work folks!

    Filed under: , ,
  •  11-19-2008, 8:14 PM 3710 in reply to 3707

    Re: Suggestions for Future Releases

    Thank you. Yes, it would be nice to be able to easily add extra javascript to the pages to integrate services like Protonotes. We'll look into tool that lets you add javascript to the HEAD tag in all the generated html files in the prototype folder (except the non-page files). Let me know if you beat us to it!

  •  11-20-2008, 3:55 AM 3716 in reply to 3710

    Re: Suggestions for Future Releases

    victor:

    Thank you. Yes, it would be nice to be able to easily add extra javascript to the pages to integrate services like Protonotes. We'll look into tool that lets you add javascript to the HEAD tag in all the generated html files in the prototype folder (except the non-page files). Let me know if you beat us to it!


    Maybe you could make an include file that doesn't get overwritten when you generate the prototype, but does get generated when the include file doesn't excist?
    (When the include file doesn't excist, generate a empty one.)

    This way users can put there custom code in the include file per page.

    Or maybe you could make 4 versions of the include file:

    - one per page in the head
    - one per page in the body
    - one for the whole project in the head
    - one for the whole project in the body

    It may be a little difficult for those not familiar with include files,
    but isn't the custom code something for the "experienced" users?

    Filed under: ,
  •  11-20-2008, 6:00 PM 3726 in reply to 3716

    Re: Suggestions for Future Releases

    Hi Koen. Thanks for the suggestion. I can see how that could work.
  •  11-25-2008, 5:00 AM 3757 in reply to 3726

    Re: Suggestions for Future Releases

    We'll see in the next release what you guys made of it :-)
    *just another quick remark: The image in front of "Delete Row(s)" in the right-click menu on tables is still wrong*
  •  12-03-2008, 3:14 PM 3802 in reply to 3726

    Re: Suggestions for Future Releases

    Has there been consideration for adding shared project history to the specification document, or even better, the option to include it in the doc?
    Filed under:
  •  12-04-2008, 8:33 AM 3809 in reply to 3802

    Re: Suggestions for Future Releases

    One important feature that will be useful is to allow interactive case development on dynamic panels, so that when a dynamic panel is clicked itself it can change a state.

    Cheers and great software!

     

    Filed under:
  •  12-04-2008, 8:50 PM 3814 in reply to 3809

    Re: Suggestions for Future Releases

    kosarkasx23:

    One important feature that will be useful is to allow interactive case development on dynamic panels, so that when a dynamic panel is clicked itself it can change a state.

    Cheers and great software!

    Currently, you can affect a dynamic panel with interactions on widgets within the dynamic panel's states. To make the click of a dynamic panel change its own state, you could put a rectangle widget in the first state and add the interaction to the rectangle.

  •  12-10-2008, 2:19 PM 3836 in reply to 3707

    Protonote Tool

    Attachment: HeadInsert.zip

     

    I started playing with Protonotes myself, and I agree that it would be useful to be able to automatically insert Protonote code and options when generating a prototype.  I decided to take a little initiative myself, and I wrote a script that lets you insert code into the <Head> tag of all files in a directory that end in .html.  I've attached the script to this post as a .zip file.

    Just drop the HeadInsert.exe file into your prototype directory, run it, then paste your Protonotes code into the text box and press the insert button. For example, I pasted the following:

    <script src="http://www.protonotes.com/js/protonotes.js" type="text/javascript"></script>
    <script type="text/javascript">
    var groupnumber="##############";
    </script>

    into all of my prototype HTML files.

    I recommend making a backup of your prototype files if they are important, as there is no way to reverse the process short of opening each .html file and removing the code you inserted.  I am not responsible for anything unexpected that happens to your files.  If anything does, let me know (please provide any errors that are given by the program).

     

    InsertHead
  •  12-11-2008, 3:36 AM 3838 in reply to 3836

    Re: Protonote Tool

    Wow, this looks very nice!
    Haven't had the time to test it yet, but will :-)

    Maybe it's an idea to insert comments in the html like:

    <!-- start insert html -->

    <Your custom code>

    <!-- end insert html -->

    Then maybe you could make a script that scans the pages on these comments... reed them, display them in your program and you can update/delete the inserted html.

    Just some inspiration for your development :)

  •  12-11-2008, 2:43 PM 3845 in reply to 3838

    Text Panel Bug

    I noticed that when I change the font for a text panel, then click off of it (so it becomes deselected), then select it again, the font name doesn't update in the text formatting toolbar dropdown.

    The font name updates for other widgets, though (rectangles, buttons, etc.) 

  •  12-12-2008, 10:57 PM 3857 in reply to 3845

    Re: Text Panel Bug

    pixeler:

    I noticed that when I change the font for a text panel, then click off of it (so it becomes deselected), then select it again, the font name doesn't update in the text formatting toolbar dropdown.

    The font name updates for other widgets, though (rectangles, buttons, etc.) 

    The font dropdown in the toolbar shows the font style that was last applied to the text panel widget as a whole. If you are setting the font on selected text within the text panel while editing the text (as opposed to selecting the text panel widget and setting the font), the toolbar will not show the font that was applied to the text within. This makes sense if only parts of the text are set to a new font, but not when the entire text is set to a new font. We will look into that.

Page 12 of 13 (191 items)   « First ... < Previous 9 10 11 12 13 Next >
View as RSS news feed in XML