[Sugar-devel] Sugar-devel Digest, Vol 36, Issue 75

[Tony Anderson]

Hi,

I had hoped to use the bulletin board key as F11 (fullscreen). This 
seems easier to explain than the current F11 (lower audio volume).

Tony

On 10/27/2011 12:00 PM, sugar-devel-request at lists.sugarlabs.org wrote:
> Send Sugar-devel mailing list submissions to
> 	sugar-devel at lists.sugarlabs.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.sugarlabs.org/listinfo/sugar-devel
> or, via email, send a message with subject or body 'help' to
> 	sugar-devel-request at lists.sugarlabs.org
>
> You can reach the person managing the list at
> 	sugar-devel-owner at lists.sugarlabs.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Sugar-devel digest..."
>
>
> Today's Topics:
>
>     1. SoaSv6 - Last stages (Peter Robinson)
>     2. Re: [DESIGN TEAM] proposals for the Journal (Gonzalo Odiard)
>     3. Re: [DESIGN TEAM] proposals for the Journal (Walter Bender)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 27 Oct 2011 16:13:40 +0100
> From: Peter Robinson<pbrobinson at gmail.com>
> To: Development of live Sugar distributions
> 	<soas at lists.sugarlabs.org>,	sugar-devel at lists.sugarlabs.org
> Subject: [Sugar-devel] SoaSv6 - Last stages
> Message-ID:
> 	<CALeDE9OpM4wA3R-u26VEm29s2See2pUcCZBwM+UTZzgV=8DkBw at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi All,
>
> We're in the final stages of SoaSv6. It would be good for people to
> test and see if I've missed any issues. I believe we're in pretty good
> shape for this release. In fact I think its going to be one of our
> better releases. We've had no major breakages due to upstream this
> cycle and Fedora is locking down for the final run to release so we're
> past the possibility of that (thankfully!).
>
> To create it run the following command. Note you need to correct the
> image name for the downloaded version, and also update the device name
> for your relevant usb key.
>
> sudo livecd-iso-to-disk --format --efi Fedora-SoaS-Image-Name.iso /dev/sdz
>
> I'm interested in feedback on how it works on Intel based Mac's as the
> vast majority of Mac boot issues should be resolved with this release.
> We have a nice increase in the number of Activities shipping which
> should make it more interesting.
>
> I look forward to your feedback.
>
> Peter
>
> i386 http://koji.fedoraproject.org/koji/taskinfo?taskID=3459573
> x96-64 http://koji.fedoraproject.org/koji/taskinfo?taskID=3459574
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 27 Oct 2011 12:26:17 -0300
> From: Gonzalo Odiard<gonzalo at laptop.org>
> To: Walter Bender<walter.bender at gmail.com>
> Cc: manuel qui?ones<manuel.por.aca at gmail.com>,	Claudia Urrea
> 	<claudia at laptop.org>,	Sugar-dev Devel
> 	<sugar-devel at lists.sugarlabs.org>,	Gary C Martin
> 	<garycmartin at googlemail.com>
> Subject: Re: [Sugar-devel] [DESIGN TEAM] proposals for the Journal
> Message-ID:
> 	<CAJ+iPVR8G_XTpE9MyikgdkW8JV8hTgXMz8257u-CLSpttk5REg at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Thu, Oct 27, 2011 at 4:17 AM, Walter Bender<walter.bender at gmail.com>wrote:
>
>> Alas, I will be somewhere over the Atlantic on Monday, but I wanted to
>> plant some seeds for the discussion at the Design Team meeting. All of
>> my proposed interventions are for the Journal. I've not written up
>> formal proposals yet, but will if/when I get some traction.
>>
>> (1) Activity-specific metadata: (See
>> http://wiki.laptop.org/go/Datos_diario)  The idea is to display
>> activity-specific metadata in the expanded view of a Journal entry.
>> The Learning Team has been working on categorizing the types of data
>> they are interested in capturing. The goal is both to enhance
>> self-reflection and teacher feedback and evaluation. The mechanism I
>> mocked up in Turtle Art and in the Journal itself is quite simple. A
>> metadata dictionary entry is used to specify any metadata fields that
>> the activity would like displayed in a text box (in my mockup, this
>> box is generated on demand and positioned just below the Tags box).
>> Note that most of the data that the teachers are expressing interest
>> in capturing are correlated with button presses, so it may be
>> worthwhile considering a change to the toolkit as well, but that can
>> be a decision made at a later time.
>>
>
> +1
>
>
>>
>> (2) Audio tags: I don't have a mock up for this, but adding a simple
>> mechanism for adding audio notes to Journal items has been something I
>> have discussed with numerous teachers in the past. Lots of open
>> questions here in terms of the UI: should the recording happen in the
>> Journal or in Record? should multiple recordings be saved? append or
>> overwrite? Any size limit?
>>
>>
> Mhh, not only in the UI. Audio notes are not search friendly,
> and consume a lot of resources.
>
>
>
>> (3) Write to Journal any time: I'd like to assign a global keyboard
>> shortcut (and claim the unused bulletin board key on the XO) to jump
>> directly to the expanded entry for whatever activity is currently
>> active. In addition, it would be worth considering a button on the
>> activity toolbar (grabbing the space opened up by the removal of the
>> Keep button). Rationale: make it easier to get to your "lab notebook"
>> to make annotations relevant to your project.
>>
>>
> +1
>
>
>> (4) Activity-specific folders mounted in the volumes toolbar: A simple
>> way to handle the issue of activities that use clipart, sample
>> code/projects, etc. We had discussed before the idea of loading these
>> objects directly into the Journal, but this is IMHO too difficult to
>> manage. By letting an activity specify a directory (or directories) to
>> mount on the volumes toolbar would make it possible to use the Sugar
>> Chooser to access activity-specific data. We could restrict it to
>> subdirectories of the bundle path to maintain some level of security.
>> We could also use it to share clipart among activities.
>>
>>
> +1
>
> Would be good if we can have feedback about UI changes proposed to Journal
> http://wiki.sugarlabs.org/go/Journal_NewUI
> Martin Abente already worked in multiple file operations, a much requested
> feature,
> and the proposal want do the use of tags more useful.
>
> Gonzalo
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:<http://lists.sugarlabs.org/archive/sugar-devel/attachments/20111027/4e5f6d02/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 27 Oct 2011 11:32:17 -0400
> From: Walter Bender<walter.bender at gmail.com>
> To: Gonzalo Odiard<gonzalo at laptop.org>
> Cc: manuel qui?ones<manuel.por.aca at gmail.com>,	Claudia Urrea
> 	<claudia at laptop.org>,	Sugar-dev Devel
> 	<sugar-devel at lists.sugarlabs.org>,	Gary C Martin
> 	<garycmartin at googlemail.com>
> Subject: Re: [Sugar-devel] [DESIGN TEAM] proposals for the Journal
> Message-ID:
> 	<CADf7C8sKC1n1M-Q4r7R7J+NNvEfaf17tsWOn-VmTGgOg9YdWnw at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Thu, Oct 27, 2011 at 11:26 AM, Gonzalo Odiard<gonzalo at laptop.org>  wrote:
>>
>>
>> On Thu, Oct 27, 2011 at 4:17 AM, Walter Bender<walter.bender at gmail.com>
>> wrote:
>>>
>>> Alas, I will be somewhere over the Atlantic on Monday, but I wanted to
>>> plant some seeds for the discussion at the Design Team meeting. All of
>>> my proposed interventions are for the Journal. I've not written up
>>> formal proposals yet, but will if/when I get some traction.
>>>
>>> (1) Activity-specific metadata: (See
>>> http://wiki.laptop.org/go/Datos_diario) ?The idea is to display
>>> activity-specific metadata in the expanded view of a Journal entry.
>>> The Learning Team has been working on categorizing the types of data
>>> they are interested in capturing. The goal is both to enhance
>>> self-reflection and teacher feedback and evaluation. The mechanism I
>>> mocked up in Turtle Art and in the Journal itself is quite simple. A
>>> metadata dictionary entry is used to specify any metadata fields that
>>> the activity would like displayed in a text box (in my mockup, this
>>> box is generated on demand and positioned just below the Tags box).
>>> Note that most of the data that the teachers are expressing interest
>>> in capturing are correlated with button presses, so it may be
>>> worthwhile considering a change to the toolkit as well, but that can
>>> be a decision made at a later time.
>>
>> +1
>>
>>>
>>> (2) Audio tags: I don't have a mock up for this, but adding a simple
>>> mechanism for adding audio notes to Journal items has been something I
>>> have discussed with numerous teachers in the past. Lots of open
>>> questions here in terms of the UI: should the recording happen in the
>>> Journal or in Record? should multiple recordings be saved? append or
>>> overwrite? Any size limit?
>>>
>>
>> Mhh, not only in the UI. Audio notes are not search friendly,
>> and consume a lot of resources.
>
> This is one reason I think we should put a severe restriction on the
> size. But there are lots of requests for such functionality. But not
> as pressing IMHO as the other features I have outlined.
>
>>
>>
>>>
>>> (3) Write to Journal any time: I'd like to assign a global keyboard
>>> shortcut (and claim the unused bulletin board key on the XO) to jump
>>> directly to the expanded entry for whatever activity is currently
>>> active. In addition, it would be worth considering a button on the
>>> activity toolbar (grabbing the space opened up by the removal of the
>>> Keep button). Rationale: make it easier to get to your "lab notebook"
>>> to make annotations relevant to your project.
>>>
>>
>> +1
>>
>>>
>>> (4) Activity-specific folders mounted in the volumes toolbar: A simple
>>> way to handle the issue of activities that use clipart, sample
>>> code/projects, etc. We had discussed before the idea of loading these
>>> objects directly into the Journal, but this is IMHO too difficult to
>>> manage. By letting an activity specify a directory (or directories) to
>>> mount on the volumes toolbar would make it possible to use the Sugar
>>> Chooser to access activity-specific data. We could restrict it to
>>> subdirectories of the bundle path to maintain some level of security.
>>> We could also use it to share clipart among activities.
>>>
>>
>> +1
>>
>> Would be good if we can have feedback about UI changes proposed to Journal
>> http://wiki.sugarlabs.org/go/Journal_NewUI
>> Martin Abente already worked in multiple file operations, a much requested
>> feature,
>> and the proposal want do the use of tags more useful.
>
> Should we not take all of these ideas and put them into the wiki under
> feature requests?
>
> http://wiki.sugarlabs.org/go/Features
>
> regards.
>
> -walter
>
>>
>> Gonzalo
>>
>>
>
>
>