Difference between revisions of "Syntax checking/Visualisation"
(→Meeting of the 12.05.06, Visualsation Team) |
|||
| Line 3: | Line 3: | ||
Summary of the important classes with little description of the features we plan to use: | Summary of the important classes with little description of the features we plan to use: | ||
| − | Src\library\editor\text_window\text\tokens\common\editor_token.e | + | '''Src\library\editor\text_window\text\tokens\common\editor_token.e''' |
* most important class | * most important class | ||
* all the other tokens inherit from this Class | * all the other tokens inherit from this Class | ||
| Line 9: | Line 9: | ||
* color, position and other stuff is saved here too. | * color, position and other stuff is saved here too. | ||
| − | editor_token_text.e | + | '''editor_token_text.e''' |
* top token class for all text-related tokens | * top token class for all text-related tokens | ||
* width -> the size of the token in pixel | * width -> the size of the token in pixel | ||
* display_with_colors: this should be the feature we could hook to do draw our underlining | * display_with_colors: this should be the feature we could hook to do draw our underlining | ||
| − | Src\library\editor\text_window\editor\text_window\interface\text_panel.e | + | '''Src\library\editor\text_window\editor\text_window\interface\text_panel.e''' |
* container containing tokens | * container containing tokens | ||
'''Next Steps''' are to implement the boolean (shouldn't be that hard), find a way to get the information from the parser group (define an API), use the information and set the boolean and in the end draw the underline. | '''Next Steps''' are to implement the boolean (shouldn't be that hard), find a way to get the information from the parser group (define an API), use the information and set the boolean and in the end draw the underline. | ||
Revision as of 09:25, 12 May 2006
Meeting of the 12.05.06, Visualsation Team
Summary of the important classes with little description of the features we plan to use:
Src\library\editor\text_window\text\tokens\common\editor_token.e
- most important class
- all the other tokens inherit from this Class
- implement a boolean "is_correct”, who indicates if the token is syntacticly correct or not.
- color, position and other stuff is saved here too.
editor_token_text.e
- top token class for all text-related tokens
- width -> the size of the token in pixel
- display_with_colors: this should be the feature we could hook to do draw our underlining
Src\library\editor\text_window\editor\text_window\interface\text_panel.e
- container containing tokens
Next Steps are to implement the boolean (shouldn't be that hard), find a way to get the information from the parser group (define an API), use the information and set the boolean and in the end draw the underline.
