Changes

Jump to navigation Jump to search
Line 81: Line 81:     
The tutorial creator is for both teachers and students who have earned some knowledge about JS to help other fellow students. This would not require any further development skill. The teacher/student would have to enter only three things to make tutorial expected input code, expected output code and some explanation/hint/syntax about the input code which would help the student to understand the usage of that command. This application will be packaged with some tutorials during its installation only.
 
The tutorial creator is for both teachers and students who have earned some knowledge about JS to help other fellow students. This would not require any further development skill. The teacher/student would have to enter only three things to make tutorial expected input code, expected output code and some explanation/hint/syntax about the input code which would help the student to understand the usage of that command. This application will be packaged with some tutorials during its installation only.
 +
THE VISUAL JS DEBUGGER
 +
The interface has a easy Javascript debugging facility where if the student clicks on a line of the code he/she has written the debugger will return the value of all the declared variables just after execution of that particular line. This task is accomplished by the help of library UglifyJS which parses a given source code to and can list out the variables used. I have already built a simple debugger and here is a screencast of that - [http://wiki.sugarlabs.org/images/f/fe/Final.gif LINK].
 
  INTERACTIVE TUTORIALS INTERFACE
 
  INTERACTIVE TUTORIALS INTERFACE
   Line 99: Line 101:  
MATLAB is a very important tool available for any engineering/science field.
 
MATLAB is a very important tool available for any engineering/science field.
 
We can add support for running matlab/octave(.m) codes by using the octave interpreter.
 
We can add support for running matlab/octave(.m) codes by using the octave interpreter.
* '''ANIMATED GIF OF THE DEBUGGER INTERFACE ([http://wiki.sugarlabs.org/images/f/fe/Final.gif LINK])'''
+
* '''ANIMATED GIF OF THE DEBUGGER INTERFACE ([http://wiki.sugarlabs.org/images/f/fe/Final.gif LINK])'''[[File:Final.gif|centre|1103x1103px|]]
* [[File:Final.gif|centre|1103x1103px|]]
   
* '''A SCREENSHOT FROM THE SUGAR WEB-ACTIVITY'''
 
* '''A SCREENSHOT FROM THE SUGAR WEB-ACTIVITY'''
 
[[File:SugarTest.png|thumb|1100x1100px|]]
 
[[File:SugarTest.png|thumb|1100x1100px|]]
Line 119: Line 120:  
The main GUI shown above is build usingJavascript and HTML/CSS.It communicates with a host computer (can be the device running Sugar itself) which is aNodeJSbased server. Support for languages depends on the compilers which are installed in the host computer.  
 
The main GUI shown above is build usingJavascript and HTML/CSS.It communicates with a host computer (can be the device running Sugar itself) which is aNodeJSbased server. Support for languages depends on the compilers which are installed in the host computer.  
   −
I would probably be using the [https://github.com/adobe-research/theseus Thesus] library for visual debugging.
+
I would probably be using the some JS parser library, UglifyJS for visual debugging.
    
For checking flaws in code before running it I am familiar with two tools [http://www.splint.org/ Splint] and [https://github.com/danmar/cppcheck cppcheck]. I am looking into other possible solutions for this part.
 
For checking flaws in code before running it I am familiar with two tools [http://www.splint.org/ Splint] and [https://github.com/danmar/cppcheck cppcheck]. I am looking into other possible solutions for this part.
61

edits

Navigation menu