- Joined
- 27 September 2006
- Posts
- 200
- Reactions
- 0
Part 3 - underlying behaviours
Imagine you have this wonderful trade idea but it needs a formula to work out the profit/loss.
By allowing grouped areas of the note taking space to have a behaviour assigned to them it turns it into a mini spreadsheet or even a formatted area. I know one of the annoying things about Excel is I can't see the formula AND the result at the same time. A bit of chunking and zoom functionality solves this. Not only that but the cross references between calculation areas (ie. cells) is visible as lines between rectangles.
Need to pretty print today's trading activity, draw a "string" thru those items you want, zoom in on them arrange them into a roughly coherent order, group them and attach a document formatting behaviour to the group.
I mentioned originally that I wanted all behaviours including keystroke and mouse controls to be programmable - well by zooming down far enough the behaviours are nothing more than a series of linked boxes that control the flow of keystrokes and mouse movements attached to various behavioural modules.
This kind of functionality comes from some very seminal work I did on object based design and development which also extends up to project management.
The final key is storing and indexing all this.
Imagine you have this wonderful trade idea but it needs a formula to work out the profit/loss.
By allowing grouped areas of the note taking space to have a behaviour assigned to them it turns it into a mini spreadsheet or even a formatted area. I know one of the annoying things about Excel is I can't see the formula AND the result at the same time. A bit of chunking and zoom functionality solves this. Not only that but the cross references between calculation areas (ie. cells) is visible as lines between rectangles.
Need to pretty print today's trading activity, draw a "string" thru those items you want, zoom in on them arrange them into a roughly coherent order, group them and attach a document formatting behaviour to the group.
I mentioned originally that I wanted all behaviours including keystroke and mouse controls to be programmable - well by zooming down far enough the behaviours are nothing more than a series of linked boxes that control the flow of keystrokes and mouse movements attached to various behavioural modules.
This kind of functionality comes from some very seminal work I did on object based design and development which also extends up to project management.
The final key is storing and indexing all this.