Carry over from a previous post...
Ideas are calculations, but calculations are not always ideas..
Spreadsheets are good for analysis of calculated or raw data, But not so well for organization of ideas..
If Field.OnChange could trigger a script or change the style of text in the field, we could use the string processing capabilities of terminal scripts, or do complex calculations using .rb or .pl scripts.
Another thought.
When a user checks the checkboxes in an omnioutliner document used to organize a party or conference, the Field.OnChange triggers a script to send emails to the address entered in one of the fields, writes a log file on the desktop about modifications made in my idea list, and changes the style of text representing the email address in one of the document fields.
The feature request is:
Field.OnChange >> Triggers a terminal script
Returns a value from the script to the field that can be used to
replace the text in the field
change the style of text in the field
write the result to a csv or xml file
Ideas are calculations, but calculations are not always ideas..
Spreadsheets are good for analysis of calculated or raw data, But not so well for organization of ideas..
If Field.OnChange could trigger a script or change the style of text in the field, we could use the string processing capabilities of terminal scripts, or do complex calculations using .rb or .pl scripts.
Another thought.
When a user checks the checkboxes in an omnioutliner document used to organize a party or conference, the Field.OnChange triggers a script to send emails to the address entered in one of the fields, writes a log file on the desktop about modifications made in my idea list, and changes the style of text representing the email address in one of the document fields.
The feature request is:
Field.OnChange >> Triggers a terminal script
Returns a value from the script to the field that can be used to
replace the text in the field
change the style of text in the field
write the result to a csv or xml file