User:Shainasabarwal/GSoC15/logs

Community Bonding Period

• Wrote code for new scadlexer in scadlexer.h and scadlexer.cpp files.
• Fetch the colors in scintillaeditor.cpp file for new scadlexer and it is successfully working
• Wrote functions on highlighting keywords and highlighting comments.
• Tested with Qt4 as well as Qt5
• Wrote function for highlight multiline comments
• Wrote function to highlight numbers
• Trying to search any better way for lexing approach using QSciLexerCustom class.

Coding Period

25 May

• Discussed and researched about different tools that can be used in scad lexer.

26 May

• Chosen lexertl to be used for scad lexer.
• Started reading lexertl documentation

27 May

• Lexertl in boost is not the latest version, so as per its latest documentation it doesn't work, trying to read code of lexertl included in boost

28 May

• Contacted Ben Hanson, the person who wrote lexertl and its documentation and he suggested to use the latest version of lexertl and not that included in the boost, because the latest version has some bug fixes and it also supports unicode. Also it is header file library so, we won't be needing to make any change in installation script
• Discussed about this with my mentors
• Added lexertl header files in openscad new branch lexertl

29 May

• Read lexertl documentation and examples at https://github.com/BenHanson/lexertl/tree/master/examples and tried to add something into scadlexer files to test its working.

30 May

• Added rules for numbers, operators etc and divide code into tokens.
• Wrote the code for lookup table.

1 June

• Successfully started highlighting keywords using lexertl tool in scadlexer.

2 June

• Added rules for single line and multi line comments.
• Multi line comments are not working as expected.

3 June

• Read more about regular expression to have an efficient rule for single line and multi line comments.

4 June

• Editor became slow. Trying to figure out what's the problem with it. May be the styleText function is being called again and again and so with it all rules of lexer are being called again and again on making any change in the editor by the user.

5 June

• Discussed with mentors and defined all the rules in constructor instead of styleText function and this way, editor got its normal speed.

6 June

• Discussed with mentors about problems in comments and keyword highlighting and started writing tests.

8 June

• Wrote a C++ program using lexertl library with simple rules as testing.

9 June

• Get the tests written checked by mentors and made more improvements.

10 June

• Preparation for viva-voce in college, generating report and presentation

11 June

• All day spent in college for waiting and delivering presentation to teachers and students

12 June

• Read more in lexertl documentation to write comments as another state machine.

15 June

• Discussed with mentors about writing tests, ie, reading scad script from an input file, mark the keywords, numbers etc and then put the output in another file.

16 June

• Wrote test in C++ using lexertl library, defining various rules, which puts in the output in output file and get it checked by the mentors.