Re: [Sugar-devel] Add ability to record to Speak?
On Fri, Jul 10, 2009 at 06:22, Aleksey Limalsr...@member.fsf.org wrote: On Thu, Jul 09, 2009 at 11:50:20PM -0300, Muriel de Souza Godoi wrote: Hi all, I've been away from Sugar for a long time... but keep reading the mailing lists :) I will be on vacation until July 20th, but after that I can face this as a new effort to help Sugar What about a different approach? Add the speak capability to memorize... Can memorize just use the speak library and pronounce the cards? What do you think? I'm sure thats the way to go: * adding record feature to Speak can increase complexity of Speak UI * using speak synth feature in Memorize means not using extra resources for storing audio files * and Caroline is right, speaking faces will look really funny +1 Welcome back, Muriel! Regards, Tomeu Thanks -- Aleksey ___ 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] Nobody understands Keep
On Fri, Jul 10, 2009 at 05:41, Eben Eliasone...@laptop.org wrote: On Thu, Jul 9, 2009 at 7:55 PM, Eduardo H. Silvahoboprim...@gmail.com wrote: 2009/7/9 Tomeu Vizoso to...@sugarlabs.org: On Thu, Jul 9, 2009 at 12:29, Martin Denglermar...@martindengler.com wrote: On Thu, Jul 09, 2009 at 11:22:16AM +0100, Daniel Drake wrote: On Thu, 2009-07-09 at 10:45 +0100, Martin Dengler wrote: On Thu, Jul 09, 2009 at 09:52:23AM +0100, Daniel Drake wrote: Nobody in the world seems to understand the Keep button. People think it's for regular saving and you should do it before you close or switch away from your activity. That's not far from the truth, right? At least in any work-losing or surprising way... It's far from the truth in that it's not normally what you want to do. My quoting-foo is bad, so I've caused confusion (in myself, too :)). To save your work, simply click the Stop button or change so that another activity has focus. If you click Keep, you'll end up with 2 copies - one from when you clicked Keep, and one from when you clicked Stop (or focused on another activity). As far as I understand it, Keep is useful for these types of scenarios: - you've done a lot of work but now it's time to refactor/reorganize the whole thing. However you want to keep a copy of the rough version you have now, as insurance or perhaps for reference while you re-mangle the work. - you've made a template for something, now you want to save that template (as a blank template) before starting on a version where you fill in the content. This is a great explanation -- it should be in the HIG or something. But the biggest problem is how do we explain this to users without them having to read the HIG (or manual)? Should be called Keep a copy? +1 For a while, in the pt_PT translation of Sugar I did, I named the Keep button as Keep a copy. I urge again that keep a copy is not what is intended, in the long run. Without proper versions, of course, this is effectively how it behaves. Therefore, it's no surprise many saw it this way. But with versions, the keep button is actually a keep new version button. As mentioned before, a new version retains the tree_id, whereas a true copy does not. But are you meaning that we should name the current one Keep a copy and when we have versions add Keep? Regards, Tomeu Since versions are on the way, we should make sure to clarify the distinction! Eben Regards, Tomeu Daniel Martin ___ 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 ___ 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] Nobody understands Keep
On Fri, Jul 10, 2009 at 5:28 AM, Tomeu Vizosoto...@sugarlabs.org wrote: On Fri, Jul 10, 2009 at 05:41, Eben Eliasone...@laptop.org wrote: On Thu, Jul 9, 2009 at 7:55 PM, Eduardo H. Silvahoboprim...@gmail.com wrote: 2009/7/9 Tomeu Vizoso to...@sugarlabs.org: On Thu, Jul 9, 2009 at 12:29, Martin Denglermar...@martindengler.com wrote: On Thu, Jul 09, 2009 at 11:22:16AM +0100, Daniel Drake wrote: On Thu, 2009-07-09 at 10:45 +0100, Martin Dengler wrote: On Thu, Jul 09, 2009 at 09:52:23AM +0100, Daniel Drake wrote: Nobody in the world seems to understand the Keep button. People think it's for regular saving and you should do it before you close or switch away from your activity. That's not far from the truth, right? At least in any work-losing or surprising way... It's far from the truth in that it's not normally what you want to do. My quoting-foo is bad, so I've caused confusion (in myself, too :)). To save your work, simply click the Stop button or change so that another activity has focus. If you click Keep, you'll end up with 2 copies - one from when you clicked Keep, and one from when you clicked Stop (or focused on another activity). As far as I understand it, Keep is useful for these types of scenarios: - you've done a lot of work but now it's time to refactor/reorganize the whole thing. However you want to keep a copy of the rough version you have now, as insurance or perhaps for reference while you re-mangle the work. - you've made a template for something, now you want to save that template (as a blank template) before starting on a version where you fill in the content. This is a great explanation -- it should be in the HIG or something. But the biggest problem is how do we explain this to users without them having to read the HIG (or manual)? Should be called Keep a copy? +1 For a while, in the pt_PT translation of Sugar I did, I named the Keep button as Keep a copy. I urge again that keep a copy is not what is intended, in the long run. Without proper versions, of course, this is effectively how it behaves. Therefore, it's no surprise many saw it this way. But with versions, the keep button is actually a keep new version button. As mentioned before, a new version retains the tree_id, whereas a true copy does not. But are you meaning that we should name the current one Keep a copy and when we have versions add Keep? No, no. I'm urging that we name it Keep new version now if we rename it, so that it's meaning doesn't change down the road when versions are introduced. Eben Regards, Tomeu Since versions are on the way, we should make sure to clarify the distinction! Eben Regards, Tomeu Daniel Martin ___ 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 ___ 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] Nobody understands Keep
On Fri, Jul 10, 2009 at 10:01:19AM -0400, Eben Eliason wrote: On Fri, Jul 10, 2009 at 5:28 AM, Tomeu Vizosoto...@sugarlabs.org wrote: But are you meaning that we should name the current one Keep a copy and when we have versions add Keep? No, no. I'm urging that we name it Keep new version now if we rename it, so that it's meaning doesn't change down the road when versions are introduced. Keep new version seems a lot closer to a description of the implementation than of the user-desired result. Unless this new version becomes the active one (i.e., the one upon which the user continues to work, assuming they don't close the application), isn't the result of the button press better called Keep[ing of a] backup version? Regards, Tomeu Eben pgpXqzVGqhDb4.pgp Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Nobody understands Keep
Eben Eliason wrote: No, no. I'm urging that we name it Keep new version now if we rename it, so that it's meaning doesn't change down the road when versions are introduced. We should call it Checkpoint and let the localization teams sort it out. The English-speakers will have no problem understanding what it means; they've been playing video games with checkpoints for their whole lives. --Ben signature.asc Description: OpenPGP digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Nobody understands Keep
On Fri, Jul 10, 2009 at 10:05 AM, Martin Denglermar...@martindengler.com wrote: On Fri, Jul 10, 2009 at 10:01:19AM -0400, Eben Eliason wrote: On Fri, Jul 10, 2009 at 5:28 AM, Tomeu Vizosoto...@sugarlabs.org wrote: But are you meaning that we should name the current one Keep a copy and when we have versions add Keep? No, no. I'm urging that we name it Keep new version now if we rename it, so that it's meaning doesn't change down the road when versions are introduced. Keep new version seems a lot closer to a description of the implementation than of the user-desired result. Unless this new version becomes the active one (i.e., the one upon which the user continues to work, assuming they don't close the application), isn't the result of the button press better called Keep[ing of a] backup version? I'm happy to entertain other terminology. All I'm really trying to get across is that, technically, this action is strictly not what I interpreted as keep a copy in the presence of versions, and I don't want to confuse the terminology later by mixing up the terms. I'd be equally satisfied, I think, by finding a better term for what I'm presently describing as keep a copy, wherein a brand new tree_id is assigned to the copy, detaching it from the history (and collaboration scope) of the original. The fundamental issue is whether or not version/collaboration history is retained with the action, so let's ensure that we name both of these types of copy operations at the same time, even if we only have one of them for now, so that it can be extended later. Ben's suggestion of checkpoint could work. Perhaps Keep checkpoint would be better to retain the action. You're right that it's more like keep backup versionthat is, the keep operation which retains the tree_id basically writes the current state of the activity as a version (the just-now-previous one), and allows you to continue working in the most current one. No branching, in the traditional sense, happens here. Eben Regards, Tomeu Eben ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Nobody understands Keep
On Fri, Jul 10, 2009 at 16:25, Eben Eliasone...@laptop.org wrote: On Fri, Jul 10, 2009 at 10:05 AM, Martin Denglermar...@martindengler.com wrote: On Fri, Jul 10, 2009 at 10:01:19AM -0400, Eben Eliason wrote: On Fri, Jul 10, 2009 at 5:28 AM, Tomeu Vizosoto...@sugarlabs.org wrote: But are you meaning that we should name the current one Keep a copy and when we have versions add Keep? No, no. I'm urging that we name it Keep new version now if we rename it, so that it's meaning doesn't change down the road when versions are introduced. Keep new version seems a lot closer to a description of the implementation than of the user-desired result. Unless this new version becomes the active one (i.e., the one upon which the user continues to work, assuming they don't close the application), isn't the result of the button press better called Keep[ing of a] backup version? I'm happy to entertain other terminology. All I'm really trying to get across is that, technically, this action is strictly not what I interpreted as keep a copy in the presence of versions, and I don't want to confuse the terminology later by mixing up the terms. I'd be equally satisfied, I think, by finding a better term for what I'm presently describing as keep a copy, wherein a brand new tree_id is assigned to the copy, detaching it from the history (and collaboration scope) of the original. The fundamental issue is whether or not version/collaboration history is retained with the action, so let's ensure that we name both of these types of copy operations at the same time, even if we only have one of them for now, so that it can be extended later. Ben's suggestion of checkpoint could work. Perhaps Keep checkpoint would be better to retain the action. You're right that it's more like keep backup versionthat is, the keep operation which retains the tree_id basically writes the current state of the activity as a version (the just-now-previous one), and allows you to continue working in the most current one. No branching, in the traditional sense, happens here. Should we discuss this in sugar-devel? Why not asking any of the teachers in IAEP what is more natural for them? Regards, Tomeu Eben Regards, Tomeu Eben ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Nobody understands Keep
On Fri, Jul 10, 2009 at 10:29 AM, Tomeu Vizosoto...@sugarlabs.org wrote: On Fri, Jul 10, 2009 at 16:25, Eben Eliasone...@laptop.org wrote: On Fri, Jul 10, 2009 at 10:05 AM, Martin Denglermar...@martindengler.com wrote: On Fri, Jul 10, 2009 at 10:01:19AM -0400, Eben Eliason wrote: On Fri, Jul 10, 2009 at 5:28 AM, Tomeu Vizosoto...@sugarlabs.org wrote: But are you meaning that we should name the current one Keep a copy and when we have versions add Keep? No, no. I'm urging that we name it Keep new version now if we rename it, so that it's meaning doesn't change down the road when versions are introduced. Keep new version seems a lot closer to a description of the implementation than of the user-desired result. Unless this new version becomes the active one (i.e., the one upon which the user continues to work, assuming they don't close the application), isn't the result of the button press better called Keep[ing of a] backup version? I'm happy to entertain other terminology. All I'm really trying to get across is that, technically, this action is strictly not what I interpreted as keep a copy in the presence of versions, and I don't want to confuse the terminology later by mixing up the terms. I'd be equally satisfied, I think, by finding a better term for what I'm presently describing as keep a copy, wherein a brand new tree_id is assigned to the copy, detaching it from the history (and collaboration scope) of the original. The fundamental issue is whether or not version/collaboration history is retained with the action, so let's ensure that we name both of these types of copy operations at the same time, even if we only have one of them for now, so that it can be extended later. Ben's suggestion of checkpoint could work. Perhaps Keep checkpoint would be better to retain the action. You're right that it's more like keep backup versionthat is, the keep operation which retains the tree_id basically writes the current state of the activity as a version (the just-now-previous one), and allows you to continue working in the most current one. No branching, in the traditional sense, happens here. Should we discuss this in sugar-devel? Why not asking any of the teachers in IAEP what is more natural for them? Makes sense to me, as long as we can convey to them first the distinction between the two. The problem at hand is that keep a copy makes perfect sense, until you toss in this alternate action to confuse things. As another note, I have another reason why I interpreted keep a copy to mean new tree_id, and not just new version. Looking at the design mockups for the action/object views of the Journal, we designed the object view to show only the most recent version of any object. That is, each object is represented just once in that list. Here, it seems like keep a copy should mean give me a new object in this list; Keeping a version is just an action which snapshots a previous state of the current object, without making a true copy of it. Maybe we could always refer to versions as history in Sugar (seems logical, given the Journal metaphor!). Then, we could call what the new tree_id case keep a copy as I initially suggested, and the new version_id case keep in history, to indicate that pressing it will add a new listing in the history of the current object. Eben Regards, Tomeu Eben Regards, Tomeu Eben ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] GPA curriculum
Hi Caroline, Can you send over any details you have on the curriculum at GPA? Anything covering what the teachers are trying to teach and what they are doing outside the computer lab will be very helpful. I want to try and tie the learning goals of the teachers back to the SW as concretely as possible. I'm hesitant to add work to your pile so let me know if there's any way I can help gather, record or disseminate that information. Thanks, Greg S ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] GPA curriculum
Getting more info on curriclum is on my agenda for Tuesday afternoon can you stay after class and join me? I want to focus on the 3rd grade curriclum on tuesday. 2 nd grade theme is community and math they study clocks so we will make a clock in turtle art Sent from my iPhone Caroline Meeks 617-395-7966 On Jul 10, 2009, at 10:57 AM, Greg Smith gregsmit...@gmail.com wrote: Hi Caroline, Can you send over any details you have on the curriculum at GPA? Anything covering what the teachers are trying to teach and what they are doing outside the computer lab will be very helpful. I want to try and tie the learning goals of the teachers back to the SW as concretely as possible. I'm hesitant to add work to your pile so let me know if there's any way I can help gather, record or disseminate that information. Thanks, Greg S ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Initial implementation of toolbars design
Hi all, http://git.sugarlabs.org/projects/sugar-toolkit/repos/toolbars there is simle example in examples/toolbar.py Does it satisfy mockups? -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [RELEASE] sugar-toolkit-0.85.1
== Source ==
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.85.1.tar.bz2
== Fixed tickets ==
* #757 telepathy_room_handle unused and unusable
* #610 Journal Palette does not manage too many characters for a title correctly
* #635 bundlebuilder.list_files drops first character of file names if base_dir
has trailing slash
* #428 connect('map') to activity widow not to current canvas
* #428 connect('map') to activity widow not to current canvas
* #647 git-ls-files does not work with newer Git
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [RELEASE] hulahop-0.5.0
== Source == http://download.sugarlabs.org/sources/sucrose/glucose/hulahop/hulahop-0.5.0.tar.bz2 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [RELEASE] sugar-0.85.1
== Source == http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.85.1.tar.bz2 == News == * Switch to metacity as the window manager * Refactor journal to use a gtk.TreeView * Display tags in the activity list * Change activity list to use a gtk.TreeView * Hold a reference to the monitors so don't get disposed (gio) * More meaningful screenshot titles #650 * Creating ad-hoc wireless networks * Add fullscreen option to the emulator and change default size to 800x600 #565 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [RELEASE] Browse-109
== Source == http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-109.tar.bz2 == Fixed tickets == * Open new windows in tabs * Put the download url in the description field of the metadata ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [RELEASE] Log-19
== Source == http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-19.tar.bz2 == Fixed tickets == * Hold a reference to the monitors so they don't get disposed #957 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Sugar as desktop os
I am looking into implenting sugar for a Montessori school. The current plan is to start with 10 to 20 (depending on budget) computers for a group of about 100 students from 6 to 13, and usage would be on a rotating basis by groups. At this stage, there is no plan to supply each child with a computer. On the other hand, if this implementation is reasonably successful then the school will probably recommend that parents buy computers for their children. As things stand now what I was hoping to do is : - Install Sugar on each computer as the main OS. - Setup a server to hold the kids' home directories and provide other services as needed (routing and chat among other things...). I am familiar with the XO and I have downloaded Sugar on a Stick to try it out. My first problem with SaoS is that there is no easy way to install the OS on a hard disk. By easy, I mean something like a) boot the stick, b) click on install to hard disk, or something equivalent. (As a side note, SaoS includes none of the sound/music applications! That's a huge loss!) I looked at the distributions I use, Debian and Ubuntu, and at Fedora because Sugar is derived from it. All three seem to have small problems. In addition it seems that they all require a sugar- emulator and it's not clear to me what is being emulated. I'm on a short schedule (only 4/6 weeks to procure and setup) so I am looking for quick answers to avoid blind alleys while doing the necessary research. Any comments/pointers welcome. Mostly I think what I'd like to know is whether what I'm thinking of is even possible. Specifically, is it possible and how difficult would it be to have share use of a computer with Sugar as the only desktop OS? Thanks in advance! Note: The hardware I am looking at is the HP Mini 110 Mi and the System76 Starling Netbook. -- Philippe -- The trouble with common sense is that it is so uncommon. Anonymous ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar as desktop os
2009/7/10 Philippe Clérié phili...@gcal.net: I am looking into implenting sugar for a Montessori school. The current plan is to start with 10 to 20 (depending on budget) computers for a group of about 100 students from 6 to 13, and usage would be on a rotating basis by groups. At this stage, there is no plan to supply each child with a computer. On the other hand, if this implementation is reasonably successful then the school will probably recommend that parents buy computers for their children. As things stand now what I was hoping to do is : - Install Sugar on each computer as the main OS. - Setup a server to hold the kids' home directories and provide other services as needed (routing and chat among other things...). I am familiar with the XO and I have downloaded Sugar on a Stick to try it out. My first problem with SaoS is that there is no easy way to install the OS on a hard disk. By easy, I mean something like a) boot the stick, b) click on install to hard disk, or something equivalent. (As a side note, SaoS includes none of the sound/music applications! That's a huge loss!) I looked at the distributions I use, Debian and Ubuntu, and at Fedora because Sugar is derived from it. All three seem to have small problems. In addition it seems that they all require a sugar- emulator and it's not clear to me what is being emulated. I'm on a short schedule (only 4/6 weeks to procure and setup) so I am looking for quick answers to avoid blind alleys while doing the necessary research. Any comments/pointers welcome. Mostly I think what I'd like to know is whether what I'm thinking of is even possible. Specifically, is it possible and how difficult would it be to have share use of a computer with Sugar as the only desktop OS? I think you might want to try Fedora 11, and install the sugar-desktop package, if you have not already tried it. This should give you a sugar login session option and should be similar to what SoaS is running. Dave Thanks in advance! Note: The hardware I am looking at is the HP Mini 110 Mi and the System76 Starling Netbook. -- Philippe -- The trouble with common sense is that it is so uncommon. Anonymous ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Dave Bauer d...@solutiongrove.com http://www.solutiongrove.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar as desktop os
2009/7/10 Philippe Clérié phili...@gcal.net Specifically, is it possible and how difficult would it be to have share use of a computer with Sugar as the only desktop OS? Trivial, if you use fedora as Dave said. You can create an account for each user and have them log in using GDM or another session manager, which would load Sugar as the session. Where are you located? -- Luke Faraone http://luke.faraone.cc ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar as desktop os
On 07/10/2009 07:09 PM, Philippe Clérié wrote: I am looking into implenting sugar for a Montessori school. The current plan is to start with 10 to 20 (depending on budget) computers for a group of about 100 students from 6 to 13, and usage would be on a rotating basis by groups. At this stage, there is no plan to supply each child with a computer. On the other hand, if this implementation is reasonably successful then the school will probably recommend that parents buy computers for their children. As things stand now what I was hoping to do is : - Install Sugar on each computer as the main OS. - Setup a server to hold the kids' home directories and provide other services as needed (routing and chat among other things...). I am familiar with the XO and I have downloaded Sugar on a Stick to try it out. My first problem with SaoS is that there is no easy way to install the OS on a hard disk. By easy, I mean something like a) boot the stick, b) click on install to hard disk, or something equivalent. (As a side note, SaoS includes none of the sound/music applications! That's a huge loss!) I looked at the distributions I use, Debian and Ubuntu, and at Fedora because Sugar is derived from it. All three seem to have small problems. In addition it seems that they all require a sugar- emulator and it's not clear to me what is being emulated. I'm on a short schedule (only 4/6 weeks to procure and setup) so I am looking for quick answers to avoid blind alleys while doing the necessary research. Any comments/pointers welcome. Mostly I think what I'd like to know is whether what I'm thinking of is even possible. Specifically, is it possible and how difficult would it be to have share use of a computer with Sugar as the only desktop OS? Thanks in advance! Note: The hardware I am looking at is the HP Mini 110 Mi and the System76 Starling Netbook. Hi Philippe, I am doing the same thing in my pilot in a school here in Berlin. I use Fedora as OS, and do yum groupinstall sugar-desktop. You can then log into Sugar as an alternate desktop (in gdm login after typing the user you can select the session at the bottom). No need for the emulation. I have a server that provides the authentication via openldap and the home folders are mounted via NFS. Even though I will have local installations (the OS) on each machine - the authentication will happen at the server. So this is one scenario. Otherwise you can use thin clients and LTSP. Hope this helps - will share more info as I go in my blog, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar as desktop os
2009/7/10 Philippe Clérié phili...@gcal.net: I am looking into implenting sugar for a Montessori school. Maria would be so pleased. +1 Where is your school? Is there a Sugar/XO user group nearby? The current plan is to start with 10 to 20 (depending on budget) computers for a group of about 100 students from 6 to 13, and usage would be on a rotating basis by groups. At this stage, there is no plan to supply each child with a computer. On the other hand, if this implementation is reasonably successful then the school will probably recommend that parents buy computers for their children. I would suggest getting donations of 100 computers, and providing Sugar on a Stick to every student. That way, they could continue at home. Talk to any computer recycler about taking systems with no hard drive, and to any Linux User Group that does Installfests. As things stand now what I was hoping to do is : - Install Sugar on each computer as the main OS. - Setup a server to hold the kids' home directories and provide other services as needed (routing and chat among other things...). I am familiar with the XO and I have downloaded Sugar on a Stick to try it out. My first problem with SaoS is that there is no easy way to install the OS on a hard disk. By easy, I mean something like a) boot the stick, b) click on install to hard disk, or something equivalent. That's the hard way. Use a package manager like Synaptic to install Sugar. You will get more Activities that way. or yum install sugar (Fedora) apt-get install sugar (Debian, Ubuntu) (As a side note, SaoS includes none of the sound/music applications! That's a huge loss!) Jukebox is included but not selected as a Favorite. There is a technical discussion going on about sound in SoaS. When it is finished, you can expect to see more. I looked at the distributions I use, Debian and Ubuntu, and at Fedora because Sugar is derived from it. All three seem to have small problems. If so, please check and if necessary file bug reports. We'll help you. The only issue I am aware of is that Sugar is broken in Ubuntu Jaunty. What problems do you see? In addition it seems that they all require a sugar- emulator and it's not clear to me what is being emulated. It's just the name of the program that starts everything. It is in a sense emulating an XO within a separate X session. But it isn't the fake version of some original that we're hiding from you. :) I'm on a short schedule (only 4/6 weeks to procure and setup) so I am looking for quick answers to avoid blind alleys while doing the necessary research. Any comments/pointers welcome. Mostly I think what I'd like to know is whether what I'm thinking of is even possible. Specifically, is it possible There are some issues in configuring a school server that you will need to ask about. We need the experts to write a procedure for a reasonable configuration with Jabber and Moodle, and put it into the Wiki. and how difficult would it be to have share use of a computer with Sugar as the only desktop OS? It is of course possible. But it is like sharing one pencil among five or ten students. You can't integrate it into a curriculum. This may not be so bad in a Montessori environment, where children don't all work on the same topic together. So if some children are using the traditional Montessori equipment, and some the computer, you will no doubt find a balance. I will be interested to know what balance point the children come to. It will no doubt vary by age and perhaps other factors. That information would be worth an article in one of the Montessori publications. I volunteer to write it if you and the teachers are willing to collect the data. Thanks in advance! Note: The hardware I am looking at is the HP Mini 110 Mi and the System76 Starling Netbook. More than adequate. -- Philippe -- The trouble with common sense is that it is so uncommon. Anonymous +1 -- Silent Thunder (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) is my name And Children are my nation. The Cosmos is my dwelling place, The Truth my destination. http://earthtreasury.org/worknet (Edward Mokurai Cherlin) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Sugar as desktop os
2009/7/10 Edward Cherlin echer...@gmail.com In addition it seems that they all require a sugar- emulator and it's not clear to me what is being emulated. It's just the name of the program that starts everything. It is in a sense emulating an XO within a separate X session. But it isn't the fake version of some original that we're hiding from you. :) To be clear, no software is being emulated; sugar-emulator simply lets sugar run inside a self-contained window so as to not mess up the display of your normal desktop. -- Luke Faraone http://luke.faraone.cc ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar as desktop os
We're located in Haiti. Sorry I left that off. And before anyone asks :-) we're not part of the pilot that was scheduled to begin in Haiti last year. I briefly worked with them. As far as I can tell, after the last cabinet shuffle, the project has gone dormant. Officially, I don't know why. Unofficially, the new Minister of Education does not like anything started by the previous one. Or so it seems. And thanks everyone for the responses. That was quite a few in such a short span of time. I am now quite sure I can make it happen. This may not be so bad in a Montessori environment, where children don't all work on the same topic together. So if some children are using the traditional Montessori equipment, and some the computer, you will no doubt find a balance. That's the plan. Use the computer as _just_ another montessori equipment/exercise. One problem is that while I have the computer expertise, I know next to nothing about education, and those who have that expertise are somewhat afraid? of the computer. Has there been any documented experience in a Montessori environment? It seems to me that there is a lot of soul searching but not much hard data. I will be interested to know what balance point the children come to. It will no doubt vary by age and perhaps other factors. That information would be worth an article in one of the Montessori publications. I volunteer to write it if you and the teachers are willing to collect the data. LOL! Get in line! But let's see what we can do. I certainly plan to document what I do on the computer side. -- Philippe -- The trouble with common sense is that it is so uncommon. Anonymous On Friday 10 July 2009 12:48:18 Edward Cherlin wrote: 2009/7/10 Philippe Clérié phili...@gcal.net: I am looking into implenting sugar for a Montessori school. Maria would be so pleased. +1 Where is your school? Is there a Sugar/XO user group nearby? The current plan is to start with 10 to 20 (depending on budget) computers for a group of about 100 students from 6 to 13, and usage would be on a rotating basis by groups. At this stage, there is no plan to supply each child with a computer. On the other hand, if this implementation is reasonably successful then the school will probably recommend that parents buy computers for their children. I would suggest getting donations of 100 computers, and providing Sugar on a Stick to every student. That way, they could continue at home. Talk to any computer recycler about taking systems with no hard drive, and to any Linux User Group that does Installfests. As things stand now what I was hoping to do is : - Install Sugar on each computer as the main OS. - Setup a server to hold the kids' home directories and provide other services as needed (routing and chat among other things...). I am familiar with the XO and I have downloaded Sugar on a Stick to try it out. My first problem with SaoS is that there is no easy way to install the OS on a hard disk. By easy, I mean something like a) boot the stick, b) click on install to hard disk, or something equivalent. That's the hard way. Use a package manager like Synaptic to install Sugar. You will get more Activities that way. or yum install sugar (Fedora) apt-get install sugar (Debian, Ubuntu) (As a side note, SaoS includes none of the sound/music applications! That's a huge loss!) Jukebox is included but not selected as a Favorite. There is a technical discussion going on about sound in SoaS. When it is finished, you can expect to see more. I looked at the distributions I use, Debian and Ubuntu, and at Fedora because Sugar is derived from it. All three seem to have small problems. If so, please check and if necessary file bug reports. We'll help you. The only issue I am aware of is that Sugar is broken in Ubuntu Jaunty. What problems do you see? In addition it seems that they all require a sugar- emulator and it's not clear to me what is being emulated. It's just the name of the program that starts everything. It is in a sense emulating an XO within a separate X session. But it isn't the fake version of some original that we're hiding from you. :) I'm on a short schedule (only 4/6 weeks to procure and setup) so I am looking for quick answers to avoid blind alleys while doing the necessary research. Any comments/pointers welcome. Mostly I think what I'd like to know is whether what I'm thinking of is even possible. Specifically, is it possible There are some issues in configuring a school server that you will need to ask about. We need the experts to write a procedure for a reasonable configuration with Jabber and Moodle, and put it into the Wiki. and how difficult would it be to have share use of a computer with Sugar as the only desktop OS? It is of course possible. But it is like sharing one pencil among five or ten students. You can't
[Sugar-devel] [RELEASE] sugar-toolkit-0.84.5
== Source == http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.84.5.tar.bz2 == News == Fix ContentBundle bundle_id Most content bundles use global_name as the ID-style thing, as suggested on the OLPC wiki. bundle_class seems undocumented and hence is not present in any of the content bundles I have here. Change get_bundle_id() to fall back on the global_name if no bundle_class is set. This fixes a complete sugar crash when installing the standard content bundles (it tried to send a None value over dbus). ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] Building strawberry from git
On Fri, Jul 10, 2009 at 8:23 PM, Andrés Arrieta Perréardandres.ap.li...@gmail.com wrote: So I tried the following: Waited some time and ran things with no mods getting the libabiword dependency error: http://fpaste.org/paste/18026 Then Added the updates and updates testing getting a *debug error, and with pyabiword again: http://fpaste.org/paste/18055 Then commented the rawhide line and adding: repo --name=F11 --cost=10 --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-11arch=i386 Resulting in the b43-bfwwf not found: http://fpaste.org/paste/18056 Then just changed the rawhide link for repo --name=rawhide --baseurl=http://download.fedora.redhat.com/pub/fedora/linux/development/i386/os Geting errors with plymouth-theme-charge: http://fpaste.org/paste/18069 If you enable the fedora-rawhide repo you don't need any of the fedora, fedora-updates, fedora-updates-testing repos. The first one is what will become Fedora 12. The later 3 is what Strawberry is based upon (Fedora 11). If your new to it I would stick to Fedora 11 as its stable and is the same package base of strawberry. fedora-rawhide is a moving target and it regularly has issues at the moment (for example at the moment it has issues with running GUI terminal windows - IE it might break and you get to keep both pieces). Cheer, Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Problems running Sugar under Jaunty (9.04)
A new entry today on http://wiki.sugarlabs.org/go/Talk:Community/Distributions/Ubuntu: (from) Neil Mayhew http://wiki.sugarlabs.org/go/User:Nmayhew 16:28, 10 July 2009 (UTC) I was able to make the sugar packages work by adding a gconf setting: gconftool-2 -s /desktop/sugar/desktop/favorites_layout -t string ring-layout I think this will be fixed by adding the right gconf schema to the package, and hopefully will be fixed in version 0.84. There are still lots of non-fatal error messages in the terminal, but it looks like these can be ignored. I used sugar-emulator --dpi=200. Logging in to a Sugar session from gdm worked too. Previously, it was thought that a problem with Xephyr and dbushttps://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/325706 was at fault, but the above workaround shows that it's a Sugar packaging problem. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Problems running Sugar under Jaunty (9.04)
On Fri, Jul 10, 2009 at 12:50 PM, Frederick Grosefgr...@gmail.com wrote: A new entry today on http://wiki.sugarlabs.org/go/Talk:Community/Distributions/Ubuntu: (from) Neil Mayhew 16:28, 10 July 2009 (UTC) I was able to make the sugar packages work by adding a gconf setting: gconftool-2 -s /desktop/sugar/desktop/favorites_layout -t string ring-layout Doesn't work for me. I think this will be fixed by adding the right gconf schema to the package, and hopefully will be fixed in version 0.84. There are still lots of non-fatal error messages in the terminal, but it looks like these can be ignored. I used sugar-emulator --dpi=200. I tried that, too. No luck. It still gets to the Sugar cursor and hangs. Logging in to a Sugar session from gdm worked too. Previously, it was thought that a problem with Xephyr and dbus was at fault, but the above workaround shows that it's a Sugar packaging problem. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Silent Thunder (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) is my name And Children are my nation. The Cosmos is my dwelling place, The Truth my destination. http://earthtreasury.org/worknet (Edward Mokurai Cherlin) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Haiti dormant (was Re: Sugar as desktop os)
2009/7/10 Philippe Clérié phili...@gcal.net: We're located in Haiti. Excellent. I had a hand in getting Kreyol localization started. Sorry I left that off. And before anyone asks :-) we're not part of the pilot that was scheduled to begin in Haiti last year. I briefly worked with them. As far as I can tell, after the last cabinet shuffle, the project has gone dormant. Officially, I don't know why. Unofficially, the new Minister of Education does not like anything started by the previous one. Or so it seems. Did the laptops get distributed first? If not, where are they? -- Silent Thunder (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) is my name And Children are my nation. The Cosmos is my dwelling place, The Truth my destination. http://earthtreasury.org/worknet (Edward Mokurai Cherlin) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Haiti dormant (was Re: Sugar as desktop os)
Did the laptops get distributed first? If not, where are they? No the laptops were not distributed as far as I know. As to where they are, the information is not public so I don't know. Excellent. I had a hand in getting Kreyol localization started. It's such a small world. :-) I got involved too at the beginning but the effort seemed to have fizzled very quickly, based on zero activity on the mailing list. Perhaps the effort went elsewhere and I did not notice. -- Philippe -- The trouble with common sense is that it is so uncommon. Anonymous On Friday 10 July 2009 17:26:00 Edward Cherlin wrote: 2009/7/10 Philippe Clérié phili...@gcal.net: We're located in Haiti. Excellent. I had a hand in getting Kreyol localization started. Sorry I left that off. And before anyone asks :-) we're not part of the pilot that was scheduled to begin in : Haiti last year. I briefly worked with them. As far as I can tell, after the last cabinet shuffle, the project has gone dormant. Officially, I don't know why. Unofficially, the new Minister of Education does not like anything started by the previous one. Or so it seems. Did the laptops get distributed first? If not, where are they? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Haiti dormant (was Re: Sugar as desktop os)
2009/7/10 Philippe Clérié phili...@gcal.net: Did the laptops get distributed first? If not, where are they? No the laptops were not distributed as far as I know. As to where they are, the information is not public so I don't know. Excellent. I had a hand in getting Kreyol localization started. It's such a small world. :-) I got involved too at the beginning but the effort seemed to have fizzled very quickly, based on zero activity on the mailing list. Perhaps the effort went elsewhere and I did not notice. http://wiki.laptop.org/go/Pootle [ht] — Haitian Creole language — kreyòl ayisyen TA Edward MokuraiCherlin Pootle: mokurai TA Bastien Guerry Pootle: bzg TRA Jude AugusmaPootle: jude O Alexander Dupuy Pootle: Dupuy TRA MasterChes Pootle: Masterches TRA lacrete Pootle: lacrete MasterChes is also involved with Ubuntu localization. -- Philippe -- The trouble with common sense is that it is so uncommon. Anonymous -- Silent Thunder (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) is my name And Children are my nation. The Cosmos is my dwelling place, The Truth my destination. http://earthtreasury.org/worknet (Edward Mokurai Cherlin) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] Building strawberry from git
Hi, If you enable the fedora-rawhide repo you don't need any of the fedora, fedora-updates, fedora-updates-testing repos. The first one is what will become Fedora 12. The later 3 is what Strawberry is based upon (Fedora 11). If your new to it I would stick to Fedora 11 as its stable and is the same package base of strawberry. fedora-rawhide is a moving target and it regularly has issues at the moment (for example at the moment it has issues with running GUI terminal windows - IE it might break and you get to keep both pieces). Cheer, Peter When I added the rawhide repos I did commented the others. I prefer staying with F11 but I had to try all the ways I could till I got something working. What am I doing wrong? :D You're certainly not failling for lack of trying. It is a trying process :) If you are doing this build for an XO, please see what problems you encounter with: git-clone git://git.sugarlabs.org/soas/devxo.git soas-xo cd soas-xo git checkout -b xo-strawberry origin/xo-strawberry mkdir images cache echo soasxo00 images/lastbuild sudo ./build See BULDING.txt for a bit more detail. Martin The build is not for an XO, just for laptops. Thx, -- - Andrés Arrieta Perréard (XE1YAA) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Initial implementation of toolbars design
Hi Aleksey, On 10 Jul 2009, at 16:19, Aleksey Lim wrote: Hi all, http://git.sugarlabs.org/projects/sugar-toolkit/repos/toolbars there is simle example in examples/toolbar.py Does it satisfy mockups? Sugar-jhbuild is broken for me just now so can't look/test :-( Is this toolbar example work for the Journal, Browse (tabs treatment), or the main system wide Sugar toolbars (BTW: I'm making some new mock-ups of them just now)? Any chance of a screen shot or two? :-) Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar as desktop os
Hi Philippe, Philippe Clérié phili...@gcal.net writes: We're located in Haiti. Sorry I left that off. And before anyone asks :-) we're not part of the pilot that was scheduled to begin in Haiti last year. I briefly worked with them. As far as I can tell, after the last cabinet shuffle, the project has gone dormant. Officially, I don't know why. Unofficially, the new Minister of Education does not like anything started by the previous one. Or so it seems. Thanks for the news. You may remember that I was in Haïti one year ago, helping at the very beginning of the project. I've been trying hard to get some fresh information on the current status of the project, with no luck. I expected something like you describe, which is very sad. The last news I had was this movie: http://olpc-france.org/blog/2009/06/olpc-haiti-deploiement-dans-une-nouvelle-ecole/ Apparently things are not stuck, just moving *very* slowly. One problem is that while I have the computer expertise, I know next to nothing about education, and those who have that expertise are somewhat afraid? of the computer. Common pattern, I would say. This is an issue we plan to tackle here at OLPC France. We have been contacting teachers and will build the Sugar documentation in collaboration with them, with example of what they want to do in the classrooms. If you want to join us, just jump on this link: http://lists.laptop.org/listinfo/olpc-france Congrats for your continuous efforts. -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Haiti dormant
Hi Philippe, Philippe Clérié phili...@gcal.net writes: Did the laptops get distributed first? If not, where are they? No the laptops were not distributed as far as I know. As to where they are, the information is not public so I don't know. There is no information on the olpchaiti.org website due to lack of webmaster. But as I said, I think there are a few schools already equiped with the laptops. At least one: http://olpc-france.org/blog/2009/06/olpc-haiti-deploiement-dans-une-nouvelle-ecole/ Excellent. I had a hand in getting Kreyol localization started. It's such a small world. :-) Indeed. I got involved too at the beginning but the effort seemed to have fizzled very quickly, based on zero activity on the mailing list. Perhaps the effort went elsewhere and I did not notice. The effort went IRL during the last summer. The haitian team worked hard getting the translation done, and there were very few messages on the mailing list because things were mainly done face to face. Someone was in charge of letting the mailing list notice about the progress but obviously it was not me. (Part of my work in Haiti was to help them be more autonomous about such tasks.) Regards, -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Bug tracker enhancements
On Thu, 2009-07-09 at 07:45 +0200, Simon Schampijer wrote: Hi, Our current trac instance is missing some basic functionality: - versions per component: a really simple enhancement would be to have a text field (maybe some versions (sugar core) you can select from) but that we do not have to keep the list updated for each activity - milestones should be on a component basis as well (similar to versions) - I want to make certain fields only being available with certain permissions (a milestone and priority can only be set by the mainteiner, the severity by the bugsquad (see new fedora policy)) Can u provide me a link to the policy? Is this what u r referring to http://fedoraproject.org/wiki/Security/TrackingBugs - having a clear separation from the Soas component - if we have the things from above this is maybe not as critical, otherwise I would suggest to get a new instance for Soas Can someone help to get there? Is trac giving us that functionality? Other trac software we should consider (besides bugzilla :)? Thanks, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Bryan W. Berry Technology Director OLE Nepal, http://www.olenepal.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Bug tracker enhancements
Bryan Berry wrote: On Thu, 2009-07-09 at 07:45 +0200, Simon Schampijer wrote: Hi, Our current trac instance is missing some basic functionality: - versions per component: a really simple enhancement would be to have a text field (maybe some versions (sugar core) you can select from) but that we do not have to keep the list updated for each activity - milestones should be on a component basis as well (similar to versions) - I want to make certain fields only being available with certain permissions (a milestone and priority can only be set by the mainteiner, the severity by the bugsquad (see new fedora policy)) Can u provide me a link to the policy? Is this what u r referring to http://fedoraproject.org/wiki/Security/TrackingBugs I think Simon was referring to this one: https://www.redhat.com/archives/fedora-devel-announce/2009-July/msg1.html --Sebastian - having a clear separation from the Soas component - if we have the things from above this is maybe not as critical, otherwise I would suggest to get a new instance for Soas Can someone help to get there? Is trac giving us that functionality? Other trac software we should consider (besides bugzilla :)? Thanks, Simon ___ 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] Bug tracker enhancements
I spent a couple hours playing w/ redmine version 0.84 this morning. It is still relatively tedious to manage large #'s of users compared to Trac. The trunk version promises much better user management. I will report back on this after working on it w/ bernie. I think redmine in general is much easier to use but it might not provide enough additional functionality to justify the pain of migration. - versions per component: a really simple enhancement would be to have a text field (maybe some versions (sugar core) you can select from) but that we do not have to keep the list updated for each activity In the trunk version, components should copy target versions from the parent project when the component subproject is created but probably won't be updated when new target versions are added to the parent project. Will have to see this firsthand though when i work w/ the trunk. - milestones should be on a component basis as well (similar to versions) That is easy. But harder to tie tickets in components to versions for that component, but perhaps not possible to tie them to milestones of the parent project. - I want to make certain fields only being available with certain permissions (a milestone and priority can only be set by the mainteiner, the severity by the bugsquad (see new fedora policy)) This is definitely feasible for certain fields but afaik not for the milestone or priority. I will look for haqs for it though, as there are many, many redmine hacks Hopefully, I will have sommething to show u folks in the next couple days -- Bryan W. Berry Technology Director OLE Nepal, http://www.olenepal.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Initial implementation of toolbars design
On 07/11/2009 03:44 AM, Gary C Martin wrote: Hi Aleksey, On 10 Jul 2009, at 16:19, Aleksey Lim wrote: Hi all, http://git.sugarlabs.org/projects/sugar-toolkit/repos/toolbars there is simle example in examples/toolbar.py Does it satisfy mockups? Sugar-jhbuild is broken for me just now so can't look/test :-( Is this toolbar example work for the Journal, Browse (tabs treatment), or the main system wide Sugar toolbars (BTW: I'm making some new mock-ups of them just now)? Any chance of a screen shot or two? :-) Regards, --Gary Awesome, Aleksey. It is for the activities. But I guess can be used in the Journal as well. I have attached a screenshot from Aleksey's work. Regards, Simon attachment: toolbars.png___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
