Difference between revisions of "Syntax checking"

Line 35: Line 35:
 
*'''Parser Group''': Find out what results you get from the parser
 
*'''Parser Group''': Find out what results you get from the parser
 
*'''Visualisation Group''': Write a feature that draw the red underline
 
*'''Visualisation Group''': Write a feature that draw the red underline
 +
 +
== May 17th ==
 +
'''Results of Parser Group:''' [[Syntax_checking/Parser| Parser]]
  
 
=Team=
 
=Team=

Revision as of 03:21, 17 May 2006

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 here

Groups

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

May 17th

Results of Parser Group: Parser

Team

Everyone intrested in this project is welcome to join our mailinglist 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

Parser

Assistant