<br><br><div class="gmail_quote">On Tue, Apr 5, 2011 at 7:23 AM, NoiseEHC <span dir="ltr"><<a href="mailto:NoiseEHC@freemail.hu">NoiseEHC@freemail.hu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Scott!<br>
<br>
The IAEP thread if I am not mistaken is this:<br>
<a href="http://lists.sugarlabs.org/archive/iaep/2011-February/012522.html" target="_blank">http://lists.sugarlabs.org/archive/iaep/2011-February/012522.html</a><br>
<br>
When last time I proposed similar things on the mailing list all I have<br>
got were:<br>
1. Do not tell others what to do!<br>
2. CADT<br>
3. I want others to drop all sugar code now!<br>
4. People unsubscribed from the list because of me. (At least it was a<br>
good excuse I guess...)<br>
So congratulations, you have *way* better communication skills that I<br>
will ever have, your thread was fascinating to read.<br>
<br>
In the meantime I personally changed my preferences regarding this Sugar<br>
"rewrite" on Android, and now I see how stupid was I. The problem is<br>
that there is no need to "rewrite" stuff on Android when there is a much<br>
more easier, cross-platform thing exists and it is HTML5!!! (I have even<br>
tested chrome's speed on an XO-1 and it is totally acceptable.)<br>
When I skimmed over the activities in the Sugar Activity Store :) I<br>
realized that there are not too many of them. Most of the activities<br>
fall into the following 3 categories:<br>
1. Small activities which can be easily rewritten.<br>
2. Big activities which are ported to Sugar (etoys, scratch, write).<br>
3. GCompris. A lot of them.<br>
4. It can be that Uruguay and Peru created a lot of stuff I do not know<br>
about and I am stupid.<br></blockquote><div><br></div><div>Notably Ceibal Jam </div><div><a href="http://ceibaljam.org/?q=lista_descargas/jam">http://ceibaljam.org/?q=lista_descargas/jam</a></div><div><br></div><div>some of them are already on Sugar's Activity Library.</div>
<div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
So I clearly cannot see the need for invisible perfect compatibility<br>
because 2-3 are already ports so they must be ported anyway, and 1. does<br>
not contain that much activities to warrant such amount of work in my<br>
opinion. But you know, I will not tell you what (not) to do... ;)<br>
<br>
What you do not seem to take into consideration are these:<br>
1. Activities should move to a per activity storage model (like Android<br>
does) otherwise your compatibility layer will not work too well.<br>
2. The Sugar HIG will result in pathetic touch controlled applications,<br>
even if the problems can be fixed by the excellent suggestions of Gary<br>
C Martin (here:<br>
<a href="http://lists.sugarlabs.org/archive/iaep/2011-February/012556.html" target="_blank">http://lists.sugarlabs.org/archive/iaep/2011-February/012556.html</a>).<br>
Okay, actually I think that you totally understand 2. so I just do not<br>
get what your point with invisible compatibility is...<br>
<br>
Good luck anyway,<br>
NoiseEHC<br>
<br>
BTW, in the next 4 weeks I will rewrite Sugar to HTML5... :)<br>
<div><div></div><div class="h5"><br>
<br>
<br>
<br>
<br>
<br>
<br>
On 2011.04.05. 0:09, C. Scott Ananian wrote:<br>
> I've posted a four week plan for XO-3 software exploration at<br>
> <a href="http://cananian.livejournal.com/62667.html" target="_blank">http://cananian.livejournal.com/62667.html</a><br>
><br>
> Briefly:<br>
> April 4-8: Android<br>
> April 11-15: Chrome/ChromeOS/NativeClient<br>
> April 18-22: Get down& dirty with mesh<br>
> April 25-29: Yanking legacy Sugar codebase into the future<br>
> May 2-6: in Uruguay to present results and discuss all this w/ Sugar<br>
> folks in person<br>
><br>
> I'll be posting more about each project as I dig into them; there are<br>
> also threads on IAEP where I've discussed all these topics before, so<br>
> they shouldn't come as too much of a surprise.<br>
><br>
> There are other ideas out there, and I'm not going to *finish* any of<br>
> these investigations in a single week. Feel free to ask questions and<br>
> suggest other projects -- although please read the existing<br>
> discussions first if you can. In order to actually get work done w/o<br>
> endless distraction, I'll probably try to avoid getting into lots of<br>
> details for projects other than the one I'm currently focusing on.<br>
> --scott<br>
> _______________________________________________<br>
> Devel mailing list<br>
> <a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br>
> <a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
><br>
><br>
<br>
_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
</div></div></blockquote></div><br>