User:Shainasabarwal/GSoC14/logs

Development Logs

Community Bonding Period

• Read OpenSCAD source and test files.
• Learnt some important Qt classes used in OpenSCAD.
• Explore different editors that can be integrated into OpenSCAD editor.
• Discussed with community about the editor and finalized QScintilla.

Development Period

Week 1

19th May Worked on Detachable rendering window.

20th May Read about QScintilla integration after discussion with community

21st May Completed the task of Detachable window and made a pull request in branch detatchrenderwindow of OpenSCAD.

22nd May

• Submitted patch for detachable render window, which my mentor said, can be a good addition to https://github.com/openscad/openscad/pull/787.
• Discussed about the integration of editor.
• Added class Qscintilla and make two separate objects of QTextEditor and QScintilla classes in Editor class.

23 May

• Removed errors and Added some built in functions of QScintilla class so that its minimal functionality can be seen.
• Discussed about it with mentors and I got that two separate classes should be made say legacyEditor and ScintillaEditor which will inherit QTextEdit and QScintilla classes respectively and an Interface class Editor will be used to call the functions of both these classes.

24 May

• Refactored some code and made two separate classes as discussed.
• More code need to be refactored yet.

Week 2

26 May

• Searched about how to change the color of rendered model.
• Checked rendersettings.cc renderer.cc preferences.cc. Preferences.cc has color scheme for preview but not for rendered model.

27 May

• The functions defined in legacyEditor.cc can be called in mainwin.cc by object of interface class i.e. Editor.

28 May

• Still not able to find the code that affects the color of rendered model. Struggling for it.
• Facing a segmentation fault because of toPlainText() function call in mainwin.cc at some places. Trying to solve it.

29 May

• Completed the editor class as interface and defined virtual functions into it using which the derived class functions can be called into the mainwin.cc

30 May

• The size of the editor is creating problem. It is not fitting into the DockWidget. Read about size hint, size policy and customizing Qt widgets.

31 May

• Cloned new openscad as a lot of changes are made by the developer and installed required libraries. Build OpenSCAD with Qt5 and remove errors caused to old libraries versions. My mentor suggested me to shift to Operating system Ubuntu 14.04 as 12.04 is not supporting new libraries required by OpenSCAD.

Week 3

2 June

• Installed QScintilla editor API and read its example to understand how to it can be integrated into OpenSCAD.
• Made Scintilla class derived from Editor class.

3 June

• Install OS Ubuntu 14.04 lts.
• Cloned OpenSCAD and build required libraries
• Scintilla editor is not working. Trying to figure out the problem.

4 June

• As the editor is removed from MainWindow.ui file, the editor defined as object of legacyEditor is facing some size issues. Trying to figure out how to set its size equal to its parent editorDockContents.

5 June

• Integrated QScintilla editor into openscad with minimal functionality.

6 June

• Solved size problem of legacy and scintilla editors successfully. Now they are occupying the full editorDock widget space.

7 June

• Read and became familiar with QScintilla documentation to add new features into the scintilla Editor.

Week 4

9 June

• Made a wiki page showing what features need to be implemented in editor
• Line numbers at the margin.
• Brace Matching.
• Auto Indentation

10 June

• Included line wrap and flags at wrapping to make the editor responsive to the window size.
• Add margin width to the line numbers so show the full line number, previously it was showing just the last digit.

11 June

• Discussed with mentors, how to add error indicators. This was bit confusing, as with scintilla editor we are not using the existing highlighter class which is used for highlighting and error indicating

12 June

• Understanding how to do error indicating using qscintilla functions provided in documentation.

13 June

• Error indicator is implemented
• Facing problem in unhighlighting when the user solve the error
• Finally implemented error indicators with marker at line number which will help to identify line having error in case there is no line wrapping

14 June

• Today's task was to work towards syntax highlighting. Qscintilla has different lexer classes such as QsciLexerCPP, QsciLexerJava etc for highlighting syntax of different languages. But all the keywords used in openscad are not supported in single language. Planning how to tackle this problem.