Summer of Code/2013: Difference between revisions

Line 235:

=== GTK wrapper library for Android ===

Sugar Activities uses the PyGTK library wich is a binding for GTK. Android doesn't have GTK and porting GTK to Android is very complicated due to the difference in the user space of GNU/Linux and Android.

The ~~objetive~~ of this task is to develop a wrapper library of [http://www.pygtk.org/ PyGTK] that expose the same API but ~~invoque~~ equivalent methods in a Android graphic library like [http://kivy.org/#home Kivy]. The student only have to implement the minimal set of methods that allows to run the [http://activities.sugarlabs.org/en-US/sugar/addon/4418 hello world activity] wich is the more basic sugar ~~activty~~.

The objective of this task is to develop a wrapper library of [http://www.pygtk.org/ PyGTK] that expose the same API but invoke equivalent methods in a Android graphic library like [http://kivy.org/#home Kivy]. The student only have to implement the minimal set of methods that allows to run the [http://activities.sugarlabs.org/en-US/sugar/addon/4418 hello world activity] wich is the more basic sugar activity.

Level: Advanced

Line 243:

Line 244:

''Co-mentor'': [[User:Walter]]

Benefits to the Student: (a) Learn about Android graphic libraries and Python programming in Android

Benefits to the Community: This will be the first step to have a framework for porting Sugar Activities to Android with a minimal impact in the actual code of the activity. Also will help outside the Sugar community being a quick method for porting GTK ~~aplications~~ to Android

Benefits to the Community: This will be the first step to have a framework for porting Sugar Activities to Android with a minimal impact in the actual code of the activity. Also will help outside the Sugar community being a quick method for porting GTK applications to Android

== Sugar Activities ==

@@ Line 235: / Line 235: @@
 === GTK wrapper library for Android ===
 Sugar Activities uses the PyGTK library wich is a binding for GTK. Android doesn't have GTK and porting GTK to Android is very complicated due to the difference in the user space of GNU/Linux and Android.
-The objetive of this task is to develop a wrapper library of [http://www.pygtk.org/ PyGTK] that expose the same API but invoque equivalent methods in a Android graphic library like [http://kivy.org/#home Kivy]. The student only have to implement the minimal set of methods that allows to run the [http://activities.sugarlabs.org/en-US/sugar/addon/4418 hello world activity] wich is the more basic sugar activty.
+The objective of this task is to develop a wrapper library of [http://www.pygtk.org/ PyGTK] that expose the same API but invoke equivalent methods in a Android graphic library like [http://kivy.org/#home Kivy]. The student only have to implement the minimal set of methods that allows to run the [http://activities.sugarlabs.org/en-US/sugar/addon/4418 hello world activity] wich is the more basic sugar activity.
 Level: Advanced
@@ Line 243: / Line 244: @@
 ''Co-mentor'': [[User:Walter]]
 Benefits to the Student: (a) Learn about Android graphic libraries and Python programming in Android
-Benefits to the Community: This will be the first step to have a framework for porting Sugar Activities to Android with a minimal impact in the actual code of the activity. Also will help outside the Sugar community being a quick method for porting GTK aplications to Android
+Benefits to the Community: This will be the first step to have a framework for porting Sugar Activities to Android with a minimal impact in the actual code of the activity. Also will help outside the Sugar community being a quick method for porting GTK applications to Android
 == Sugar Activities ==