| 
|
QuoteRef: zandBT11_2005
Topic:
constraints
Topic:
declarative vs. procedural representation
Topic:
user interface tool kits
Topic:
flavor analysis and typestates for supplementary type checking
Topic:
access to objects by a path
Reference
Zanden, B.T.Z., Halterman, R., Myers, B.A., Miller, R., Szekely, P., Giuse, D.A., Kosbie, D., McDaniel, R., "Lessons learned from programmers' experiences with one-way constraints", Software-Practice and Experience, 35, November 10, 2005, pp. 1275-1298. Google
abstract ;;Quote: survey of one-way constraints in two user interface development tookkits, Garnet and Amulet
abstract+;;Quote: allow arbitrary code in constraints; constraints are difficult to debug; easily used for graphical layout; difficult to use for other purposes
1276 ;;Quote: a one-way constraint determines the value of a variable from an expression; e.g., label.left = frame.left+10
1280 ;;Quote: primarily used constraints for graphical layout; preferred a layout manager for simple layouts
1280 ;;Quote: constraints make applications more modular; define at point of use, automatically adjusting to other objects; avoids change/delete notification
1282 ;;Quote: constraints are hard to debug -- cyclical constraints, bugs appear far from source, spaghetti code, slot errors, evaluation misunderstood
1284 ;;Quote: for graphical interfaces, one-way constraints will only be used for layout; students prefer a procedural approach
1287 ;;Quote: avoid using annotations to guide the constraint solver; error-prone
1294 ;;Quote: path expressions such as self.parent.frame.left are error prone; brittle under reorganization; use get_child and get_parent instead
Topic: constraints (35 items)
Topic: declarative vs. procedural representation (54 items)
Topic: user interface tool kits (31 items)
Topic: flavor analysis and typestates for supplementary type checking (68 items)
Topic: access to objects by a path (13 items)