Difference between revisions of "Activities/Pilas"
Jump to navigation
Jump to search
Tonyforster (talk | contribs) |
Tonyforster (talk | contribs) |
||
| Line 36: | Line 36: | ||
* Bug: resize widgets | * 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 actions of pilas and behaviors | |
| − | + | * help tab | |
| − | + | * persistent options | |
| − | + | * Document examples / startup guide | |
Future Work | Future Work | ||
| − | + | We must turn this into a roadmap ... | |
To-do: To-do: | To-do: To-do: | ||
Revision as of 20:16, 9 April 2012
Sorry, information only available low quality translation at the moment. Your help with translation will be very welcome :)
Go to Pilas Activity page in Spanish.
This is to bring the game development engine pilas-engine to Sugar, adapting to the needs of this platform and adding elements to your learning curve.
We seek to facilitate teaching tool for Python and game development.
This project was developed during the 2011 Sugar Junin Day 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's 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 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 actions of pilas and behaviors
- help tab
- persistent options
- Document examples / startup guide
Future Work
We must turn this into a roadmap ...
To-do: To-do:
* Recortar lista de dependencias creada con PyInstaller, que solo incluya lo que hace falta Trim list of dependencies created PyInstaller, that includes only what is needed * Incorporar autocomplete e inline help de ninja-ide Incorporating inline autocomplete and help of ninja-ide * Utilizar dbus [10] para comunicar widgets del menú con los otros Use dbus [10] to communicate around the menu with the other * Incorporar persistencia de Sugar [o distintas opciones de persistencia del código que se desarrolle] Incorporate Sugar persistence [persistence options or code to be developed] * Integrar código de pilas-engine [11] y pilas.xo Embed code for battery-engine [11] and pilas.xo
Wish list
* Refactoring para PyCairo [12] Refactoring to PyCairo [12] * Incorporar posibilidad de compartir actividad de Sugar Incorporate activity sharing Sugar * Agregar opciones interactivas sobre los objetos (tipo eToys [13] ) Add interactive features on objects (eToys type [13] )