Yes, Prof. Nagarjunaji, I have heard of your device and was really keen on the opportunity to interact with you over it. Of course, I am not one for reinventing the wheel and hence, the possible steps plus I, too, am more in favor of the 2nd option.<div>
<br></div><div>Though, interestingly, Peter Robinson's suggestion makes a lot of sense of having a Fedora when, anyway, there is Linux under.<br><div><br></div><div>I will definitely meet up with you in Mumbai when the opportunity comes forth.</div>
</div><div><br></div><div><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">"....though touchscreen may have some advantages for some activities. Second, Sugar learning platform has plenty of activities to offer which are not available on Android currently."</span><br>
</div><div><br></div><div>1. Touchscreen opens up a lot of possibilities by way of creating more touchscreen conducive activities that are culture, locale specific. Enabling Touchscreen event for existing activities does not necessarily leverage the advantage of touch screen in enhancing the existing learning experience and to this regard, I am concerned about the complete picture of enabling a hand-held device to the optimum performance and therefore, this question.</div>
<div><br></div><div>2. Second you totally on the second.</div><div><br></div><div>Regards,</div><div><br></div><div>RJv</div><div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Dec 12, 2012 at 9:07 PM, Nagarjuna G. <span dir="ltr"><<a href="mailto:nagarjun@gnowledge.org" target="_blank">nagarjun@gnowledge.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br><br><div class="gmail_quote"><div class="im">On Tue, Dec 11, 2012 at 8:54 PM, RJV <span dir="ltr"><<a href="mailto:jv.ravichandran@gmail.com" target="_blank">jv.ravichandran@gmail.com</a>></span> wrote:<br>
</div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Hi,</div><div><br></div><div>We are planning to port Sugar on Android and are faced with these options:</div><div><br></div><div>1. Sugar as an application on Android.<br></div><div>2. As a platform on top of the Linux platform.</div>
<div><br></div><div>Can the Sugar build be used to create an app bundle to deploy to the app store? Are there any licensing issues?<br clear="all"><div><br></div><div>On 2., can someone share their experience, if any, please?</div>
<span><font color="#888888">
</font></span></div></blockquote></div><div><br><div class="im">We are very close to having Sugar on a tablet as well as a armel
netbook, based on A10 chipset. We already have it working through a SD
card, we are now in the process of flashing the internal memory, so that
it will work fast. Almost all the hardware on A10 chipset is working
with the linux kernel without any binary blobs. <br>
<br>We work in Mumbai. In case you are around the city, we can meet and discuss how we can work together. <br><br>The
reason why 1 is not considered for us an option is: what children need
is not a desktop that is meant mainly for delivery of content to play
multimedia files and do business communications. We would like the
children to work, do activities using a workspace that can be used with a
keyboard, though touchscreen may have some advantages for some
activities. Second, Sugar learning platform has plenty of activities to
offer which are not available on Android currently. and Third, 1 will
take a long time than 2. So we opted for 2. <br>
<br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br>Nagarjuna G.<br><a href="http://www.gnowledge.org/" target="_blank">http://www.gnowledge.org/</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>Regards,<br><br><b>Ravichandran J.V.</b><br><a href="http://ravichandranjv.blogspot.com" target="_blank">http://ravichandranjv.blogspot.com</a><div>
<span style="font-family:arial;font-size:small">XO 1.75 - 12.1, 0.96, Build 21, Q4D17</span><br></div><br>
</div>