Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
interaction:axure_feature_ideas [2015/02/15 09:08]
sam
interaction:axure_feature_ideas [2015/02/15 13:53] (current)
sam
Line 36: Line 36:
 === Solution === === Solution ===
  
-Create a function that revert all properties on a widget to be inherited from the parent adaptive view.+Create a function that revert all properties on a widget to be inherited from the parent adaptive view. Here is how it could work:
  
   * Select a widget.   * Select a widget.
Line 43: Line 43:
  
 In addition to this add a "​inherited"​ indicator to all properties, that can be inherited. Clicking on the indicator will enable "​revert to inteited"​ for that value. In addition to this add a "​inherited"​ indicator to all properties, that can be inherited. Clicking on the indicator will enable "​revert to inteited"​ for that value.
- 
  
 ====== Extend axQuery ​ ====== ====== Extend axQuery ​ ======
Line 49: Line 48:
 === Problem === === Problem ===
  
-The JavaScript query function of the $axure object is somewhat limited. To my knowledge it can only find widgets with a given name. An example:+The JavaScript query function of the $axure object is somewhat limited. To my knowledge it can only find widgets with a given name or id. An example:
 <​code>​ <​code>​
 var query = $axure('​@Hello'​);​ // Finds all widgets named '​Hello'​ var query = $axure('​@Hello'​);​ // Finds all widgets named '​Hello'​
 +var query = $axure('#​Hello'​);​ // Finds widget with id '​Hello'​
 </​code>​ </​code>​
  
Line 73: Line 73:
 ====== Interaction styles in custom widget styles ​ ====== ====== Interaction styles in custom widget styles ​ ======
  
-== Problem ==+=== Problem ​===
  
 It should be possible to define interaction styles such as MouseDown, MouseOver in custom widget styles. It should be possible to define interaction styles such as MouseDown, MouseOver in custom widget styles.
  
-== Solution ==+=== Solution ​===
  
 Make it so that interaction styles can be selected in custom widget styles. A widget that is assigned a custom widget style where interaction styles are specified use these interaction styles. Make it so that interaction styles can be selected in custom widget styles. A widget that is assigned a custom widget style where interaction styles are specified use these interaction styles.
Line 83: Line 83:
 ====== Panel state styles defined in custom widget styles ​ ====== ====== Panel state styles defined in custom widget styles ​ ======
  
-== Problem == +=== Problem ​== =
  
 It should be possible to define panel state styles in custom widget styles. It should be possible to define panel state styles in custom widget styles.
  
-== Solution ==+=== Solution ​===
  
-When a custom widget style include panel state formatting, is assigned to a widget, this formatting ​this applies to all panel states of the widget.+When a custom widget style include panel state formatting, is assigned to a widget, this formatting ​then applies to all panel states of the widget.
  
 ====== See masters and dynamic panels in context when editing ​ ====== ====== See masters and dynamic panels in context when editing ​ ======
 +
 +=== Problem ===
 +
 +When a master or dynamic panel is edited it is not possible to see the context it is used in.
 +
 +=== Solution ==
  
 Show the context in which a master or dynamic panel is used as a "​background"​ image, when a master or dynamic panel is edited. A master can be used in multiple contexts, so the master must be opened from the context that should be showed in the background. Show the context in which a master or dynamic panel is used as a "​background"​ image, when a master or dynamic panel is edited. A master can be used in multiple contexts, so the master must be opened from the context that should be showed in the background.
Line 97: Line 103:
 ====== Masters in repeaters ====== ====== Masters in repeaters ======
  
-If a repeater uses a master. It should be displayed ​correctly in Axure. Currently it only works when viewed in a browser.+=== Problem === 
 + 
 +If a repeater uses a master and the OnItemLoad event on the repeater change widgets in the master. It is not rendered ​correctly in Axure. Currently it only works when viewed in a browser
 + 
 +=== Solution === 
 + 
 +Fix the bug.
  
 ====== Folders/​Layers ====== ====== Folders/​Layers ======
Line 109: Line 121:
     * Widget C     * Widget C
     * Widget D     * Widget D
 +
 +====== Adaptive view transitions =====
 +
 +Enable transitions between adaptive views. As a starter enable "​swing"​ transitions of positions.
  
 ====== Page States ====== ====== Page States ======