[Sugar-devel] [ASLO] Release Measure-29
Activity Homepage: http://activities.sugarlabs.org/addon/4197 Sugar Platform: 0.82 - 0.86 Download Now: http://activities.sugarlabs.org/downloads/file/26464/measure-29.xo Release notes: * support for XO 1.5 (thanks to Sayamindu Dasgupta) Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release Scribble-1
Activity Homepage: http://activities.sugarlabs.org/addon/4242 Sugar Platform: 0.82 - 0.86 Download Now: http://activities.sugarlabs.org/downloads/file// Release notes: * First release. Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] adding 3G support to Sugar (was Re: Sugarizing an application)
On Sun, Nov 22, 2009 at 12:18:51PM -0800, Peter Robinson wrote: On Sat, Nov 21, 2009 at 3:44 AM, Jonas Smedegaard wrote: On Sat, Nov 21, 2009 at 08:14:38AM +, Peter Robinson wrote: On Sat, Nov 21, 2009 at 12:10 AM, James Cameron wrote: I think I've seen Ubuntu handling this UI design issue by building a data set of providers. It might be possible to piggy back on some of that work. Well NetworkManager in Fedora which we already use has all that support already so we don't need to piggy back off anything as the tools we use already support all of what we require. All that needs to be done is to extend the sugar interface to add the 3G support that's already in NM. If you want this for _Sugar_ then please do not just rely on a specific distro, but document in an INSTALL file what it is from that particular distro that you rely on - so that other distros can mimic that. If you are not targeting Sugar but just a specific distribution of it like, say, SoaS, then obviously you need not document anything. But it would be sad if you do not target Sugar globally. NetworkManager is distribution agnostic so its not targetted at specific distributions as NM support multiple distros undernearth. That's the advantage of it and one of the reasons its ued! I am perfectly aware that NetworkManager is cross-distro. You, not me, talked about Fedora as a reason to not depend on anything new (isn't "depend" the meaning of "piggy back"?). I simply point out a general recommendation to document whatever you choose to depend on - no matter if it is cross-platform or not. KDE is cross-platform too. You probably do not want to depend on *everything* available in Fedora, right? Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sharing in Terminal
On Sun, Nov 22, 2009 at 6:10 PM, Wade Brainerd wrote: > Hey Sayamindu, > > This sounds great to me! It was on my TODO list when I added tabs, > but I never got around to attempting it. I too like the idea of > shared tabs. > > The way I would do the UI is: > > When the Terminal activity is shared (either the Share toolbar button > has been clicked, or the activity was launched in response to an > invitation), an extra button appears in the Tabs toolbar: New Shared > Tab > > Any user can click this button; tab that is created will be visible by > all participants. The shared tab's title bar will be prefixed with > the owner's buddy name and could even display their buddy icon. That sounds pretty good. It would actually be nice to have a Shared Tab control that rendered the tab itself in XO colors, instead of just putting the XO icon inside a generic tab. Eben ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sharing in Terminal
Hey Sayamindu, This sounds great to me! It was on my TODO list when I added tabs, but I never got around to attempting it. I too like the idea of shared tabs. The way I would do the UI is: When the Terminal activity is shared (either the Share toolbar button has been clicked, or the activity was launched in response to an invitation), an extra button appears in the Tabs toolbar: New Shared Tab Any user can click this button; tab that is created will be visible by all participants. The shared tab's title bar will be prefixed with the owner's buddy name and could even display their buddy icon. -Wade On Sun, Nov 22, 2009 at 5:32 PM, Sayamindu Dasgupta wrote: > On Tue, Nov 17, 2009 at 8:09 AM, Benjamin M. Schwartz > wrote: >> Sayamindu Dasgupta wrote: >>> Hello, >>> While going through Ben Schwartz's Shared Term feature proposal >>> discussion page >>> (http://wiki.sugarlabs.org/go/Talk:Features/Terminal_Sharing), I >>> started to wonder if we could somehow implement "readonly" mode for >>> sharing in the Terminal activity. >>> After a weekend of hacking : I have managed to come up with the following: >> >> I like it. A read-only mode is definitely useful, albeit in a very >> different way from a shared interactive terminal. I couldn't figure out a >> way to grab the text from the terminal, so I ended up implementing Watch >> Me, which provides the same functionality (and much more general >> functionality), but in a much less efficient and integrated way. >> >> There are some UI things that will need to be worked out. Most obviously, >> the hidden split-screen is currently totally non-discoverable. I also >> think that N-to-N sharing might be more generally useful. For example, it >> could use the Terminal's tabs mechanism to show one tab for each user to >> all users. Perhaps both modes could be subsumed into one by providing a >> button for each user to show or hide her terminal. >> > >> I can't tell from your e-mail what is working, exactly. I think it's >> important that TUIs like nano and less work properly, as far as possible. >> For users with different screen or font sizes, some difficulty is >> inevitable. > > Thanks for the feedback. I checked with Nano and VIM and they render > fine (though a small problem is that the "action" is often hidden from > view as the initial text manipulation happens in the top of the > screen, which remains out of the viewport in the shared terminal > view). I like your ideas on utilizing the tab mechanism for N-N > sharing, since at the moment, the sharing happens blindly in 1->N > fashion from the first tab only, which I think is a bit clumsy. > > I think I'll propose read only shared terminal as a feature for 0.88 > Thanks again, > Sayamindu > > -- > Sayamindu Dasgupta > [http://sayamindu.randomink.org/ramblings] > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sharing in Terminal
Excellent ideas. I would like to see the same option for programming. There are doubtless applications for joint programming, but RO would be great for XP pair programming and for code reviews. Now if we can integrate all of this with chat...Have a look at the Write interface in Floss Manuals. http://en.flossmanuals.net/write You have to log in in order to see the chat box activated. On Mon, Nov 16, 2009 at 13:20, Sayamindu Dasgupta wrote: > Hello, > While going through Ben Schwartz's Shared Term feature proposal > discussion page > (http://wiki.sugarlabs.org/go/Talk:Features/Terminal_Sharing), I > started to wonder if we could somehow implement "readonly" mode for > sharing in the Terminal activity. > After a weekend of hacking : I have managed to come up with the following: > > * First user shares Terminal - nothing in the UI changes > * Second user joins - and gets a split screen: on the top, the shell > running in her own machine, and the lower half showing a read only > version of the Terminal Activity canvas in the first user's machine > * Third user and so forth get the same experience as the second user. > > http://people.sugarlabs.org/sayamindu/shared_terminal.ogv shows a very > barebones implementation of this. I was wondering if this would be > useful, and if so, what would be the extra UI elements ? Probably > there should be some way of showing the first user who has joined (in > the activity itself), and for the other users, there should probably > be some way to indicate/differentiate the read-only part and the > read-write part. > > Of course, this has got a lot of limitations (the major one being that > only plain text elements can be transferred, etc). I'm using the > accessibility features of the VTE widget to scrape the screen and then > sending the data across. > > Thanks, > Sayamindu > > -- > Sayamindu Dasgupta > [http://sayamindu.randomink.org/ramblings] > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Edward Mokurai (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) Cherlin Silent Thunder is my name, and Children are my nation. The Cosmos is my dwelling place, the Truth my destination. http://www.earthtreasury.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sharing in Terminal
On Tue, Nov 17, 2009 at 8:09 AM, Benjamin M. Schwartz wrote: > Sayamindu Dasgupta wrote: >> Hello, >> While going through Ben Schwartz's Shared Term feature proposal >> discussion page >> (http://wiki.sugarlabs.org/go/Talk:Features/Terminal_Sharing), I >> started to wonder if we could somehow implement "readonly" mode for >> sharing in the Terminal activity. >> After a weekend of hacking : I have managed to come up with the following: > > I like it. A read-only mode is definitely useful, albeit in a very > different way from a shared interactive terminal. I couldn't figure out a > way to grab the text from the terminal, so I ended up implementing Watch > Me, which provides the same functionality (and much more general > functionality), but in a much less efficient and integrated way. > > There are some UI things that will need to be worked out. Most obviously, > the hidden split-screen is currently totally non-discoverable. I also > think that N-to-N sharing might be more generally useful. For example, it > could use the Terminal's tabs mechanism to show one tab for each user to > all users. Perhaps both modes could be subsumed into one by providing a > button for each user to show or hide her terminal. > > I can't tell from your e-mail what is working, exactly. I think it's > important that TUIs like nano and less work properly, as far as possible. > For users with different screen or font sizes, some difficulty is inevitable. Thanks for the feedback. I checked with Nano and VIM and they render fine (though a small problem is that the "action" is often hidden from view as the initial text manipulation happens in the top of the screen, which remains out of the viewport in the shared terminal view). I like your ideas on utilizing the tab mechanism for N-N sharing, since at the moment, the sharing happens blindly in 1->N fashion from the first tab only, which I think is a bit clumsy. I think I'll propose read only shared terminal as a feature for 0.88 Thanks again, Sayamindu -- Sayamindu Dasgupta [http://sayamindu.randomink.org/ramblings] ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] adding 3G support to Sugar (was Re: Sugarizing an application)
On Sat, Nov 21, 2009 at 3:44 AM, Jonas Smedegaard wrote: > On Sat, Nov 21, 2009 at 08:14:38AM +, Peter Robinson wrote: >> >> On Sat, Nov 21, 2009 at 12:10 AM, James Cameron wrote: >>> >>> I think I've seen Ubuntu handling this UI design issue by building a data >>> set of providers. It might be possible to piggy back on some of that work. >> >> Well NetworkManager in Fedora which we already use has all that >> support already so we don't need to piggy back off anything as the >> tools we use already support all of what we require. All that needs to >> be done is to extend the sugar interface to add the 3G support that's >> already in NM. > > If you want this for _Sugar_ then please do not just rely on a specific > distro, but document in an INSTALL file what it is from that particular > distro that you rely on - so that other distros can mimic that. > > If you are not targeting Sugar but just a specific distribution of it like, > say, SoaS, then obviously you need not document anything. But it would be > sad if you do not target Sugar globally. NetworkManager is distribution agnostic so its not targetted at specific distributions as NM support multiple distros undernearth. That's the advantage of it and one of the reasons its ued! Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] .swf files visualization and bundling
Hey Rafael, Check out http://git.sugarlabs.org/projects/eatboom/repos/wadebs-clone. That project provides a template for making .SWF files into proper Sugar activities. The bundle is also available on ASLO here: http://activities.sugarlabs.org/en-US/sugar/addon/4225 EatBoom is pretty simplistic, but I'm working on porting a more advanced example. Let me know if you need any assistance with this. -Wade On Sun, Nov 22, 2009 at 2:11 AM, Rafael Enrique Ortiz Guerrero wrote: > Hi. > > I have some educational content .swf files that i wish to visualize > inside Sugar and also making a content bundle for them. > > What is the present way of doing so (both making the bundle and > visualizing .swf files) ?, we have not talked in a while about content > bundles at least that i remember ;), so please direct me to past > conversations or links about it. > > > > > Cheers and thanks in advance for your help. > Rafael Ortiz > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
