EiffelStudio: an EiffelSoftware project - User contributions [en]

Syntax checking

2006-06-27T20:12:31Z

Jabernet:

[[Category:Projects]]
[[Category:Editor]]
[[Image:Logo_synche.gif|right|frame| SynChé Logo]]
=Overview=

The aim of this project is to provide adequate, but non obtrusive feedback to user about syntax errors. This is done by checking syntax as you type and underlining syntax errors by the well knwon wavy red line. Furthermore, error descriptions and possible solutions should be provided.

The Project is named '''SynChé''', which is a combination of syntax and checking.
The ''é'' at the end is important, as a cool name needs either a recursive acronym or a special character from a non English language.

=Documentation=
[http://n.ethz.ch/student/indermum/download/synche_doc.pdf PDF Synché documentation]

=Software Requirement Specification (SRS)=
You can find our SRS [[Syntax_checking/SRS|here]]

=Groups=

* [[Syntax_checking/Visualisation|Visualisation]]
* [[Syntax_checking/Parser|Parser]]

=Milestones=

==M1: April 25th==
* Get home-grown EiffelStudio up and running.

==M2: May 2nd==
* '''Put your name in this Wiki!'''
* Analyse source code to certain degree, so discussion about interfaces between parser and visual is possible

==M3: May 9th==
* SRS written
* Overview of relevant classes (BON diagram or more)
* Further Project Milestones specified, based on SRS and knowledge about code

== May 12th ==
'''Results of the Meeting:''' [[Syntax_checking/Visualisation| Visualisation]]

== May 17th ==
'''Results of Parser Group:''' [[Syntax_checking/Parser| Parser]]

==M4: May 23rd==
*'''Parser Group''': Find out what results you get from the parser
*'''Visualisation Group''': Write a feature that draw the red underline

==M6: June 27th==
*'''Parser Group''': Multi Error Parser (don't stop parsing after first error encountered)
*'''Visualisation Group''': Draw the mouseover boxes; find how to use stones (especially x,y coordinates -> stones/tokens); collect all parser errors into information window on bottom

=Team=
Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-ui es-ui@origo.ethz.ch].
At this point, the team is divided into two groups at this point, one responsible for the parser, the other one for visual feedback (like underlininig).

== Visual Feedback ==
* [[User:jabernet| Janick Bernet]] (project leader)
* [[User:fdevries| Fabien de Vries]]
* [[User:indermum| Matthias Indermühle]]
* [[User:clerco| Olivier Clerc]]

== Parser ==
* [[User:maser| Martin Luder]]
* [[User:Chrigu| Christoph Huber]]
* [[User:goalgettah| Ueli Etter]]
* [[User:Squeezie| Michael Schär]]
* [[User:MarkoR| Marko Ristin]]

== Assistant ==
* [[User:classens| Stephan Classen]]

Syntax checking/Visualisation

2006-06-03T13:32:56Z

Jabernet:

[[Syntax_checking|back to Syntax checking page]]

== Work distribution for Milestone on June 15. ==
* '''Oli''': find out how to add data to the EV_OUTPUT pane; do a proof of concept
* '''Mätthu''': find out how to draw a popup window; do a proof of concept
* '''Fabi''' & '''Janick''': find out how to go from keyboard x,y to token and from mouse x,y to token (or to keyboard x,y , then to token); add those features to editor

=== Status token from moue/keyboard ===
relevant data in EB_CLICKABLE_EDITOR

== Underlining proof of concept from May 23. ==
[[Image:Ec-proof-of-concept.gif]]
Screenshot of EiffelStudio with every token underlined.

== 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.

TEXT_OBSERVER, EDITABLE_TEXT_PANEL.on_char may be relevant for parser hook too!

[[Image:BON_token_text.png]]

Syntax checking/Visualisation

2006-06-03T07:32:23Z

Jabernet: /* Work distribution for Mileston on June 15. */

[[Syntax_checking|back to Syntax checking page]]

== Work distribution for Mileston on June 15. ==
* '''Oli''': find out how to add data to the EV_OUTPUT pane; do a proof of concept
* '''Mätthu''': find out how to draw a popup window; do a proof of concept
* '''Fabi''' & '''Janick''': find out how to go from keyboard x,y to token and from mouse x,y to token (or to keyboard x,y , then to token); add those features to editor

== Underlining proof of concept from May 23. ==
[[Image:Ec-proof-of-concept.gif]]
Screenshot of EiffelStudio with every token underlined.

== 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.

TEXT_OBSERVER, EDITABLE_TEXT_PANEL.on_char may be relevant for parser hook too!

[[Image:BON_token_text.png]]

Syntax checking/Visualisation

2006-06-03T07:32:04Z

Jabernet:

[[Syntax_checking|back to Syntax checking page]]

== Work distribution for Mileston on June 15. ==
* Oli: find out how to add data to the EV_OUTPUT pane; do a proof of concept
* Mätthu: find out how to draw a popup window; do a proof of concept
* Fabi & Jäne: find out how to go from keyboard x,y to token and from mouse x,y to token (or to keyboard x,y , then to token); add those features to editor

== Underlining proof of concept from May 23. ==
[[Image:Ec-proof-of-concept.gif]]
Screenshot of EiffelStudio with every token underlined.

== 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.

TEXT_OBSERVER, EDITABLE_TEXT_PANEL.on_char may be relevant for parser hook too!

[[Image:BON_token_text.png]]

Syntax checking

2006-06-03T07:28:27Z

Jabernet: /* M6: June 6th */

[[Category:Projects]]
[[Category:Editor]]
=Overview=
The aim of this project is to provide adequate, but non intrusive feedback to user about syntax errors. This is done by checking syntax as you type and underlining syntax errors by the well knwon wavy red line. Furthermore, error descriptions and possible solutions should be provided.

The Project is named '''SynChé''', which is a combination of syntax and checking.
The ''é'' at the end is important, as a cool name needs either a recursive acronym or a special character from a non English language.

=Software Requirement Specification (SRS)=
You can find our SRS [[Syntax_checking/SRS|here]]

=Groups=

* [[Syntax_checking/Visualisation|Visualisation]]
* [[Syntax_checking/Parser|Parser]]

=Milestones=

==M1: April 25th==
* Get home-grown EiffelStudio up and running.

==M2: May 2nd==
* '''Put your name in this Wiki!'''
* Analyse source code to certain degree, so discussion about interfaces between parser and visual is possible

==M3: May 9th==
* SRS written
* Overview of relevant classes (BON diagram or more)
* Further Project Milestones specified, based on SRS and knowledge about code

== May 12th ==
'''Results of the Meeting:''' [[Syntax_checking/Visualisation| Visualisation]]

== May 17th ==
'''Results of Parser Group:''' [[Syntax_checking/Parser| Parser]]

==M4: May 23th==
*'''Parser Group''': Find out what results you get from the parser
*'''Visualisation Group''': Write a feature that draw the red underline

==M6: June 15th==
*'''Parser Group''': Multi Error Parser (don't stop parsing after first error encountered)
*'''Visualisation Group''': Draw the mouseover boxes; find how to use stones (especially x,y coordinates -> stones/tokens); collect all parser errors into information window on bottom

=Team=
Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-ui es-ui@origo.ethz.ch].
At this point, the team is divided into two groups at this point, one responsible for the parser, the other one for visual feedback (like underlininig).

== Visual Feedback ==
* [[User:jabernet| Janick Bernet]] (project leader)
* [[User:fdevries| Fabien de Vries]]
* [[User:indermum| Matthias Indermühle]]
* [[User:clerco| Olivier Clerc]]

== Parser ==
* [[User:maser| Martin Luder]]
* [[User:Chrigu| Christoph Huber]]
* [[User:goalgettah| Ueli Etter]]
* [[User:Squeezie| Michael Schär]]
* [[User:MarkoR| Marko Ristin]]

== Assistant ==
* [[User:classens| Stephan Classen]]

Syntax checking

2006-05-30T12:29:17Z

Jabernet:

[[Category:Projects]]
[[Category:Editor]]
=Overview=
The aim of this project is to provide adequate, but non intrusive feedback to user about syntax errors. This is done by checking syntax as you type and underlining syntax errors by the well knwon wavy red line. Furthermore, error descriptions and possible solutions should be provided.

The Project is named '''SynChé''', which is a combination of syntax and checking.
The ''é'' at the end is important, as a cool name needs either a recursive acronym or a special character from a non English language.

=Software Requirement Specification (SRS)=
You can find our SRS [[Syntax_checking/SRS|here]]

=Groups=

* [[Syntax_checking/Visualisation|Visualisation]]
* [[Syntax_checking/Parser|Parser]]

=Milestones=

==M1: April 25th==
* Get home-grown EiffelStudio up and running.

==M2: May 2nd==
* '''Put your name in this Wiki!'''
* Analyse source code to certain degree, so discussion about interfaces between parser and visual is possible

==M3: May 9th==
* SRS written
* Overview of relevant classes (BON diagram or more)
* Further Project Milestones specified, based on SRS and knowledge about code

== May 12th ==
'''Results of the Meeting:''' [[Syntax_checking/Visualisation| Visualisation]]

== May 17th ==
'''Results of Parser Group:''' [[Syntax_checking/Parser| Parser]]

==M4: May 23th==
*'''Parser Group''': Find out what results you get from the parser
*'''Visualisation Group''': Write a feature that draw the red underline

==M6: June 6th==
*'''Parser Group''': Multi Error Parser (don't stop parsing after first error encountered)
*'''Visualisation Group''': Draw the mouseover boxes; find how to use stones (especially x,y coordinates -> stones/tokens); collect all parser errors into information window on bottom

=Team=
Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-ui es-ui@origo.ethz.ch].
At this point, the team is divided into two groups at this point, one responsible for the parser, the other one for visual feedback (like underlininig).

== Visual Feedback ==
* [[User:jabernet| Janick Bernet]] (project leader)
* [[User:fdevries| Fabien de Vries]]
* [[User:indermum| Matthias Indermühle]]
* [[User:clerco| Olivier Clerc]]

== Parser ==
* [[User:maser| Martin Luder]]
* [[User:Chrigu| Christoph Huber]]
* [[User:goalgettah| Ueli Etter]]
* [[User:Squeezie| Michael Schär]]
* [[User:MarkoR| Marko Ristin]]

== Assistant ==
* [[User:classens| Stephan Classen]]

Syntax checking/Visualisation

2006-05-24T08:09:48Z

Jabernet:

[[Syntax_checking|back to Syntax checking page]]

== Proof of concept from May 23. ==
[[Image:Ec-proof-of-concept.gif]]
Screenshot of EiffelStudio with every token underlined.

== 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.

TEXT_OBSERVER, EDITABLE_TEXT_PANEL.on_char may be relevant for parser hook too!

[[Image:BON_token_text.png]]

Syntax checking/SRS

2006-05-23T01:15:41Z

Jabernet: /* Interface */

[[Syntax_checking|back to Syntax checking page]]

= Goal =
Provide adequate, but non intrusive feedback to user about syntax errors.

= Parser =
# Should only parse when neccessary:
## When editing a new or correct expression:
### After typing a point, comma, colon, semi-colon, space, tab or line-break
### After leaving the edited expression (using cursor or mouse)
## When editing a incorrect expression:
### After each added character
# Provide errors in adequate datastructure to visualisation components (replaced by is_correct attribute on token)
##linenumber
##type of error
##further information
# Whenever the visualisation of an expression should change, the parser should call an event handler provided by visualization components

'''Note:'''
* A new expression is correct until it becomes incorrect.
* The state of an expression can only be changed when the cursor leaves it.

= Parser-to-Visualization-Interface =
# The parser invalidates a TOKEN, by settings its attribute is_correct to false
# The parser can also set TOKEN's error_description attribute to the specific error (or error_type if we don't get description)
# An additional data-structure has to be maintained, to pass error summary information to visualization

= Visualization =
# Highlighting happens only in code editing view
# Visualization component should maintain information on line states (underlined y/n)
# Underline syntax errors using a (preferably wavy) red line
# On mouse over, show information on error
# Information window could be clickable to provide further error information
# Errors should be accessible over summarization

= 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

Syntax checking/Visualisation

2006-05-23T01:08:38Z

Jabernet:

[[Syntax_checking|back to Syntax checking page]]

== Proof of concept from May 23. ==
[[Image:Ec-proof-of-concept.gif]]

== 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.

TEXT_OBSERVER, EDITABLE_TEXT_PANEL.on_char may be relevant for parser hook too!

[[Image:BON_token_text.png]]

Syntax checking/Visualisation

2006-05-23T01:08:24Z

Jabernet:

[[Syntax_checking|back to Syntax checking page]]

== Proof of concept from May 23. ==
[[Image:Ec-proof-of-concept.gif]

== 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.

TEXT_OBSERVER, EDITABLE_TEXT_PANEL.on_char may be relevant for parser hook too!

[[Image:BON_token_text.png]]

File:Ec-proof-of-concept.gif

2006-05-23T01:07:03Z

Jabernet: Proof of concept Eiffelstudio with wavy red lines.

Proof of concept Eiffelstudio with wavy red lines.

Syntax checking/SRS

2006-05-20T16:31:40Z

Jabernet:

[[Syntax_checking|back to Syntax checking page]]

= Goal =
Provide adequate, but non intrusive feedback to user about syntax errors.

= Parser =
# Should only parse when neccessary:
## When editing a new or correct expression:
### After typing a point, comma, colon, semi-colon, space, tab or line-break
### After leaving the edited expression (using cursor or mouse)
## When editing a incorrect expression:
### After each added character
# Provide errors in adequate datastructure to visualisation components (replaced by is_correct attribute on token)
##linenumber
##type of error
##further information
# Whenever the visualisation of an expression should change, the parser should call an event handler provided by visualization components

'''Note:'''
* A new expression is correct until it becomes incorrect.
* The state of an expression can only be changed when the cursor leaves it.

= Interface =
# The parser invalidates a TOKEN, by settings its attribute is_correct to false
# The parser can also set TOKEN's error_description attribute to the specific error (or error_type if we don't get description)
# An additional data-structure has to be maintained, to pass error summary information to visualization

= Visualization =
# Highlighting happens only in code editing view
# Visualization component should maintain information on line states (underlined y/n)
# Underline syntax errors using a (preferably wavy) red line
# On mouse over, show information on error
# Information window could be clickable to provide further error information
# Errors should be accessible over summarization

= 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

Syntax checking/SRS

2006-05-20T16:26:43Z

Jabernet: /* Visualization */

[[Syntax_checking|back to Syntax checking page]]

= Goal =
Provide adequate, but non intrusive feedback to user about syntax errors.

= Parser =
# Should only parse when neccessary:
## When editing a new or correct expression:
### After typing a point, comma, colon, semi-colon, space, tab or line-break
### After leaving the edited expression (using cursor or mouse)
## When editing a incorrect expression:
### After each added character
# Provide errors in adequate datastructure to visualisation components
##linenumber
##type of error
##further information
# Whenever the visualisation of an expression should change, the parser should call an event handler provided by visualization components

'''Note:'''
* A new expression is correct until it becomes incorrect.
* The state of an expression can only be changed when the cursor leaves it.

= Visualization =
# Highlighting happens only in code editing view
# Visualization component should maintain information on line states (underlined y/n)
# Underline syntax errors using a (preferably wavy) red line
# On mouse over, show information on error
# Information window could be clickable to provide further error information
# Errors should be accessible over summarization

= 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

User:Jabernet

2006-05-17T09:20:02Z

Jabernet: /* Janick Bernet */

=Janick Bernet=

Student ETH Zurich, currently working on SynChé project.

Kontakt:
jabernet ät student...
079 400 04 59
MSN: inflagranti82@hotmail.com
ICQ: 32896520

Syntax checking/SRS

2006-05-17T09:18:50Z

Jabernet:

[[Syntax_checking|back to Syntax checking page]]

= Goal =
Provide adequate, but non intrusive feedback to user about syntax errors.

= Parser =
# Should only parse when neccessary:
## When editing a new or correct expression:
### After typing a point, comma, colon, semi-colon, space, tab or line-break
### After leaving the edited expression (using cursor or mouse)
## When editing a incorrect expression:
### After each added character
# Provide errors in adequate datastructure to visualisation components
##linenumber
##type of error
##further information
# Whenever the visualisation of an expression should change, the parser should call an event handler provided by visualization components

'''Note:'''
* A new expression is correct until it becomes incorrect.
* The state of an expression can only be changed when the cursor leaves it.

= Visualization =
# Highlighting happens only in code editing view
# Provides event handler and registers it to parser error-event
# Visualization component should maintain information on line states (underlined y/n)
# Underline syntax errors using a (preferably wavy) red line
# On mouse over, show information on error
# Information window could be clickable to provide further error information
# Errors should be accessible over summarization

= 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

Syntax checking/Visualisation

2006-05-17T09:18:39Z

Jabernet:

[[Syntax_checking|back to Syntax checking page]]

== 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.

TEXT_OBSERVER, EDITABLE_TEXT_PANEL.on_char may be relevant for parser hook too!

[[Image:BON_token_text.png]]

Syntax checking

2006-05-17T09:18:12Z

Jabernet:

[[Category:Projects]]
[[Category:Editor]]
=Overview=
The aim of this project is to provide adequate, but non intrusive feedback to user about syntax errors. This is done by checking syntax as you type and underlining syntax errors by the well knwon wavy red line. Furthermore, error descriptions and possible solutions should be provided.

The Project is named '''SynChé''', which is a combination of syntax and checking.
The ''é'' at the end is important, as a cool name needs either a recursive acronym or a special character from a non English language.

=Software Requirement Specification (SRS)=
You can find our SRS [[Syntax_checking/SRS|here]]

=Groups=

* [[Syntax_checking/Visualisation|Visualisation]]
* [[Syntax_checking/Parser|Parser]]

=Milestones=

==M1: April 25th==
* Get home-grown EiffelStudio up and running.

==M2: May 2nd==
* '''Put your name in this Wiki!'''
* Analyse source code to certain degree, so discussion about interfaces between parser and visual is possible

==M3: May 9th==
* SRS written
* Overview of relevant classes (BON diagram or more)
* Further Project Milestones specified, based on SRS and knowledge about code

== May 12th ==
'''Results of the Meeting:''' [[Syntax_checking/Visualisation| Visualisation]]

==M4: May 23th==
*'''Parser Group''': Find out what results you get from the parser
*'''Visualisation Group''': Write a feature that draw the red underline

=Team=
Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-ui es-ui@origo.ethz.ch].
At this point, the team is divided into two groups at this point, one responsible for the parser, the other one for visual feedback (like underlininig).

== Visual Feedback ==
* [[User:jabernet| Janick Bernet]] (project leader)
* [[User:fdevries| Fabien de Vries]]
* [[User:indermum| Matthias Indermühle]]
* [[User:clerco| Olivier Clerc]]

== Parser ==
* [[User:maser| Martin Luder]]
* [[User:Chrigu| Christoph Huber]]
* [[User:goalgettah| Ueli Etter]]
* [[User:Squeezie| Michael Schär]]
* [[User:MarkoR| Marko Ristin]]

== Assistant ==
* [[User:classens| Stephan Classen]]

Syntax checking

2006-05-17T09:18:05Z

Jabernet:

[[Category:Projects]]
[[Category:Editor]]

=Overview=
The aim of this project is to provide adequate, but non intrusive feedback to user about syntax errors. This is done by checking syntax as you type and underlining syntax errors by the well knwon wavy red line. Furthermore, error descriptions and possible solutions should be provided.

The Project is named '''SynChé''', which is a combination of syntax and checking.
The ''é'' at the end is important, as a cool name needs either a recursive acronym or a special character from a non English language.

=Software Requirement Specification (SRS)=
You can find our SRS [[Syntax_checking/SRS|here]]

=Groups=

* [[Syntax_checking/Visualisation|Visualisation]]
* [[Syntax_checking/Parser|Parser]]

=Milestones=

==M1: April 25th==
* Get home-grown EiffelStudio up and running.

==M2: May 2nd==
* '''Put your name in this Wiki!'''
* Analyse source code to certain degree, so discussion about interfaces between parser and visual is possible

==M3: May 9th==
* SRS written
* Overview of relevant classes (BON diagram or more)
* Further Project Milestones specified, based on SRS and knowledge about code

== May 12th ==
'''Results of the Meeting:''' [[Syntax_checking/Visualisation| Visualisation]]

==M4: May 23th==
*'''Parser Group''': Find out what results you get from the parser
*'''Visualisation Group''': Write a feature that draw the red underline

=Team=
Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-ui es-ui@origo.ethz.ch].
At this point, the team is divided into two groups at this point, one responsible for the parser, the other one for visual feedback (like underlininig).

== Visual Feedback ==
* [[User:jabernet| Janick Bernet]] (project leader)
* [[User:fdevries| Fabien de Vries]]
* [[User:indermum| Matthias Indermühle]]
* [[User:clerco| Olivier Clerc]]

== Parser ==
* [[User:maser| Martin Luder]]
* [[User:Chrigu| Christoph Huber]]
* [[User:goalgettah| Ueli Etter]]
* [[User:Squeezie| Michael Schär]]
* [[User:MarkoR| Marko Ristin]]

== Assistant ==
* [[User:classens| Stephan Classen]]

Syntax checking/Parser

2006-05-17T09:17:50Z

Jabernet:

[[Syntax_checking|back to Syntax checking page]]

==Important Classes==

====EIFFEL_PARSER====
* has a feature parse(file)
====CLASS_AS====
* AST of a class
====ERROR====
* deferred; superclass of all error types like EIFFEL_ERROR or SYNTAX_ERROR
* features line, column: INTEGER give location of error
====ERROR_HANDLER====
* feature error_list: ERROR is a list of errors found by the parser
====SHARED_ERROR_HANDLER====
* singleton used by all relevant classes

====EIFFEL_CLASS_C====
* features build_ast and parse_ast show how the parser can be used.

User:Jabernet

2006-05-17T09:16:42Z

Jabernet: /* Janick Bernet */

=Janick Bernet=

Student ETH Zurich, currently working on SynChé project.

Kontakt:
jabernet ät student...
079 400 04 59

User:Jabernet

2006-05-17T09:16:35Z

Jabernet: /* Janick Bernet */

=Janick Bernet=

Student ETH Zurich, currently working on SynChé project.

Kontakt:
jabernet ät student...
079 400 04 59

User:Jabernet

2006-05-17T09:16:25Z

Jabernet: /* Janick Bernet */

=Janick Bernet=

Student ETH Zurich, currently working on SynChé project.

Kontakt:

jabernet ät student...

079 400 04 59

User:Jabernet

2006-05-17T09:16:17Z

Jabernet: /* Janick Bernet */

=Janick Bernet=

Student ETH Zurich, currently working on SynChé project.

Kontakt:
jabernet ät student...
079 400 04 59

Syntax checking/Visualisation

2006-05-12T18:59:43Z

Jabernet:

== 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.

TEXT_OBSERVER, EDITABLE_TEXT_PANEL.on_char may be relevant for parser hook too!

[[Image:BON_token_text.png]]

File:BON token text.png

2006-05-12T18:59:22Z

Jabernet: BON diagram of important token classes

BON diagram of important token classes

Syntax checking/Visualisation

2006-05-12T18:58:52Z

Jabernet:

Syntax checking/Visualisation

2006-05-12T18:58:31Z

Jabernet:

Syntax checking/Visualisation

2006-05-12T18:46:01Z

Jabernet:

Syntax checking/Visualisation

2006-05-12T18:44:16Z

Jabernet:

Syntax checking/Visualisation

2006-05-12T18:25:53Z

Jabernet:

Syntax checking

2006-05-12T18:23:52Z

Jabernet: /* M3: May 9th */

[[Category:Projects]]
[[Category:Editor]]

=Overview=
The aim of this project is to provide adequate, but non intrusive feedback to user about syntax errors. This is done by checking syntax as you type and underlining syntax errors by the well knwon wavy red line. Furthermore, error descriptions and possible solutions should be provided.

The Project is named '''SynChé''', which is a combination of syntax and checking.
The ''é'' at the end is important, as a cool name needs either a recursive acronym or a special character from a non English language.

=Software Requirement Specification (SRS)=
You can find our SRS [[Syntax_checking/SRS|here]]

=Milestones=

==M1: April 25th==
* Get home-grown EiffelStudio up and running.

==M2: May 2nd==
* '''Put your name in this Wiki!'''
* Analyse source code to certain degree, so discussion about interfaces between parser and visual is possible

==M3: May 9th==
* SRS written
* Overview of relevant classes (BON diagram or more)
* Further Project Milestones specified, based on SRS and knowledge about code

== May 12th ==
'''Results of the Meeting:''' [[Syntax_checking/Visualisation| Visualisation]]

=Team=
Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-ui es-ui@origo.ethz.ch].
At this point, the team is divided into two groups at this point, one responsible for the parser, the other one for visual feedback (like underlininig).

== Visual Feedback ==
* [[User:jabernet| Janick Bernet]] (project leader)
* [[User:fdevries| Fabien de Vries]]
* [[User:indermum| Matthias Indermühle]]
* [[User:clerco| Olivier Clerc]]

== Parser ==
* [[User:maser| Martin Luder]]
* [[User:Chrigu| Christoph Huber]]
* [[User:goalgettah| Ueli Etter]]
* [[User:Squeezie| Michael Schär]]
* [[User:MarkoR| Marko Ristin]]

== Assistant ==
* [[User:classens| Stephan Classen]]

Syntax checking/Visualisation

2006-05-12T18:12:35Z

Jabernet: /* Meeting of the 12.05.06, Visualsation Team */

== 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.

Talk:Syntax checking/SRS

2006-05-06T00:08:12Z

Jabernet:

== Janick ==
Please give some feedback regarding SRS so far

==Manus==
It is great. For the syntax validity, create an instance of EIFFEL_PARSER with the AST_NULL_FACTORY for the factory. That way it is quite efficient for the parsing.

[[User:Manus|manus]] 19:03, 2 May 2006 (CEST)

==Janick==
Manu, thanks for the feedback and hints.

Some people thaught that an timing-based parser would be better. Who is of the same opionion? Please use this discussion, as we need to finalize the specifications soon.

May 5th 2006 (CEST)

== Martin ==

What exactly do you mean by timing-based? As specified in the SRS but with a timeout before it starts parsing or really independent of user input? I think it's good the way it is now (if it is efficient enough). Just a little remark to the notes: If the state of an expression can only change when the cursor leaves it, does that include the items under 1.1.1? I think it should, although I guess you should get a little time to resume typing.

[[User:Maser|Maser]] 23:57, 5 May 2006 (CEST)

==Janick==
Timing based would mean that the document gets parsed and highlighted in specific intervals (like every 50ms). This would also imply that while writing not yet completed feature names etc. would get underlined.

Stephan added that "when the cursor" leaves part, so he should answer that question. IMO if we have event-based parsing, that coursor leaves clause could be removed.

01:59, May 6th 2006 (CEST)

Talk:Syntax checking/SRS

2006-05-05T21:30:50Z

Jabernet:

Talk:Syntax checking/SRS

2006-05-05T21:30:39Z

Jabernet:

Talk:Syntax checking/SRS

2006-05-05T21:30:27Z

Jabernet:

Please give some feedback regarding SRS so far

==Manus==
It is great. For the syntax validity, create an instance of EIFFEL_PARSER with the AST_NULL_FACTORY for the factory. That way it is quite efficient for the parsing.

[[User:Manus|manus]] 19:03, 2 May 2006 (CEST)

Manu, thanks for the feedback and hints.

==Janick==
Some people thaught that an timing-based parser would be better. Who is of the same opionion? Please use this discussion, as we need to finalize the specifications soon.

May 5th 2006 (CEST)

Talk:Syntax checking/SRS

2006-05-05T21:30:16Z

Jabernet: /* Manus */

Talk:Syntax checking/SRS

2006-05-05T21:29:59Z

Jabernet: /* Manus */

Please give some feedback regarding SRS so far

==Manus==
It is great. For the syntax validity, create an instance of EIFFEL_PARSER with the AST_NULL_FACTORY for the factory. That way it is quite efficient for the parsing.

[[User:Manus|manus]] 19:03, 2 May 2006 (CEST)

Manu, thanks for the feedback and hints.

Some people thaught that an timing-based parser would be better. Who is of the same opionion? Please use this discussion, as we need to finalize the specifications soon.

[[User:jabernet|Janick]] May 5th 2006 (CEST)

Talk:Syntax checking/SRS

2006-05-05T21:29:23Z

Jabernet:

Please give some feedback regarding SRS so far

==Manus==
It is great. For the syntax validity, create an instance of EIFFEL_PARSER with the AST_NULL_FACTORY for the factory. That way it is quite efficient for the parsing.

[[User:Manus|manus]] 19:03, 2 May 2006 (CEST)

Manu, thanks for the feedback and hints.

Some people thaught that an timing-based parser would be better. Who is of the same opionion? Please use this discussion, as we need to finalize the specifications soon.

Syntax checking

2006-05-04T15:20:13Z

Jabernet: /* Software Requirement Specification (SaRS) */

Talk:Syntax checking/SRS

2006-05-02T15:59:56Z

Jabernet:

Please give some feedback regarding SRS so far

Syntax checking/SRS

2006-05-02T15:58:33Z

Jabernet:

= 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

Syntax checking

2006-05-02T15:56:34Z

Jabernet:

[[Category:Projects]]
[[Category:Editor]]

=Overview=
The aim of this project is to provide adequate, but non intrusive feedback to user about syntax errors. This is done by checking syntax as you type and underlining syntax errors by the well knwon wavy red line. Furthermore, error descriptions and possible solutions should be provided.

The Project is named '''SynChé''', which is a combination of syntax and checking.
The ''é'' at the end is important, as a cool name needs either a recursive acronym or a special character from a non English language.

=Software Requirement Specification (SaRS)=
you can find our SaRS [[Syntax_checking/SRS|here]] (comming soon)

=Milestones=

==M1: April 25th==
* Get home-grown EiffelStudio up and running.

==M2: May 2nd==
* '''Put your name in this Wiki!'''
* Analyse source code to certain degree, so discussion about interfaces between parser and visual is possible

==M3: May 9th==
* SRS written
* Overview of relevant classes (BON diagram or more)
* Further Project Milestones specified, based on SRS and knowledge about code

=Team=
Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-ui es-ui@origo.ethz.ch].
At this point, the team is divided into two groups at this point, one responsible for the parser, the other one for visual feedback (like underlininig).

== Visual Feedback ==
* [[User:jabernet| Janick Bernet]] (project leader)
* [[User:fdevries| Fabien de Vries]]
* [[User:indermum| Matthias Indermühle]]
* [[User:clerco| Olivier Clerc]]

== Parser ==
* [[User:maser| Martin Luder]]
* [[User:chrhuber| Christoph Huber]]
* [[User:goalgettah| Ueli Etter]]
* [[User:Squeezie| Michael Schär]]

== Assistant ==
* [[User:classens| Stephan Classen]]

Syntax checking/SRS

2006-05-02T15:53:08Z

Jabernet:

Syntax checking/SRS

2006-05-02T15:52:31Z

Jabernet:

= 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

Syntax checking/SRS

2006-05-02T15:52:20Z

Jabernet:

= 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

Syntax checking/SRS

2006-05-02T15:52:04Z

Jabernet:

= 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

Syntax checking/SRS

2006-05-02T15:45:26Z

Jabernet:

Syntax checking/SRS

2006-05-02T15:41:57Z

Jabernet:

= # Goal =
Provide adequate, but non intrusive feedback to user about syntax errors.

=

Syntax checking/SRS

2006-05-02T15:41:48Z

Jabernet:

#= Goal =
Provide adequate, but non intrusive feedback to user about syntax errors.

=