Syntax checking/SRS: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
# On mouse over, show information on error | # On mouse over, show information on error | ||
# Information window could be clickabel to provide further error information | # Information window could be clickabel to provide further error information | ||
= Suggestions = | |||
# To be implemented after parser and visualization components are feature complete | |||
# Suggestions based on information from parse tree | |||
# Analyzation based on soundex or other algorithm | |||
Revision as of 15:58, 2 May 2006
Goal
Provide adequate, but non intrusive feedback to user about syntax errors.
Parser
- Should only parse when neccessary, using timer function or after certain input (like spaces, enter) (to be further specified )
- Provide errors in adequate datastructure to visualisation components (linenumber, type of error, further information)
- On error, parser should call event handler provided by visualization components
Visualization
- Provides event handler and register it to parser error-event
- Underline syntax errors using a (preferably wavy) red line
- On mouse over, show information on error
- Information window could be clickabel to provide further error information
Suggestions
- To be implemented after parser and visualization components are feature complete
- Suggestions based on information from parse tree
- Analyzation based on soundex or other algorithm