Project/Develop Activity: Difference between revisions
Tag: visualeditor |
Tag: visualeditor |
||
| Line 30: | Line 30: | ||
https://github.com/somosazucar/artisan | https://github.com/somosazucar/artisan | ||
==== Inspiration ==== | ==== Inspiration and Prior Art ==== | ||
<gallery> | Credit to the respective authors<gallery> | ||
File:Screenshot_of_Develop_testgtk2_.png| | File:Screenshot_of_Develop_testgtk2_.png| | ||
File:Pippy-screenshot.png | File:Pippy-screenshot.png | ||
| Line 37: | Line 37: | ||
=== Author === | === Author === | ||
Sebastian Silva - [[User:Sebastian]] | Jappy Activity is a project by Sebastian Silva - [[User:Sebastian]] | ||
Discussion to happen on sugar-devel@ | Discussion to happen on sugar-devel@ | ||
Revision as of 17:44, 2 April 2017
Jappy Activity
An Integrated Development Environment for Sugar and Sugarizer.
TRY IT NOW
Screenshot
Summary
Jappy Activity allows code editing and execution, much like Pippy in classic Sugar.
This provides the browser platform with a clear Python style syntax.
Jappy is already a full IDE, it can run Python code and save it in your Journal.
Secondary Goals
These are good objectives to achieve with GSOC
- An interactive console
- Build zip bundles (.xo)
- Git version control
- Internationalization of strings in Exceptions
- Interactive Debugger, Linter (like http://thonny.org/)
- Block snippets (like https://codesters.org/)
- External resources (like http://jsfiddle.net)
- More examples
Repository
https://github.com/somosazucar/artisan
Inspiration and Prior Art
Credit to the respective authors
Author
Jappy Activity is a project by Sebastian Silva - User:Sebastian
Discussion to happen on sugar-devel@
Timeframe
When it's done.
Proposed Architecture / Stack
Single page application.
Ace editor. Y-JS for collaboration. Git support.