EiffelStudio: an EiffelSoftware project - User contributions [en]

Syntax checking

2006-06-26T15:32:03Z

Indermum:

[[Category:Projects]]
[[Category:Editor]]
[[Image:Logo_synche.gif|right|frame| SynChé Logo]]
=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.

=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

2006-06-26T13:01:16Z

Indermum:

[[Category:Projects]]
[[Category:Editor]]
[[Image:Logo_synche.gif|right|frame| SynChé Logo]]
=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 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

2006-06-26T11:29:17Z

Indermum:

[[Category:Projects]]
[[Category:Editor]]
=Overview=
[[Image:Logo_synche.gif]]

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 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]]

File:Logo synche.gif

2006-06-26T11:27:25Z

Indermum: Logo of SynChé

Logo of SynChé

Syntax checking

2006-05-30T12:01:01Z

Indermum:

[[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
*'''Visualisation Group''': Draw the mouseover boxes, find how to use stones

=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-30T11:47:59Z

Indermum:

[[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''': Define the things that the parser can return
*'''Visualisation Group''': Draw the mouseover boxes, find how to use stones

=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-24T10:06:25Z

Indermum:

[[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

=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:Squeezie| Michael Schär]]
* [[User:MarkoR| Marko Ristin]]

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

Syntax checking

2006-05-16T12:09:01Z

Indermum:

[[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]]

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

Talk:Syntax checking

2006-05-16T10:06:33Z

Indermum:

Wir sollten irgendwo noch den Namen "SynChé" erwähnen.
engl: we should mentions smowherer the name "SynChé"

'''[[User:FoB|FoB]] 12:52, 20 April 2006 (CEST)'''

'''yes you should!!''' it is your task and duty to fill in more information into this page. you should have a SRS and an introductiory text, and you should also post updates and a TODO list and other interesting stuff here. remember, thsi is not just your project. this is an open source project and everybody can participate. but you only will get help from the comunity if you provide informations on what, why and how you do things.

oh and by the way: '''stick to english'''

== Meeting 11.5.06 ==

Both of the Groups have a Meeting at 4 pm. in the bQm. There we plan our next steps and share informations

'''Group Parser'''
No one of us could compile the Eiffel Studio yet. We will study the code and make a page in this Wiki, in which we describe each class that is useful for our project. And then, we should talking about the interface with the other group.
(Someone of our Group knew, where you can read the Eiffel Studio source code online. Please post the link here. That would be very useful.)

Here is your link [https://eiffelsoftware.origo.ethz.ch/svn/es/ Eiffel Source]

[[User:Indermum|Indermum]] 13:38, 12 May 2006 (CEST) '''Group Visualisation'''

We still have problems to compile Eiffel Studio too. We made a little summary about the classes we need to use under [[Syntax_checking/Visualisation]]

Ah and one other thing. could '''everybody''' pleas insert in his page his e-mail adress and his cell phone number for faster communication and if aviable the msn or icq adress. thx

User:Indermum

2006-05-14T16:03:04Z

Indermum:

==Matthias Indermühle==

4. semester student in D-INFK at the ETH Zurich

indermum_at_student.ethz.ch

078 674 93 85

MSN: snowworldpictures@hotmail.com

[http://www.snowworldpictures.ch.vu www.snowworldpictures.ch.vu]

==Work==
project in software arcitecture
[[Syntax_checking]]

Talk:Syntax checking

2006-05-12T11:43:44Z

Indermum:

Wir sollten irgendwo noch den Namen "SynChé" erwähnen.
engl: we should mentions smowherer the name "SynChé"

'''[[User:FoB|FoB]] 12:52, 20 April 2006 (CEST)'''

'''yes you should!!''' it is your task and duty to fill in more information into this page. you should have a SRS and an introductiory text, and you should also post updates and a TODO list and other interesting stuff here. remember, thsi is not just your project. this is an open source project and everybody can participate. but you only will get help from the comunity if you provide informations on what, why and how you do things.

oh and by the way: '''stick to english'''

== Meeting 11.5.06 ==

Both of the Groups have a Meeting at 4 pm. in the bQm. There we plan our next steps and share informations

'''Group Parser'''
No one of us could compile the Eiffel Studio yet. We will study the code and make a page in this Wiki, in which we describe each class that is useful for our project. And then, we should talking about the interface with the other group.

[[User:Indermum|Indermum]] 13:38, 12 May 2006 (CEST) '''Group Visualisation'''

We still have problems to compile Eiffel Studio too. We made a little summary about the classes we need to use under [[Syntax_checking/Visualisation]]

Ah and one other thing. could everybody pleas insert in his page his e-mail adress and his cell phone number for faster communication and if aviable the msn or icq adress. thx

User:Indermum

2006-05-12T11:41:37Z

Indermum:

==Matthias Indermühle==

4. semester student in D-INFK at the ETH Zurich

indermum_at_student.ethz.ch
078 674 93 85

[http://www.snowworldpictures.ch.vu www.snowworldpictures.ch.vu]

==Work==
project in software arcitecture
[[Syntax_checking]]

Talk:Syntax checking

2006-05-12T11:38:59Z

Indermum:

Wir sollten irgendwo noch den Namen "SynChé" erwähnen.
engl: we should mentions smowherer the name "SynChé"

'''[[User:FoB|FoB]] 12:52, 20 April 2006 (CEST)'''

'''yes you should!!''' it is your task and duty to fill in more information into this page. you should have a SRS and an introductiory text, and you should also post updates and a TODO list and other interesting stuff here. remember, thsi is not just your project. this is an open source project and everybody can participate. but you only will get help from the comunity if you provide informations on what, why and how you do things.

oh and by the way: '''stick to english'''

== Meeting 11.5.06 ==

Both of the Groups have a Meeting at 4 pm. in the bQm. There we plan our next steps and share informations

'''Group Parser'''
No one of us could compile the Eiffel Studio yet. We will study the code and make a page in this Wiki, in which we describe each class that is useful for our project. And then, we should talking about the interface with the other group.

[[User:Indermum|Indermum]] 13:38, 12 May 2006 (CEST) '''Group Visualisation'''

We still have problems to compile Eiffel Studio too. We made a little summary about the classes we need to use under [[Syntax_checking/Visualisation]]

Talk:Syntax checking

2006-05-12T11:38:46Z

Indermum:

Wir sollten irgendwo noch den Namen "SynChé" erwähnen.
engl: we should mentions smowherer the name "SynChé"

'''[[User:FoB|FoB]] 12:52, 20 April 2006 (CEST)'''

'''yes you should!!''' it is your task and duty to fill in more information into this page. you should have a SRS and an introductiory text, and you should also post updates and a TODO list and other interesting stuff here. remember, thsi is not just your project. this is an open source project and everybody can participate. but you only will get help from the comunity if you provide informations on what, why and how you do things.

oh and by the way: '''stick to english'''

== Meeting 11.5.06 ==

Both of the Groups have a Meeting at 4 pm. in the bQm. There we plan our next steps and share informations

'''Group Parser'''
No one of us could compile the Eiffel Studio yet. We will study the code and make a page in this Wiki, in which we describe each class that is useful for our project. And then, we should talking about the interface with the other group.

--[[User:Indermum|Indermum]] 13:38, 12 May 2006 (CEST)'''Group Visualisation'''

We still have problems to compile Eiffel Studio too. We made a little summary about the classes we need to use under [[Syntax_checking/Visualisation]]

Talk:Syntax checking

2006-05-12T11:38:20Z

Indermum:

Wir sollten irgendwo noch den Namen "SynChé" erwähnen.
engl: we should mentions smowherer the name "SynChé"

'''[[User:FoB|FoB]] 12:52, 20 April 2006 (CEST)'''

'''yes you should!!''' it is your task and duty to fill in more information into this page. you should have a SRS and an introductiory text, and you should also post updates and a TODO list and other interesting stuff here. remember, thsi is not just your project. this is an open source project and everybody can participate. but you only will get help from the comunity if you provide informations on what, why and how you do things.

oh and by the way: '''stick to english'''

== Meeting 11.5.06 ==

Both of the Groups have a Meeting at 4 pm. in the bQm. There we plan our next steps and share informations

'''Group Parser'''
No one of us could compile the Eiffel Studio yet. We will study the code and make a page in this Wiki, in which we describe each class that is useful for our project. And then, we should talking about the interface with the other group.

'''Group Visualisation'''

We still have problems to compile Eiffel Studio too. We made a little summary about the classes we need to use under [[Syntax_checking/Visualisation]]

Talk:Syntax checking

2006-05-12T11:37:58Z

Indermum:

Wir sollten irgendwo noch den Namen "SynChé" erwähnen.
engl: we should mentions smowherer the name "SynChé"

'''[[User:FoB|FoB]] 12:52, 20 April 2006 (CEST)'''

'''yes you should!!''' it is your task and duty to fill in more information into this page. you should have a SRS and an introductiory text, and you should also post updates and a TODO list and other interesting stuff here. remember, thsi is not just your project. this is an open source project and everybody can participate. but you only will get help from the comunity if you provide informations on what, why and how you do things.

oh and by the way: '''stick to english'''

== Meeting 11.5.06 ==

Both of the Groups have a Meeting at 4 pm. in the bQm. There we plan our next steps and share informations

'''Group Parser'''
No one of us could compile the Eiffel Studio yet. We will study the code and make a page in this Wiki, in which we describe each class that is useful for our project. And then, we should talking about the interface with the other group.
'''Group Visualisation'''
We still have problems to compile Eiffel Studio too. We made a little summary about the classes we need to use under [[Syntax_checking/Visualisation]]

Talk:Syntax checking

2006-05-12T11:36:58Z

Indermum:

Wir sollten irgendwo noch den Namen "SynChé" erwähnen.
engl: we should mentions smowherer the name "SynChé"

'''[[User:FoB|FoB]] 12:52, 20 April 2006 (CEST)'''

'''yes you should!!''' it is your task and duty to fill in more information into this page. you should have a SRS and an introductiory text, and you should also post updates and a TODO list and other interesting stuff here. remember, thsi is not just your project. this is an open source project and everybody can participate. but you only will get help from the comunity if you provide informations on what, why and how you do things.

oh and by the way: '''stick to english'''

== Meeting 11.5.06 ==

Both of the Groups have a Meeting at 4 pm. in the bQm. There we plan our next steps and share informations

'''Group Parser'''
No one of us could compile the Eiffel Studio yet. We will study the code and make a page in this Wiki, in which we describe each class that is useful for our project. And then, we should talking about the interface with the other group.
'''Group Visualisation'''
We still have problems to compile Eiffel Studio too. We made a little summary about the classes we need to use under [[Syntax_checking/visualisation]]

Syntax checking/Visualisation

2006-05-12T11:36:19Z

Indermum:

== 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 “correct”, who indicates if the token is syntacticly correct or not.
* 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)
* inherit editor_token
* 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.

Src\library\editor\text_window\editor\text_window\interface\text_panel.e
* update lines: draws the textline

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

Syntax checking

2006-05-12T11:36:11Z

Indermum:

[[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
'''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

2006-05-12T11:27:45Z

Indermum:

[[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
'''Results of the Meeting:''' [[synche_visualistaion| 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]]

Talk:Syntax checking

2006-05-11T09:22:08Z

Indermum: Meeting 11.5.06

User:Chrigu

2006-05-11T08:59:14Z

Indermum:

chrhuber_at_student.ethz.ch

== Work ==
[[Syntax_checking]]

Syntax checking/SRS

2006-05-09T13:04:13Z

Indermum: /* Visualization */

= 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/SRS

2006-05-09T12:32:34Z

Indermum: /* Parser */

= 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 =
# Provides event handler and registers 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 clickable 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/SRS

2006-05-09T12:32:03Z

Indermum: /* Parser */

= 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; or leaving the edited word
### 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 =
# Provides event handler and registers 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 clickable 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

User:Indermum

2006-04-25T12:51:58Z

Indermum:

==Matthias Indermühle==

4. semester student in D-INFK at the ETH Zurich

indermum_at_student.ethz.ch

[http://www.snowworldpictures.ch.vu www.snowworldpictures.ch.vu]

==Work==
[[Syntax_checking]]

User:Indermum

2006-04-25T12:49:54Z

Indermum:

Matthias Indermühle

4. semester student in D-INFK at the ETH Zurich

indermum_at_student.ethz.ch

[http://www.snowworldpictures.ch.vu www.snowworldpictures.ch.vu]

working in software arcitecture at:
[[Syntax_checking]]

User:Indermum

2006-04-25T12:49:18Z

Indermum:

Matthias Indermühle
4. semester student in D-INFK at the ETH Zurich
indermum_at_student.ethz.ch
[http://www.snowworldpictures.ch.vu www.snowworldpictures.ch.vu]

working in software arcitecture at:
[[Syntax_checking]]

Syntax checking

2006-04-25T12:44:05Z

Indermum:

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

=Overview=
The aim of this project is to have a syntax checking done as you type.
Syntax errors should be highlited and eventualy also options for correcting the error should be propossed.

=Milestones=

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

==M2: May ??? ==
* To be completed by the team

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

* [[User:jabernet| Janick Bernet]] (big boss and scapegoat)
* [[User:fdevries| Fabien de Vries]]
* [[User:maser| Martin Luder]]
* [[User:clerco| Olivier Clerc]]
* [[User:indermum| Matthias Indermühle]]
* [[User:classens| Stephan Classen]]