<html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi, Jonas I guess you see how far out from the developer community I am. I associate sucrose with Activity Central. I am not sure what a sucrose developer is. The involved developers have been doing well. However, for many of the activities in ASLO, the original contributors have moved on, a natural situation in open source. There is no attempt to point fingers, the decision is there. If Sugar is to move to the mobile device, it appears necessary to work in a Javascript not Python environment. So an activity developer/maintainer needs to decide whether his investment in time in GTK is warranted or should be spent it in rewriting the activity as a Sugar-web-activity. Tony <div class="moz-cite-prefix">On 12/26/2015 04:58 PM, Jonas Smedegaard wrote: </div> <blockquote cite="mid:145114190542.1782.11302964747740379691@auryn.jones.dk" type="cite"> <pre wrap="">Quoting Tony Anderson (2015-12-26 19:53:47) [Jonas wrote:] </pre> <blockquote type="cite"> <blockquote type="cite"> <pre wrap="">True - either that or ditch the activities evidently too badly maintained to work well with modern Sugar. </pre> </blockquote> <pre wrap=""> Aye, There's the rub! Is the problem 'bad maintenance or none at all' or 'modern' Sugar. Certainly TuxMath is suffering from 'abandonment'. However, even abandoned code continues to run when the underlying support is there. In this case, programmers who were not involved in the development or maintenance of the code will have to figure out how to get it running again or rewrite it in Javascript. </pre> </blockquote> <pre wrap=""> Wrong: In this case all developers were involved at their various levels of the chains of events but some of them were inactive: GTK+ developers chose to improve their code beyond what a previous API could contain and sensibly bumped API and kept alive the previous API for ages. Sucrose developers chose to build their code on top of GTK+ and sensibly handled the API split of GTK+ including maintenance of a legacy interface for ages. Activity developers chose to build their code on top of Sucrose and some of them sensibly migrated to new interfaces, but sadly some activity developers did not react yet - and *that* is not sensible. </pre> <blockquote type="cite"> <pre wrap="">The port of activities to GTK+ 3.x seems to have stalled because of the higher priority to re-implement activities such as TurtleBlocks in javascript. Consider the long-term job security in rewriting Sim City in javascript as a Sugar-web-activity. </pre> </blockquote> <pre wrap=""> Are you pointing fingers at other volunteers choosing to spend their time in a way you disaprove of, or have you provided patches to migrate some activities but have been turned down? </pre> <blockquote type="cite"> <pre wrap="">In the case of gstreamer 0.1, I was able to find how to install the codecs: </pre> </blockquote> <pre wrap="">[...] </pre> <blockquote type="cite"> <pre wrap="">I am certainly sure that everyone is bored to tears on this subject since I have mentioned it so many times already. </pre> </blockquote> <pre wrap=""> Did you "mention" it through the appropriate issue tracker? - Jonas </pre> <fieldset class="mimeAttachmentHeader"></fieldset> <pre wrap="">_______________________________________________ Sugar-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </pre> </blockquote> </body> </html>