[Sugar-devel] A prototype of SugarWeb / SugarAndroid - Technical questions

[Daniel Narvaez]

On 15 November 2013 21:16, Lionel Laské <lionel at olpc-france.org> wrote:

>
> I wonder if we should first just fork sugar-web, implement the ideal API
> for Web/Android there and later figure out how reconcile with Linux.
> Reconciling is going to be a bit tricky I think, even more without a clear
> idea of what API we will need for Web/Android. (Thinking of the datastore
> mostly).
>
> Hummm. I would be better to avoid forking now. At worse, I think, a
> testing condition (if Linux else Web/Android) could be better.
>

That's fine too. Hopefully it won't be too much of a mess :)


>  Yeah or use them conditionally.
>>
>> Perhaps we need to choose one or two target browsers initially, being
>> compatible with everything is going to be a lot work or too limiting anyway.
>>
>
> It's not very important in activities but I think the framework should be
> compatible with a large number of browsers. Today two activities have
> compatibility issue (Clock), other issues are in the framework (Custom and
> Blob object).
>

I agree that compatibility is more important in the framework.


>
>> It's a way for the native python activity to pass some  initial
>> environment variables to the web layer (like the activity id and the
>> datastore object id). As for bus.js etc I would fork and get rid of these
>> initially, then we can figure out the best way to reconcile.
>>
>
> Okay. I guessed it was use as a way to detect Sugar Linux or Sugar Web but
> I didn't figure how. To hack it I've forced the creation of the sugar
> object (
> https://github.com/llaske/SugarWebUI/blob/master/lib/sugar-web/bus.js#L2)
> but I'm not very happy with it.
>

 Do you have any plan on how to implement datastore? To known that even
just vaguely would be helpful in suggesting how to deal with
bus.js/environment.js...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20131116/379f544f/attachment.html>