[Sugar-devel] ARM fork
Ryan Cunningham
rvskmbrly3 at gmail.com
Wed Jun 18 12:11:14 EDT 2014
This fork should not be merged into the main repository.
--
Sent from my iPad
> On Jun 18, 2014, at 9:05 AM, Ryan Cunningham <rvskmbrly3 at gmail.com> wrote:
>
> I have forked your "sugarlabs/sugar" GitHub repository and made some changes necessary to enable Sugar to operate successfully on ARM tablets.
>
> The most important change is the requirement of installation of the onBoard on-screen keyboard from Ubuntu; it is to be automatically invoked on entry into any text field (except if onBoard is already running) and is to be automatically killed on departure from that field; therefore, some activities may have to be ported specifically for this architecture.
>
> The new repository branch is at <https://github.com/rcunning01/sugar/tree/arm>. It is public; however, only I have authorization to modify it.
>
> I am writing this e-mail to query for any results from testing this on any Android tablet (this version does not work with Android phones) you might have or desire to purchase. However, such a test causes /all/ existing data on the tablet (including core OS data) to be erased, so deploy carefully. The software itself, however, is, and should continue to be, platform-independent.
>
> The results should be as follows, if any errors are generated:
>
> * Abnormal tracebacks from the Python interpreter (said tracebacks are accessed via the Log activity)
> * Abnormal exception reports from ADB (the Android Debugger)
> * Suggestions for correction
>
> This version continues to use GTK+. You will need to modify the resulting Android OS image, adding to it cross-compilations (for the ARM platform) of the following applications and libraries:
>
> * X11
> * The Metacity window manager
> * GTK+
> * Pango
> * GLib
> * GObject-Introspection
> * ATK
> * GDK-Pixbuf
> * PyGObject
> * Python 2.7
> * sugar-artwork
> * sugar-toolkit-gtk3
>
> Tell me if more are needed.
>
> (This version does not have cell phone network support. The Terminal activity, when ported to ARM, should require that the destination device have sufficient access privileges [on Android, this is obtained by rooting], and, with this port, should be a separate download.)
>
> --
> Sent from my iPad
More information about the Sugar-devel
mailing list