[Sugar-devel] New Chapter in Make Your Own Sugar Activities needs review

[James Simmons]

Bert,

I could have done it that way, but the whole point of Sugar Commander
is to update the metadata for an entry.  If someone adds or removes a
Journal object I definitely want to know about it, but if someone
updates an entry I may have unsaved changes that I don't want to lose.

Sugar is a single-user environment and it actually takes some effort
to update the Journal while Sugar-Commander is running.  It's much
more difficult than it would be in a windowed UI.  For that reason it
seemed reasonable to ignore updates to the Journal entries outside of
Sugar-Commander.

When I select a Journal entry in the list I get the latest entry from
the datastore.

I'll think some more about changing this, but that will wait for version 3.

James Simmons


> Date: Tue, 30 Mar 2010 17:16:50 +0200
> From: Bert Freudenberg <bert at freudenbergs.de>
> Subject: Re: [Sugar-devel] New Chapter in Make Your Own Sugar
>        Activities      needs review
> To: Sugar Devel <sugar-devel at lists.sugarlabs.org>
> Message-ID: <983200AA-E943-44BB-A7BF-31AB9C655802 at freudenbergs.de>
> Content-Type: text/plain; charset=us-ascii
>
>
> I'd have expected the "Updated" signal to be used like this:
>
>    def _datastore_updated_cb(self,  uid):
>        if uid == jobject.object_id:
>            self.update_details()
>
> where update_details() would be factored out from the body of selection_journal_cb() ...
>
> - Bert -