Sucrose 0.83.2 Development Release

[Simon Schampijer-2]

This is our second Development Release in the 0.84 cycle [1]. Besides
all the great bug fixing that has been going into this release we want
to highlight some interesting changes.

Some great work has been going into this release regarding the 'View
source' support. The source of all the activities can be shown, and
browse does still support showing the source of the document.

Sugar now supports setting up a priority list of languages. Not all
programs have translations for all languages. You can create a list of
languages in the Control panel that are used to display messages in
place of a non-existent translation.

More work has been going into the sugar support for NM 0.7. We finished
the support for wireless devices in the frame, updated the radio off
code in the control panel to work with NM 0.7 and added WPA support.

Three great activities are now part of fructose, the Image Viewer
activity, Turtleart and Jukebox. They have been included in
sugar-jhbuild. Give them a try!

Thanks to everyone who made this release possible!

In behalf of the sugar community,
    Your release team


[1] Sucrose Release Schedule:
http://sugarlabs.org/go/DevelopmentTeam/Release/Roadmap#Schedule

Full Release Notes:
http://sugarlabs.org/go/DevelopmentTeam/Release/Releases/Sucrose/0.83.2


-----------------------------------------------------------------------

== Glucose news ==

=== sugar-toolkit ===
* Fixed misformed plural equation (russian po)
* Add view-source-related methods HandleViewSource and GetDocumentPath

=== sugar ===
* fix uninstalling activities from the home view
* Make sugar control panel support selection of multiple languages d.l.o
* {{Bug|8876}} add saving and loading of the nm connections and support
for WPA
* Implement a global handler for the view source key
* Initial implementation of activity notifications
* d.s.o #9 wireless network frame device.
* {{Bug|8876}} Make sugar control panel support selection of multiple
languages
* d.s.o #7 update Icon in the AP palette
* {{Bug|8131}} Control Panel needs to list wireless firmware version


== Fructose news ==

=== read-activity ===
* Sugar API update: Use self.shared_activity not self._shared_activity
* Updated translation: ja
* Remove timeout hack for object picker

=== browse-activity ===
Return the document source to the shell for displaying in the view
source dialog. This is used by the new source view code to display the
document source.

=== imageviewer-activity ===
* Show an object picker if no file is specified initially
* Initial Journal support

=== turtleart-activity ===
* Turkish and Mongolian language support
* shebang patch

=== jukebox-activity ===
* Encoding error fixed for bn_IN.po
* Full Screen option
* Volume Control support
* Supporting m3u playlists
* Internet radios through m3u files.
* Next/Previous buttons , if you open a playlist with more than one song


== Fructose dependencies news ==

=== hulahop ===
* Remove flags which are breaking the build on latest libtool
* Add AC_PROG_CXX
_______________________________________________
Sugar mailing list
[hidden email]
http://lists.laptop.org/listinfo/sugar

[Tomeu Vizoso]

[cc'ing [hidden email] because this subject is of importance to
activity authors and I know many haven't yet subscribed to
[hidden email]. Please subscribe!]

On Tue, Nov 25, 2008 at 5:16 PM, Bert Freudenberg <[hidden email]> wrote:

> On 22.11.2008, at 16:35, Simon Schampijer wrote:
>
>> Some great work has been going into this release regarding the 'View
>> source' support. The source of all the activities can be shown, and
>> browse does still support showing the source of the document.
>>
>> === sugar-toolkit ===
>> * Add view-source-related methods HandleViewSource and GetDocumentPath
>>
>> === sugar ===
>> * Implement a global handler for the view source key
>
> Since I could not find any discussion, let alone documentation about
> this, I (again) got out my rusty Emacs, fed it with some grep'ed
> source files, and reverse-engineered the whole thing. My findings are
> here:

Sorry, announcing this properly is something that has been in my TODO
for a while, but hadn't managed to get to it yet.

> http://wiki.laptop.org/go/Low-level_Activity_API#D-Bus_Methods

All looks good to me.

> I like the idea so far, but here are the issues I have with the
> current implementation:
>
> 1. HandleViewSource should return a boolean to indicate whether the
> request was handled or not.
>    This would also get rid of the Python-specific dbus error handling
> code in viewsource.py because handle_view_source in activity.py could
> simply answer False.

Hmm, but we still need to handle the case where a non-python activity
hasn't implemented the method, right?

> 2. GetDocumentPath is a poor name for what it does.
>    It should contain "source" because it's not the document that is
> viewed, but its source. How about GetSourcePath()?

Well, the idea is that, by default, sugar will show the activity's
source. This method is intended for displaying a textual
representation of the sources behind a document, be it html for
browse, logo for turtleart, etc. So perhaps getDocumentSourcePath()?

>    Also, this file is deleted unconditionally when the source view is
> closed. I'd add a boolean "transfer_ownership" flag to indicate that
> it's okay to delete (similar to the datastore API).

Sounds good, if activity authors think this added complexity is ok, I
can add it.

>    Also, what kinds of source does this support? I noticed the
> Browser's HTML source was highlighted. Is that determined by the file
> name extension?

The sugar shell tries its best to display a formatted view of the
source code based on the extension and the contents of the file.
Currently, it uses gtksourceview2 for that. If an activity author
would like an improved or new formatter, we should talk to the
upstream maintainers to add it. It's quite configurable and should be
a matter of editing some xml files.

> On a more general note, activityservice.py should be annotated with
> the actual DBus signatures.

True, added it to my TODO at http://sugarlabs.org/go/User:Tomeu

Thanks,

Tomeu
_______________________________________________
Sugar mailing list
[hidden email]
http://lists.laptop.org/listinfo/sugar

[Bert Freudenberg]

On 26.11.2008, at 12:07, Tomeu Vizoso wrote:

> [cc'ing [hidden email] because this subject is of importance to
> activity authors and I know many haven't yet subscribed to
> [hidden email]. Please subscribe!]
>
> On Tue, Nov 25, 2008 at 5:16 PM, Bert Freudenberg <[hidden email]
> > wrote:
>> On 22.11.2008, at 16:35, Simon Schampijer wrote:
>>
>>> Some great work has been going into this release regarding the 'View
>>> source' support. The source of all the activities can be shown, and
>>> browse does still support showing the source of the document.
>>>
>>> === sugar-toolkit ===
>>> * Add view-source-related methods HandleViewSource and  
>>> GetDocumentPath
>>>
>>> === sugar ===
>>> * Implement a global handler for the view source key
>>
>> Since I could not find any discussion, let alone documentation about
>> this, I (again) got out my rusty Emacs, fed it with some grep'ed
>> source files, and reverse-engineered the whole thing. My findings are
>> here:
>
> Sorry, announcing this properly is something that has been in my TODO
> for a while, but hadn't managed to get to it yet.
>
>> http://wiki.laptop.org/go/Low-level_Activity_API#D-Bus_Methods
>
> All looks good to me.
>
>> I like the idea so far, but here are the issues I have with the
>> current implementation:
>>
>> 1. HandleViewSource should return a boolean to indicate whether the
>> request was handled or not.
>>   This would also get rid of the Python-specific dbus error handling
>> code in viewsource.py because handle_view_source in activity.py could
>> simply answer False.
>
> Hmm, but we still need to handle the case where a non-python activity
> hasn't implemented the method, right?

Oh certainly, the logic is sound, it's just the "not implemented"  
Pythonism there that is not necessary.

>> 2. GetDocumentPath is a poor name for what it does.
>>   It should contain "source" because it's not the document that is
>> viewed, but its source. How about GetSourcePath()?
>
> Well, the idea is that, by default, sugar will show the activity's
> source. This method is intended for displaying a textual
> representation of the sources behind a document, be it html for
> browse, logo for turtleart, etc. So perhaps getDocumentSourcePath()?

Sure.

>>   Also, this file is deleted unconditionally when the source view is
>> closed. I'd add a boolean "transfer_ownership" flag to indicate that
>> it's okay to delete (similar to the datastore API).
>
> Sounds good, if activity authors think this added complexity is ok, I
> can add it.

Well, it's more complexity to having to make a copy just so Sugar can  
delete it ...

>>   Also, what kinds of source does this support? I noticed the
>> Browser's HTML source was highlighted. Is that determined by the file
>> name extension?
>
> The sugar shell tries its best to display a formatted view of the
> source code based on the extension and the contents of the file.
> Currently, it uses gtksourceview2 for that. If an activity author
> would like an improved or new formatter, we should talk to the
> upstream maintainers to add it. It's quite configurable and should be
> a matter of editing some xml files.

Also, the call could additionally answer a mime type which would  
override the guessing.

>> On a more general note, activityservice.py should be annotated with
>> the actual DBus signatures.
>
> True, added it to my TODO at http://sugarlabs.org/go/User:Tomeu


:)

- Bert -


_______________________________________________
Sugar mailing list
[hidden email]
http://lists.laptop.org/listinfo/sugar