Difference between revisions of "Activities/Pilas"
Jump to navigation
Jump to search
Tonyforster (talk | contribs) |
Tonyforster (talk | contribs) (→Status) |
||
| Line 38: | Line 38: | ||
* Documentation of how it is packaged with Qt activity [http://qt.nokia.com/] for Sugar | * Documentation of how it is packaged with Qt activity [http://qt.nokia.com/] for Sugar | ||
* define user guidelines and make mockups | * define user guidelines and make mockups | ||
| − | * typical Pippy examples [http://activities.sugarlabs.org | + | * typical Pippy examples [http://activities.sugarlabs.org/sugar/addon/4041] |
* interpreter and code editor tabs | * interpreter and code editor tabs | ||
* option to run in fullscreen or box | * option to run in fullscreen or box | ||
Revision as of 06:08, 10 April 2012
Sorry, this page translated from the original Spanish. Your help improving this translation will be very welcome :)
Go to Pilas Activity page in Spanish.
Pilas.xo Project
This brings the pilas-engine game development engine to Sugar, adapting it to the needs of the Sugar platform and adding elements to your learning curve.
We seek to facilitate a teaching tool for Python and game development.
This project was developed during the 2011 Sugar Junin Day Sugar Day Junin 2011
Links to the project
- Activity. .XO [1]
- Code [2]
- Issues tracker [3]
- Name of branch 'pilasqt'. Command to take to the branch:
hg clone https://hugoruscitti@bitbucket.org/hugoruscitti/pilas cd pilas/ hg update pilasqt
Status
What has been done:
- Packaging the pilas-engine [4] to run on Sugar.
- Incorporation of PyQt libraries [5] into the activity
- Adding widget ninja-ide [6] , to have the interactive shell on the same screen.
- Generation of file dependencies needed for the project with PyInstaller [7]
- Creating the pilas.xo activity
To-do immediately:
- Bug: resize widgets
- Bug: set focus
- Documentation of how it is packaged with Qt activity [8] for Sugar
- define user guidelines and make mockups
- typical Pippy examples [9]
- interpreter and code editor tabs
- option to run in fullscreen or box
- list of Pilas actions and behaviors
- help tab
- persistent options
- Document examples / startup guide
Future Work
We must turn this into a roadmap ...
To-do:
- Trim list of dependencies created PyInstaller, to include only what is needed
- Incorporating autocomplete and inline help for the ninja-ide
- Use dbus [10] to communicate with the menu of others
- Incorporate Sugar persistence [persistence options or code to be developed]
- Integrate code for the pilas-engine [11] and pilas.xo
Wish list