[Sugar-devel] Starting a new web activity : problem when closing activity, and with icon design

Lionel Laské lionel at olpc-france.org
Wed Dec 3 09:40:37 EST 2014


Ooch, it's a key issue.

In practice, an activity using the Sugarizer sugar-web version could work
both on Sugarizer and Sugar without any change. The bad news is that the
reverse is not true - today.

The problem is that of course, sugar-web must have a different
implementation for Sugarizer and for Sugar. For the datastore for example,
in Sugar the JavaScript code should call Python datastore API, and in
Sugarizer the JavaScript code should call the HTML5 local storage.
>From the beginning, sugar-web for Sugarizer use exactly the same interface
than the one for Sugar. It's why there is no need to change an activity
between Sugar and Sugarizer. More, in sugar-web for Sugarizer, both source
code are separate to avoid confusion and collision [1].

However, the multiple attempt I've done to integrate this Sugarizer
specific code into sugar-web repository has failed. All my pull request has
been refused [2]. I must confess that I've lost the courage to insist about
that thought I'm still convinced like you that we should have an unique
sugar-web version. So any help to work on this is welcome.

               Lionel.

[1]
https://github.com/llaske/sugarizer/blob/master/activities/ActivityTemplate/lib/sugar-web/datastore.js
[2] https://github.com/sugarlabs/sugar-web/pull/112


2014-12-02 19:06 GMT+01:00 Gonzalo Odiard <godiard at sugarlabs.org>:

> Hi Lionel,
> Why we need two different versions of sugar-web?
> That in practice makes the same activity can't run in both environments...
>
> Gonzalo
>
> On Tue, Dec 2, 2014 at 3:04 PM, Lionel Laské <lionel at olpc-france.org>
> wrote:
>
>> It's a nice first start.
>> Now replace your lib/sugar-web directory with the one from
>> lib/ActivityTemplate directory.
>> It should work.
>>
>>           Lionel
>>
>> 2014-12-02 11:04 GMT+01:00 laurent bernabe <laurent.bernabe at gmail.com>:
>>
>>> Hi again,
>>>
>>> Restarting my computer, I was finally able to run sugarizer in my chrome
>>> instance.
>>> Meanwhile, I can't close my application (Simple Tic Tagardsc Toe).
>>>
>>> regards
>>>
>>> 2014-12-01 18:42 GMT+01:00 laurent bernabe <laurent.bernabe at gmail.com>:
>>>
>>>> I am just using the "modified" chrome instance (with allow access from
>>>> file), but I am still getting the same errors in the navigator console.
>>>>
>>>>
>>>> Regards
>>>>
>>>> 2014-12-01 15:57 GMT+01:00 Lionel Laské <lionel at olpc-france.org>:
>>>>
>>>>>
>>>>>
>>>>> 2014-12-01 15:25 GMT+01:00 laurent bernabe <laurent.bernabe at gmail.com>
>>>>> :
>>>>>
>>>>>>
>>>>>> So it seems that the option is not taken into account from my Chrome
>>>>>> instance.
>>>>>> I will look for another way (like in settings:// ?) to set this
>>>>>> option.
>>>>>>
>>>>>> Ensure that no other instance is running. If one instance is running,
>>>>> it's not possible to start one another with another setting.
>>>>>
>>>>>         Lionel.
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Laurent Bernabé
>>>>
>>>> laurent.bernabe at gmail.com
>>>>
>>>
>>>
>>>
>>> --
>>> Laurent Bernabé
>>>
>>> laurent.bernabe at gmail.com
>>>
>>
>>
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>
>
> --
> Gonzalo Odiard
>
> SugarLabs - Software for children learning
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20141203/a40d781c/attachment-0001.html>


More information about the Sugar-devel mailing list