Core Objects read the spec.
- Views have name conflict with foreign models having same names with attributes gonna need some design to have related model name distinguished from view attributes list name
- ActiveView
- presentation
- mode
- key [ undefined , null , value ]
- presentation = Presentation.activate ( key , mode )
- close ( key )
- Add reference from Attribute when models created
- View created with:
- new View(primaryModel, relatedModels, relatedIDs, attributeArray);
- Primary model
- Related models {'Customer': {model:customerModel, id: 'CustomerID'}
- Array of attributes (must have model ref / can't be standalone attribute)
- Add to getList as parm instead of Model
- make a putList like getList
- coerce() useless since have to have attribute instances limits - make util func ?
- Transport sendRaw & onRaw have no tests
- REPLInterface - handle presentation (WIP)
- view shows and leaves
- edit edits
- if commands present then waits for commands ?
- OR execute waits ?
- app.dispatch(request,response) ... response is not used review design
- Presentation use model property & modelConstructor method or get rid of
- Review models for completeness esp. Workspace and Session
- Interface.notify needs review
- Misc: improve coverage
- Misc remove bucket - replace example with closure variables as needed
- Review tequila for lingering todo
- model tests don't use SurrogateModel as much as it should
- MenuCommand ... Menu of commands for app
- InfoCommand ... about app and interface - store connection(s) - also sys info
- FindCommand ... model
- FavoritesCommand ... favorite models
- HistoryCommand ... logged activity
- WorkspaceCommand ... active models
- AlertsCommand ... shit you need to deal with