Page 1 of 1

setting html attributes, annotations, ...

Posted: Tue May 24, 2011 11:34 pm
by hyounesy

Great tool guys! Thanks for making it available for free.
I have been trying out tiggr for a couple of days and I had a few questions:

Q: I am able to change the src attribute of an image to change the image interactively. However this only works when the image is in a main screen. As soon as I create a custom template, it stops working. Looking at the javascript code in the html, looks like the html attributes are not being referenced correctly for components in a custom template.

Q: Is there a way to change the html src attribute of an image, to one of local images in the project assets (through an event), rather than an explicit url?

Q: Is there a way to set the initial visibility attribute of a component to hidden? For normal screens, I can use the load event of the screen. However There is no Load attribute when I group a collection of components for custom made templates.

Q: Looking at the Feature page in the website, there is an Arrow item that can be used for annotations (http://blog.gotiggr.com/wp-content/up..., however in the actual environment, I only have Rectange, Ellipse and Callout.

Q: Is there a way to show annotations in the preview mode?


setting html attributes, annotations, ...

Posted: Tue May 24, 2011 11:48 pm
by akomolov

Hi!
Answers:

  1. great that you've tried it. I would guess this is a bug, let me report it to developers and see what they come up with

  2. not yet, let me think about it. What would be the best way to implement it , in your opinion?

  3. do you mean a visibility attribute of a custom component? Would you please share your scenario with me at akomolov at exadel dot com?
    4.the arrow got dropped during development, but screenshots were not updated. Do you think an arrow would be beneficial?

  4. we didn't intend annotations to be used in previews, because we treat a preview as a clickable/interactive prototype. So, not clear where/how to display annotations.

    In general, I can see that you are pushing our tool to its current limits(a new release with new features is coming soon). Feel free to share your ideas with us - we are listening!


setting html attributes, annotations, ...

Posted: Wed May 25, 2011 3:52 am
by hyounesy

Appreciate the quick response Andrei!

  1. Thanks for looking into it.

  2. Editor already allows specifying names for the images that are imported to the project assets. Can this be used as a variable id that can be used when setting html attributes?

  3. For example consider a custom component template consisting of a dialog with a button and a text box. I want the text box to be invisible initially, but set to visible when the button is pressed. I have shared an example project for you. I think it would be useful to add a visibility property to the components that can be set in the editor.

  4. I always have a use for an arrow :)
    I mainly need it to point to specific parts of the UI. it would also help to keep the annotation texts away from the UI itself and keep the UI less cluttered.

  5. I am looking for a way to include additional info/walkthrough in each screen for the viewer, such that they can be optionally turned on/off while the viewer is interacting with the screens. Having the annotations in the editor is helpful, but the viewer can't do interactions with the ui in the editor. I can think of a hacky solution by using normal text boxes that can be shown/hidden by clicking on a button. But I thought using annotations will be a more natural/cleaner way of doing so.

    Can't wait to see what's coming with the new release :) keep up the good work!


setting html attributes, annotations, ...

Posted: Fri May 27, 2011 9:35 pm
by akomolov

Hi, a follow up to your questions
#1: a fix will be deployed in production early next week.
#2: we'll add something like this, but need to think through details. can you please post it as a separate idea?
#3: the root cause is the same as #1
#4: well, I'll see if we can add it anytime soon
#5: a very interesting idea! can you post it as an idea as well?