[Sugar-devel] Web Activity lifecycle and storage

Gonzalo Odiard gonzalo at laptop.org
Mon Aug 5 11:53:26 EDT 2013


Where is that?

Gonzalo


On Mon, Aug 5, 2013 at 12:50 PM, Daniel Narvaez <dwnarvaez at gmail.com> wrote:

> On 5 August 2013 17:47, Gonzalo Odiard <gonzalo at laptop.org> wrote:
>
>>
>>
>> On Mon, Aug 5, 2013 at 12:36 PM, Manuel Quiñones <manuq at laptop.org>wrote:
>>
>>> Thanks for the hints Daniel,
>>>
>>> 2013/8/3 Daniel Narvaez <dwnarvaez at gmail.com>:
>>> > On 3 August 2013 02:26, Manuel Quiñones <manuq at laptop.org> wrote:
>>> >>
>>> >>
>>> >> The problem is: how could the activity process wait for the datastore
>>> >> write to finish?  If the WnckWindow close is called [1], the activity
>>> >> process ends.  Unless you connect a callback to 'delete-event' [2] and
>>> >> handle the destroy() yourself [3] .  Which is what GTK activities do
>>> >> to store before closing.
>>> >
>>> >
>>> > The shell currently does
>>> >
>>> > activity.get_window().close()
>>> >
>>> > We could
>>> >
>>> > 1 Add a close method to Activity directly. That would emit a close
>>> signal
>>> > and call get_window().close() only if the signal didn't return True.
>>>
>>>
>> Activity class already have a close method, and deal with saving.
>>
>> Or are you talking about the web activity?
>>
>
> Talking about Activity class in the shell.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20130805/07ee8fb1/attachment-0001.html>


More information about the Sugar-devel mailing list