<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000">Hey all,<br>
<br>
Some brief thoughts before conking out-<br>
<br>
- Before rethinking everything, let's check with Apple to clarify the
website restriction. I don't think PhoneGap would exist as such if its
biggest platform couldn't actually be leveraged. Also, considering Apple
was a driving force behind HTML5, I find it hard to believe they'd
reject it out of hand.<br>
<br>
- The repository gotcha is more troubling. I guess it's a security
consideration, which is reasonable. I don't see why you'd need teachers
to fork the whole project to create modules, though. As long as the
modules are sufficiently--er--modular, is there any barrier to having
them read in from SD card or other local storage? That way they can
still be downloaded (somewhat) conveniently, just not through the app
itself. Maybe I misunderstand what you're saying, Kento.<br>
<br>
- Shame about the name, but I suppose it's not worth fighting over. One
option is to keep the game's concept but change the aesthetic so instead
of racing cars, you're racing rockets. Tux Launch, maybe? *shrug*<br>
<br>
Best,<br>
Brendan<br>
<blockquote style="border: 0px none;"
cite="mid:4FD3C685.8060301@klocatelli.name" type="cite">
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="display:table;width:100%;border-top:1px solid
#EDEEF0;padding-top:5px"> <div
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
photoaddress="me@klocatelli.name" photoname="Kento Locatelli"
src="cid:part1.07020606.02020007@gmail.com"
name="compose-unknown-contact.jpg" height="25px" width="25px"></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a moz-do-not-send="true" href="mailto:me@klocatelli.name"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Kento Locatelli</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">June 9, 2012 4:56
PM</span></font></div></div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">Hey all!
<br>
<br>I think we decided to use this mailing list for discussing GSoC
project
things, right? Heh I hope so, otherwise this is in the wrong place :/
Anyway...
<br>
<br>First, Tux Racing is definitely going to change name at some
point... I
didn't think to check at the time, but there already are similarly
named games.
<br>
<br>But more importantly, I was talking to some people about the
repository
system [1] Tux Racing uses and learned of two Apple App store rules that
are problematic for Tux Racing:
<br>- Apps can't download code in any way, including Javascript code.
But
that's exactly what the repository/practice module system does,
download/run/update untested (but trusted) 3rd party code.
<br>- Apps can't be bundled websites. Again that's exactly what Tux
Racing
is, pure html5 webapp.
<br>
<br>Tux Racing violates both rules, and I'm not sure how to solve
them... I
have two proposed solutions, but I'd really appreciate community input
on the matter:
<br>
<br>- The simplest is to simply not publish in the App store and hope
users
make it to the website and set up a Web Clip (basically an icon that
launches the website). We lose publicity from the App store, but retain
the module repository system to allow teachers to make their own
practice modules for students.
<br>
<br>- The other is to remove the repository system and have everything
bundled locally in the app, which allows us to meet both of those
guideline requirements. We'll definitely get more iOS users, but
practice modules are no longer self-updating and it becomes harder for
3rd parties to create new modules for mobile platforms. In order for a
teacher to get their module working *in the Tux Racing mobile app*, they
have to get it bundled with Tux Racing, wait for users to update their
apps, and repeat the process for any updates. note this is removing the
repository system in general, not just for iOS.
<br>
<br>I'm leaning towards the latter, but my reasoning is entirely based
on
assumptions. My guess is if a teacher is creating a practice module,
simply forking TR will fulfill their needs. They can copy in their
module, upload to their website, and have students browse to the URL on
an internet-enabled device. Their module still works on mobile devices,
but through the web browser instead of the official app. Looks the same,
works the same, same code to hook in and everything. Furthermore, I
don't think there would be enough 3rd-party modules to justify not being
in the App store. Of course we can always re-add the repository system
and withdraw from the App store once more users know about the
application if it's determined the repository system is genuinely useful
in practice.
<br>
<br>What are your thoughts on the matter? Do my assumptions hold? Is
there a
better alternative to those two proposals?
<br>
<br>Cheers!
<br>Kento Locatelli
<br>
<br>
<br>[1] - Tux Racing has a problem generator system. Repository system
allows adding/updating 3rd party problem generators to the game without
reinstalling/updating the application. The idea was for teachers to
create a problem generator for their students to practice, and give
their students a URL. The game then makes the new problem generators
available.
<br>
<br>_______________________________________________
<br>Tux4kids-discuss mailing list
<br><a class="moz-txt-link-abbreviated" href="mailto:Tux4kids-discuss@lists.alioth.debian.org">Tux4kids-discuss@lists.alioth.debian.org</a>
<br><a class="moz-txt-link-freetext" href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/tux4kids-discuss">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/tux4kids-discuss</a>
<br></div>
</blockquote>
</body></html>