Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

OLD TODO (most of these are done)

Events

To Node and Scene
For GetAttribute and ExecuteAction

...

Add it to Canvas, ImageView, and Labeled (Label, Button, Cells, etc)
As a rule: any place that answers TITLE should offer alternateText.

- Pro: easy to provide a more descriptive text than what is in textProperty.
- Con: not sure that is common case
- Con: that can be done using the event
- Con: can be added later

...

- Only Label can easily be used as label
- Use the event to any node as label

Other Option: Move Label#labelFor up to Node
*Current resolution is to take no action. *

Virtualization

Pages in the pagination. -> Probably Yes
Tabs in the tab pane. -> Probably yes
Children in the parent. -> Probably not, to the best of my investigation, Mac for example, insists on getting the whole NSArray in AXChildren.

*No conclusion reached.*

getAccessible() & Accessible

Probably remove the method from Node and  Accessible class from the API.

*yes to remove getAccessible() and Accessible()*

Method names

node#accGetAttribute
node#accExecuteAction
node#accSendNotification

...

Better names ?

node#accGetAttribute ->
* node#accessibilityGetAttribute() - Too long?
node#accGetAttribute -> node#GetAttribute()  -  Not allowed, only properties can start with “get”* node#accessibleGetAttribute()
* node#getAttribute() - break the rule (such as user data)
* node#queryAttribute()
* node#valueForAttribute()
* node#namedAttribute()

* Current plan is to use getAttribute(), executeAction(), sendNotification() *
Yes: breaking the rule for getAttribute() 

Use Jira Search

OLD TODO (in process to port this to Jira)

...