Difference between revisions of "Syntax checking/Visualisation"

 
(→‎Meeting of the 12.05.06, Visualsation Team)
Line 6: Line 6:
 
* most important class
 
* most important class
 
* all the other tokens inherit from this Class
 
* all the other tokens inherit from this Class
−
* implement a boolean “correct”, who indicates if the token is syntacticly correct or not.
+
* implement a boolean "is_correct”, who indicates if the token is syntacticly correct or not.
 
* color, position and other stuff is saved here too.
 
* color, position and other stuff is saved here too.
−
* draw_text_top_left: draws the token on the pixmap (maybe we can start here for drawing the underlines)
 
  
−
editor_token_text.e (stands here as example for all the tokens that inherits from editor_token)
+
editor_token_text.e
−
* inherit editor_token
+
* 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: starts drawing the text. Implement here the boolean “correct” as argument and draw from here the underline.
+
* 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
−
* update lines: draws the textline
+
* 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:12, 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.

Retrieved from "https://dev.eiffel.com/index.php?title=Syntax_checking/Visualisation&oldid=2789"