[Sugar-devel] TamTamMini

[Daniel Narvaez]

On 16 November 2013 10:23, David Farning <dfarning at activitycentral.com>wrote:

> > TamTamMini separated from other Suite applications, deleting files that
> were
> > not used.
> > I deleted the images were not used or those that were not necessary.
> > Corrected, I simplified and cleaned up the code.
> >
> > As a result , the application occupies least 5 mb.
> >
> > I ported the application to gtk3 .
>
> The update process can take months and even years for large deployments.
>
> As a result critical activities must run, have a consistent look and
> feel, and be validated across both Gtk2 and Gtk3.
>
>
At the cost of being blamed to ignore deployment needs... I don't think
supporting both toolkits like that is realistically sustainable.

That said, I understand where this is coming from, it's just a really bad
situation to be in. Let's try to support it as well as we can but at the
same time, let's do whatever we can to move deployments to gtk3 as soon as
possible.


> > I built separate versions for xo gtk2 and gtk3 1.0 , x 1.5 , x 1.75 and
> one
> > for Magalães. Each version contains the corrections necessary for proper
> > operation as both gtk gtk3 for each particular machine.
>
> Deployments often run several types of hardware.
>
> As a result activities must run, have a consistent look and feel, and
> be validated across each type of hardware in use by the deployment.
> The becomes tricky as activities bypass the API provided by Sugar and
> interact directly with low level libraries.
>
>
I'm not sure what was the issue with TamTam exactly, but I'd hope hardware
related incompatibilities to be relatively rare, assuming a recent
software. If not, we must fix that :)


> > All versions were tested in each of the aforementioned machines and all
> > functioning properly. It only remains to make some very minor repairs on
> > gtk3 versions .
> >
> > I wish that the maintainers of the repository with TamTam saw all this
> > content for the purpose of seeing whether it is possible to unify into a
> > single repository TamTamMini .
>
> The challenge becomes what to do when the work like this does not fit
> the priorities of the activity maintainer.
>

In this community, if the maintainer is too busy to deal with patches like
this, I suspect he would be more than willing to accept co-maintainers.
That's assuming the maintainer is at all resposive. If not, I'd say
maintainership could be just taken over.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20131116/4624998b/attachment.html>