Re: [Sugar-devel] [Fwd: [PATCH] use the spanish verb quitar for unmounting devices]
On Sun, May 16, 2010 at 20:07, Bernie Innocenti ber...@codewiz.org wrote: This was also supposed to be posted on the list: - Mensaje reenviado De: Bernie Innocenti ber...@codewiz.org Para: Tomeu Vizoso to...@sugarlabs.org Cc: Sayamindu Dasgupta sayami...@gmail.com, de...@lists.sugarlabs.org, Bernie Innocenti ber...@codewiz.org Asunto: [PATCH] use the spanish verb quitar for unmounting devices Fecha: Sun, 16 May 2010 13:44:05 -0400 In Sugar 0.88, the command for unmounting removable devices has been renamed from Unmount to Remove, which is used throughout the GUI with several slightly different meanings. The common translation for remove was eliminar, whose semantic meaning is eliminate, thus inappropriate for the unmount operation. Other languages may not be so lucky. We may have to keep the string for unmounting devices distinct from the others, along with a TRNAS comment to warn translators about the context. --- po/es.po | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/po/es.po b/po/es.po index 587608f..6702db6 100644 --- a/po/es.po +++ b/po/es.po @@ -975,7 +975,7 @@ msgstr Transferencia a %r #: ../src/jarabe/frame/clipboardmenu.py:52 ../src/jarabe/view/palettes.py:218 msgid Remove -msgstr Eliminar +msgstr Quitar Retirar would also work in Spanish from Spain, is slightly more formal than Quitar but is also a bit more specific. I would say to just ask around in your office and do whatever they tell you is best. Regards, Tomeu #: ../src/jarabe/frame/clipboardmenu.py:57 #: ../src/jarabe/frame/clipboardmenu.py:80 -- 1.7.0.1 -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ 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] [PATCH] Add icons to MANIFEST files
On Sun, May 16, 2010 at 05:25:10PM -0400, Bernie Innocenti wrote: Pippy icons were not listed in the MANIFEST file and thus not being installed. [...] Isn't MANIFEST generated automatically by running ./setup.py fix_manifest? We should remove it from the Pippy git repo and make sure sugar-jhbuild calls fix_manifest. CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Announcing the Development Team Lead election
Hi, sorry for getting late to this discussion, have been traveling this weekend. Just wanted to make some clarifications and to explain my position on this. On Sat, May 15, 2010 at 18:48, Chris Ball c...@laptop.org wrote: Hi everyone, Tomeu's stepping down as the Development Team Lead¹, I actually stepped down as development team coordinator which is/was an administrative role, I wasn't the development team leader because that position has never existed before in our community. I tried to make it very clear on the email you cite. and we'd like to elect a replacement. This is an important position -- the team lead is responsible for setting clear goals for the team, being a responsive upstream for work we receive from the community, appointing a release manager for the next (0.90) release and helping to define its scope, and holding regular Development Team meetings on IRC, including coordination with the Design and Deployment Teams on new features. Has there been any discussion on the creation of this role? Are there plans to create such strong positions for other teams? There are more details on the role and the team here: http://wiki.sugarlabs.org/go/Development_Team But the wiki still refers to a chairman-like team coordinator, not to the leader position with heavy responsibilities that you describe in this email. My concerns about the position you are describing on this email: - responsible for setting clear goals for the team: May not be what you meant to say, but I think a single individual cannot be setting goals for a team when most people are volunteers or employed by several organizations. Maybe you meant making sure that the team has clear goals and is kept focused which is what is in the wiki? - being a responsive upstream for work we receive from the community: this sounds like a rather big responsibility to me. For example, what will happen with modules that are unmaintained such as hulahop and browse? If nobody has stepped up to maintain those since they were orphaned, are we going to consider the team lead a failure if nobody steps up in the future? If we put such a pressure on a single individual, maybe that person will feel compelled to take decisions that affect negatively other aspects such as QA or deployment participation? - appointing a release manager for the next (0.90) release: if you mean just formally appointing whoever the team members choose, then I'm fine with it, but it's not obvious for me as it's expressed. What about the other positions related to development, the team lead also need to appoint those? Until now we have never seen two people competing for a role, nor disagreement on a candidacy. - coordination with the Design and Deployment Teams on new features: do we really need that the team leads takes this responsibility as well? Or is assumed that the team lead will delegate it on others? The position is open to anyone; if you're interested in nominating yourself, just add your name and platform to: http://wiki.sugarlabs.org/go/Development_Team/Team_Lead_Candidates_2010_05 The platform -- and the election as a whole -- is an opportunity to express your view on development directions that Sugar should take. The nomination period will be open for seven days, closing at 00:00 UTC on May 22nd. Then the election will run for ten days, starting at 00:00 UTC on May 22nd and finishing at 00:00 UTC on June 1st. All Sugar Labs members are eligible to vote, and will receive a token for doing so by e-mail. I've volunteered to run the election. May I suggest that both candidates and voters are restricted to development team members? This would encourage interested people to join the team, strengthening it. I think that by giving some autonomy to teams we'll be encouraging them to take ownership of their areas. I agree is very important to find people interested on leading efforts and taking responsibilities, but I think is equally important to have a team structure that encourage division of work, diversity of opinions and pooling of resources. I'm also not sure we need a full-blown election with selectricity. I'm thinking that open voting on the mailing list may be enough, unless we are expecting that people won't vote freely without anonymity. Finally, many thanks to Tomeu Vizoso and Simon Schampijer for their great work as the Development Team Lead and Release Manager! Thanks to you for taking this important task, I'm very happy to see we are making progresses on this area. Hope the concerns I have raised above aren't seen as push back but as sincere opinions. Regards, Tomeu - Chris. ¹: http://lists.sugarlabs.org/archive/sugar-devel/2010-May/023825.html -- Chris Ball c...@laptop.org One Laptop Per Chil ___ IAEP -- It's An Education Project (not a laptop project!) i...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[Sugar-devel] journal maintenance (was Re: [RFC PATCH v0 0/8] Journal sorting by file size and creation time.)
On Thu, May 6, 2010 at 07:14, Aleksey Lim alsr...@member.fsf.org wrote: On Sat, May 01, 2010 at 04:33:48PM -0300, Andrés Ambrois wrote: This patchset implements sorting in the Journal UI as described in [0]. This feature was requested in [1] and sponsored by Activity Central [2]. Sorting by filesize is vital in the field where users need to free up disk space. Currently, the only way to find candidates for deletion is to access the expanded view of each entry, one by one. This can be a very time consuming process and often leads to indiscriminate deletion and thus potential loss of valuable data. This is bad. Sorting by creation time (ctime) is also implemented as described in the Design Proposal. This implementation currently lacks two aspects which I hope will be sorted out in the review process: 1- The proposal does not include a specification for changing the order of the sort. This patch assumes an ascending order. 2- There are no icons for the sorting criteria. Or at least I couldn't find the ones presented in the proposal. I'm sure someone from the design team could vectorize the ones there. v0: Initial submission to sugar-devel As current datastore and journal maintainer, some points: I'm still not sure will ml path proposal scheme work on not, it removes some bugs.sl.o issues but adds new e.g. it is pretty hard to collaborate (in my mind) via ml history, in case of bugs.sl.o, someone can just share http link to complicated query. Other thing is that on bugs.sl.o it is easy to query tickets by keywords for example. And since having patches both on bugs.sl.o and ml is pretty useless and there is no regular way to attach 0.90 targeted keyword to ml posts, please create tickets on bugs.sl.o. In case of journal, my strong thinking is that Journal shouldn't be only one for all purposes and it shouldn't be only in glucose as part of sugar core. I initiated journal library [3]. The major idea is that anyone can create his own journal activity and glucose can provide common/simple/default one. So, all my resources I spend to journal library (and related projects) not to journal code in glucose. Btw, it's a bit awkward that the official journal maintainer says it won't dedicate time to it any more. Should we consider the existing journal officially unmaintained and look for candidates? Regards, Tomeu If you share this thinking, please come aboard. Having covered all the above, I thing only datastore patch is requested. [3] http://wiki.sugarlabs.org/go/Activity_Team/Services/Journal [0] http://wiki.sugarlabs.org/go/Design_Team/Proposals/Journal#Extended_list_view_palette [1] http://bugs.sugarlabs.org/ticket/1915 [2] http://activitycentral.org Andrés Ambrois (8): Journal: Retrieve ctime and filesize from the datastore. Add ctime and filesize columns to the journal list model. Add add_separator method for convenience. Add a ListViewButton to the journal search toolbar. Rename the date column to 'sort_column' Add sort_by method to the journal list view. Call sort_by in the list view when sorting is selected in the toolbar. Expandedentry: Try to use the filesize property. src/jarabe/journal/expandedentry.py | 5 +- src/jarabe/journal/journalactivity.py | 5 ++ src/jarabe/journal/journaltoolbox.py | 75 - src/jarabe/journal/listmodel.py | 22 +++--- src/jarabe/journal/listview.py | 34 ++- src/jarabe/journal/model.py | 6 +- 6 files changed, 124 insertions(+), 23 deletions(-) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- 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] journal maintenance (was Re: [RFC PATCH v0 0/8] Journal sorting by file size and creation time.)
On 05/17/2010 12:01 PM, Tomeu Vizoso wrote: On Thu, May 6, 2010 at 07:14, Aleksey Limalsr...@member.fsf.org wrote: On Sat, May 01, 2010 at 04:33:48PM -0300, Andrés Ambrois wrote: This patchset implements sorting in the Journal UI as described in [0]. This feature was requested in [1] and sponsored by Activity Central [2]. Sorting by filesize is vital in the field where users need to free up disk space. Currently, the only way to find candidates for deletion is to access the expanded view of each entry, one by one. This can be a very time consuming process and often leads to indiscriminate deletion and thus potential loss of valuable data. This is bad. Sorting by creation time (ctime) is also implemented as described in the Design Proposal. This implementation currently lacks two aspects which I hope will be sorted out in the review process: 1- The proposal does not include a specification for changing the order of the sort. This patch assumes an ascending order. 2- There are no icons for the sorting criteria. Or at least I couldn't find the ones presented in the proposal. I'm sure someone from the design team could vectorize the ones there. v0: Initial submission to sugar-devel As current datastore and journal maintainer, some points: I'm still not sure will ml path proposal scheme work on not, it removes some bugs.sl.o issues but adds new e.g. it is pretty hard to collaborate (in my mind) via ml history, in case of bugs.sl.o, someone can just share http link to complicated query. Other thing is that on bugs.sl.o it is easy to query tickets by keywords for example. And since having patches both on bugs.sl.o and ml is pretty useless and there is no regular way to attach 0.90 targeted keyword to ml posts, please create tickets on bugs.sl.o. In case of journal, my strong thinking is that Journal shouldn't be only one for all purposes and it shouldn't be only in glucose as part of sugar core. I initiated journal library [3]. The major idea is that anyone can create his own journal activity and glucose can provide common/simple/default one. So, all my resources I spend to journal library (and related projects) not to journal code in glucose. I hope I understand this right, please state so if not. As it is perfectly ok to develop new solutions, a maintainer, should well maintain existing code. We have = 0.84 shipped to 1 million kids, and the Journal as it exists is a very important part of the Sugar experience. Please think about the position you have in. Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] changes to the review process (was Re: Sugar 0.88 packages)
On Sat, May 15, 2010 at 00:02, Bernie Innocenti ber...@codewiz.org wrote: El Fri, 14-05-2010 a las 08:59 +0200, Tomeu Vizoso escribió: I'm just asking for someone to propose a set of concrete and coherent changes to the current process, is it really asking too much? I'm sorry but I cannot go through the old threads, ask individuals for clarifications, then draft that new process myself. Do you want the proposal posted to the wiki? We could basically take Sasha's original plan and copy it to the wiki. I think it was quite well thought: http://lists.sugarlabs.org/archive/sugar-devel/2010-April/023410.html I propose the following amendments: 1) Scrap the paragraph saying that any sugar developer can approve changes, because it turned out to be a controversial point. The who and the where of reviews are orthogonal topics that can be discussed independently. 2) Also scrap the part where Sascha proposes ways to track patches in the list, since we can now use Patchwork for this. 3) Add all the clarifications in my follow-up to Sascha's proposal: http://lists.sugarlabs.org/archive/sugar-devel/2010-April/023468.html 4) The existing conventions still apply for referencing tickets in the commit logs 5) When a corresponding ticket exists, the committer should add a link to the patch discussion in Patchwork before committing the patch. Does this sound good enough for an initial iteration? If so, I could take care of transcribing it into the wiki. Then, we can further refine the process as we go. Hi Bernie, I think this is an excellent step forward, I really appreciate you having taken the time to do this. I still need to explore patchwork further and I'm a bit concerned about requiring that reviewers amend the commit message but I'm willing to give it a test drive and see how it works in real. I'm looking forward for the new text proposal. Regards, Tomeu -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Announcing the Development Team Lead election
On 05/15/2010 06:48 PM, Chris Ball wrote: Hi everyone, Tomeu's stepping down as the Development Team Lead¹, and we'd like to elect a replacement. This is an important position -- the team lead is responsible for setting clear goals for the team, being a responsive upstream for work we receive from the community, appointing a release manager for the next (0.90) release and helping to define its scope, and holding regular Development Team meetings on IRC, including coordination with the Design and Deployment Teams on new features. There are more details on the role and the team here: http://wiki.sugarlabs.org/go/Development_Team Hi Chris, the position as you describe it, seems quite complex. I would make a difference between a coordinator and a leader. The coordinator will make sure there are regular meetings to be held and to give a structure for those and is in contact with the release manager about the schedule. A team can have several leaders, this role is not appointed but comes naturally with the work one has been doing, in my opinion. I don't think the development team lead has to appoint the release manager. From my experience I can say, that I did one release with Marco together and then kept on doing it. Ideally a model where the current release manager is shadowed and then keeps on that task. If we have more candidates that want to fulfill that role, even better, they can share this task. Coordination with the design team is a good point, and the design team coordinator is another critical open vacancy. Last release I did manage that since I was interested in the outcome for the release, though this was not a long term solution ;) And for the general strategy, we have the Feature process [1]. This helps all the deployments and contributors to raise their voice. And if there is consensus in the community the Features will make their way forward into releases. So, we have the processes to move forward, we just have to use them and keep on doing. In general, I think we should wide spread more the load. There is an issue of resources. And we have to describe the positions and fill them. Make the roles small and clear, define them well and communicate well between the teams are the keys here. Most of the tasks are not that time consuming at all, but if people does fill out several roles it quickly gets too much for the individual. From my experience from last releases I would definitely add to the list: the deployment team position (which has been done already), the design team one and the testing one. Those were always the week points in previous releases. Thanks for helping to enhance in this area, Simon [1] http://wiki.sugarlabs.org/go/Features/Policy ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Paint: patch to #1015
Change gtk.ColorButton by ColorToolButton also. Gonzalo On Mon, May 17, 2010 at 12:36 AM, James Cameron qu...@laptop.org wrote: On Mon, May 17, 2010 at 12:15:50AM -0300, Gonzalo Odiard wrote: I propose a patch to http://bugs.sugarlabs.org/ticket/1015 Hmm, that's odd, your patch only changes the fill colour of an SVG, I'm puzzled as to how it fixes the ticket problem. Can you explain? -- James Cameron http://quozl.linux.org.au/ ___ 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] [PATCH] Add icons to MANIFEST files
On Mon, May 17, 2010 at 11:10:56AM +0200, Sascha Silbe wrote: Isn't MANIFEST generated automatically by running ./setup.py fix_manifest? We should remove it from the Pippy git repo and make sure sugar-jhbuild calls fix_manifest. Therefore remove also from Calculate, Hello World, Moon, Physics, and probably quite a few other activities. Sounds like a big change. Why do this? -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Paint: patch to #1015
On Mon, May 17, 2010 at 08:08:31AM -0300, Gonzalo Odiard wrote: Change gtk.ColorButton by ColorToolButton also. You only proposed a patch to icons/icon-fill.svg, there was no patch to toolbox.py in your mail. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] journal maintenance (was Re: [RFC PATCH v0 0/8] Journal sorting by file size and creation time.)
On Mon, May 17, 2010 at 12:01:53PM +0200, Tomeu Vizoso wrote: On Thu, May 6, 2010 at 07:14, Aleksey Lim alsr...@member.fsf.org wrote: On Sat, May 01, 2010 at 04:33:48PM -0300, Andrés Ambrois wrote: This patchset implements sorting in the Journal UI as described in [0]. This feature was requested in [1] and sponsored by Activity Central [2]. Sorting by filesize is vital in the field where users need to free up disk space. Currently, the only way to find candidates for deletion is to access the expanded view of each entry, one by one. This can be a very time consuming process and often leads to indiscriminate deletion and thus potential loss of valuable data. This is bad. Sorting by creation time (ctime) is also implemented as described in the Design Proposal. This implementation currently lacks two aspects which I hope will be sorted out in the review process: 1- The proposal does not include a specification for changing the order of the sort. This patch assumes an ascending order. 2- There are no icons for the sorting criteria. Or at least I couldn't find the ones presented in the proposal. I'm sure someone from the design team could vectorize the ones there. v0: Initial submission to sugar-devel As current datastore and journal maintainer, some points: I'm still not sure will ml path proposal scheme work on not, it removes some bugs.sl.o issues but adds new e.g. it is pretty hard to collaborate (in my mind) via ml history, in case of bugs.sl.o, someone can just share http link to complicated query. Other thing is that on bugs.sl.o it is easy to query tickets by keywords for example. And since having patches both on bugs.sl.o and ml is pretty useless and there is no regular way to attach 0.90 targeted keyword to ml posts, please create tickets on bugs.sl.o. In case of journal, my strong thinking is that Journal shouldn't be only one for all purposes and it shouldn't be only in glucose as part of sugar core. I initiated journal library [3]. The major idea is that anyone can create his own journal activity and glucose can provide common/simple/default one. So, all my resources I spend to journal library (and related projects) not to journal code in glucose. Btw, it's a bit awkward that the official journal maintainer says it won't dedicate time to it any more. Yeah, thats right Should we consider the existing journal officially unmaintained and look for candidates? In fact I'm sure maintainer should have some vision about how project should grow, w/o such vision maintainer should pass his responsibility. In my case, I have such vision but it's incompatible with existed scheme (journal is only particular case) and will be lucky to pass Journal. And so (with exception that I don't have any ideas how it should grow) for datastore (note for future dev team leader), in mind Sascha is more appropriate candidate for datastore maintainer since having his ds versioning work in 0.90 release cycle will be really great. Of course it's all about applying patches not about submitting, I'll do my best to fix bugs in existed code. Regards, Tomeu If you share this thinking, please come aboard. Having covered all the above, I thing only datastore patch is requested. [3] http://wiki.sugarlabs.org/go/Activity_Team/Services/Journal [0] http://wiki.sugarlabs.org/go/Design_Team/Proposals/Journal#Extended_list_view_palette [1] http://bugs.sugarlabs.org/ticket/1915 [2] http://activitycentral.org Andrés Ambrois (8): Journal: Retrieve ctime and filesize from the datastore. Add ctime and filesize columns to the journal list model. Add add_separator method for convenience. Add a ListViewButton to the journal search toolbar. Rename the date column to 'sort_column' Add sort_by method to the journal list view. Call sort_by in the list view when sorting is selected in the toolbar. Expandedentry: Try to use the filesize property. src/jarabe/journal/expandedentry.py | 5 +- src/jarabe/journal/journalactivity.py | 5 ++ src/jarabe/journal/journaltoolbox.py | 75 - src/jarabe/journal/listmodel.py | 22 +++--- src/jarabe/journal/listview.py | 34 ++- src/jarabe/journal/model.py | 6 +- 6 files changed, 124 insertions(+), 23 deletions(-) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Announcing the Development Team Lead election
On Mon, May 17, 2010 at 5:40 AM, Tomeu Vizoso to...@tomeuvizoso.net wrote: Hi, sorry for getting late to this discussion, have been traveling this weekend. It is unfortunate that you were unable to join us. Obviously, given your experience, your input is critical to getting this position properly defined and filled. (I mistakenly assumed that you would have had an opportunity to respond to Chris's initial drafts. We should have held off sending the note until we had a chance to integrate your feedback.) Just wanted to make some clarifications and to explain my position on this. On Sat, May 15, 2010 at 18:48, Chris Ball c...@laptop.org wrote: Hi everyone, Tomeu's stepping down as the Development Team Lead¹, I actually stepped down as development team coordinator which is/was an administrative role, I wasn't the development team leader because that position has never existed before in our community. I tried to make it very clear on the email you cite. and we'd like to elect a replacement. This is an important position -- the team lead is responsible for setting clear goals for the team, being a responsive upstream for work we receive from the community, appointing a release manager for the next (0.90) release and helping to define its scope, and holding regular Development Team meetings on IRC, including coordination with the Design and Deployment Teams on new features. Has there been any discussion on the creation of this role? Are there plans to create such strong positions for other teams? Please don't read so much into the word leader, which I think can mean either or both an administrative (coordinator) and someone who establishes clear goals (and processes). The way in which SL has established its team structure, we give great autonomy to teams to run in whatever way they need to to accomplish their goals. We maintain a liaison to the oversight board, but otherwise, they free to organize themselves, as long as they are aligned with the overall SL goals. There are more details on the role and the team here: http://wiki.sugarlabs.org/go/Development_Team But the wiki still refers to a chairman-like team coordinator, not to the leader position with heavy responsibilities that you describe in this email. My concerns about the position you are describing on this email: - responsible for setting clear goals for the team: May not be what you meant to say, but I think a single individual cannot be setting goals for a team when most people are volunteers or employed by several organizations. Maybe you meant making sure that the team has clear goals and is kept focused which is what is in the wiki? - being a responsive upstream for work we receive from the community: this sounds like a rather big responsibility to me. For example, what will happen with modules that are unmaintained such as hulahop and browse? If nobody has stepped up to maintain those since they were orphaned, are we going to consider the team lead a failure if nobody steps up in the future? If we put such a pressure on a single individual, maybe that person will feel compelled to take decisions that affect negatively other aspects such as QA or deployment participation? - appointing a release manager for the next (0.90) release: if you mean just formally appointing whoever the team members choose, then I'm fine with it, but it's not obvious for me as it's expressed. What about the other positions related to development, the team lead also need to appoint those? Until now we have never seen two people competing for a role, nor disagreement on a candidacy. - coordination with the Design and Deployment Teams on new features: do we really need that the team leads takes this responsibility as well? Or is assumed that the team lead will delegate it on others? There seems to be a miscommunication. My presumption is that this scope of work applies to the Development Team and that the role of the leader/coordinator is to ensure that there is a structure in place to accomplish these tasks. Delegation is one way to do this. Others include setting a example (being a role model) that others can follow. Personally, I think we need a combination of approaches. But I don't think anyone expects that the leader will do everything his/herself. Regarding the important role of Release Manager, I don't think there is any argument that we need to fill that position and Simon has graciously offered to help bring the new person up to speed. (We'd been unsuccessful in finding someone to shadow Simon during the 0.86 and 0.88 releases, which is unfortunate.) At issue is how do we find/appoint the new release manager. I think the intention of the oversight board is to delegate that responsibility to the Development Team, where presumably there is the knowledge and experience to make such an important decision. How they reach that decision is a local decision, presumably in keeping with all the of the
Re: [Sugar-devel] [PATCH] sugar-artwork: stricter compiler flags
On Tue, 2010-05-11 at 18:56 -0400, Bernie Innocenti wrote: WARN_CFLAGS was already used in gtk/engine/Makefile.am, but not initialized by configure. For backwards compatibility, GCC's by default is very permissive. In my case, it was silently miscompiling code which was calling a non-existent GTK function. For this particular case, the proposed WARN_CFLAGS should make the build fail early in this case. I'm not proposing -Werror because it frequetly results in broken builds for trivial reasons when distros update the toolchain. Signed-off-by: Bernie Innocenti ber...@codewiz.org That looks like a very good change. Thanks for the patch. Reviewed-by: Benjamin Berg benja...@sipsolutions.net ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] Add icons to MANIFEST files
On Mon, May 17, 2010 at 10:52:24PM +1000, James Cameron wrote: On Mon, May 17, 2010 at 11:10:56AM +0200, Sascha Silbe wrote: Isn't MANIFEST generated automatically by running ./setup.py fix_manifest? We should remove it from the Pippy git repo and make sure sugar-jhbuild calls fix_manifest. Therefore remove also from Calculate, Hello World, Moon, Physics, and probably quite a few other activities. If these activities currently include MANIFEST in git, then yes, they should stop doing so. Please note that I'm talking about git only, not release tarballs or .xo's. Sounds like a big change. Why do this? For the same reasons we're doing it for other autogenerated files. They have a tendency to get stale (exactly what we're dealing with here) and/or cause conflicts (see constant python-xklavier build failures [1]). [1] https://buildbot.sugarlabs.org/ CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Announcing the Development Team Lead election
Hi Tomeu, I actually stepped down as development team coordinator which is/was an administrative role, I wasn't the development team leader because that position has never existed before in our community. I tried to make it very clear on the email you cite. Sorry about that. I wasn't thinking of a strong distinction between the two; we started talking about electing a new lead in the SLOBS meeting, and the title stuck in my writing. - being a responsive upstream for work we receive from the community: this sounds like a rather big responsibility to me. For example, what will happen with modules that are unmaintained such as hulahop and browse? For this point, we were thinking about someone who makes sure that patches sent in for review are replied to and applied quickly (perhaps via delegation), rather than someone who will single-handedly maintain all the code we've received in the past. In short, we want to make sure that there's no bottleneck on community contributions of patches at the SL end. - appointing a release manager for the next (0.90) release: if you mean just formally appointing whoever the team members choose, then I'm fine with it, but it's not obvious for me as it's expressed. What about the other positions related to development, the team lead also need to appoint those? Until now we have never seen two people competing for a role, nor disagreement on a candidacy. We talked in the SLOBS meeting on Friday about our urgent need to start planning 0.90, and decided that finding a release manager would be a good first task for the new development team lead/coordinator. If the development team is already able to appoint a new release manager, you should certainly go ahead and do that -- we were operating under the assumption that no-one had been found yet. (I think part of the reason I had that assumption is that the wiki page for the development team only lists you and Simon as members.) http://wiki.sugarlabs.org/go/Development_Team/Contacts - coordination with the Design and Deployment Teams on new features: do we really need that the team leads takes this responsibility as well? Or is assumed that the team lead will delegate it on others? I think that team leads should take responsibility for this, but that the responsibility can be satisfied by delegating it to others. May I suggest that both candidates and voters are restricted to development team members? This would encourage interested people to join the team, strengthening it. I think that by giving some autonomy to teams we'll be encouraging them to take ownership of their areas. That sounds fine, if you're saying that standing/voting is still open to anyone, but that they should first sign up to join the team before doing either. I agree is very important to find people interested on leading efforts and taking responsibilities, but I think is equally important to have a team structure that encourage division of work, diversity of opinions and pooling of resources. Makes sense. Sounds like we should defer to the Development Team in defining the role. I'm also not sure we need a full-blown election with selectricity. I'm thinking that open voting on the mailing list may be enough, unless we are expecting that people won't vote freely without anonymity. Okay. Let's continue gathering candidates as we were, and then the team can decide what to do with the result; whether to have an internal election, full election or something else. Thanks to you for taking this important task, I'm very happy to see we are making progresses on this area. Hope the concerns I have raised above aren't seen as push back but as sincere opinions. No problem. - Chris. -- Chris Ball c...@laptop.org One Laptop Per Child ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Announcing the Development Team Lead election
On Mon, May 17, 2010 at 15:51, Walter Bender walter.ben...@gmail.com wrote: On Mon, May 17, 2010 at 5:40 AM, Tomeu Vizoso to...@tomeuvizoso.net wrote: Hi, sorry for getting late to this discussion, have been traveling this weekend. It is unfortunate that you were unable to join us. Obviously, given your experience, your input is critical to getting this position properly defined and filled. (I mistakenly assumed that you would have had an opportunity to respond to Chris's initial drafts. We should have held off sending the note until we had a chance to integrate your feedback.) Just wanted to make some clarifications and to explain my position on this. On Sat, May 15, 2010 at 18:48, Chris Ball c...@laptop.org wrote: Hi everyone, Tomeu's stepping down as the Development Team Lead¹, I actually stepped down as development team coordinator which is/was an administrative role, I wasn't the development team leader because that position has never existed before in our community. I tried to make it very clear on the email you cite. and we'd like to elect a replacement. This is an important position -- the team lead is responsible for setting clear goals for the team, being a responsive upstream for work we receive from the community, appointing a release manager for the next (0.90) release and helping to define its scope, and holding regular Development Team meetings on IRC, including coordination with the Design and Deployment Teams on new features. Has there been any discussion on the creation of this role? Are there plans to create such strong positions for other teams? Please don't read so much into the word leader, which I think can mean either or both an administrative (coordinator) and someone who establishes clear goals (and processes). The way in which SL has established its team structure, we give great autonomy to teams to run in whatever way they need to to accomplish their goals. We maintain a liaison to the oversight board, but otherwise, they free to organize themselves, as long as they are aligned with the overall SL goals. There are more details on the role and the team here: http://wiki.sugarlabs.org/go/Development_Team But the wiki still refers to a chairman-like team coordinator, not to the leader position with heavy responsibilities that you describe in this email. My concerns about the position you are describing on this email: - responsible for setting clear goals for the team: May not be what you meant to say, but I think a single individual cannot be setting goals for a team when most people are volunteers or employed by several organizations. Maybe you meant making sure that the team has clear goals and is kept focused which is what is in the wiki? - being a responsive upstream for work we receive from the community: this sounds like a rather big responsibility to me. For example, what will happen with modules that are unmaintained such as hulahop and browse? If nobody has stepped up to maintain those since they were orphaned, are we going to consider the team lead a failure if nobody steps up in the future? If we put such a pressure on a single individual, maybe that person will feel compelled to take decisions that affect negatively other aspects such as QA or deployment participation? - appointing a release manager for the next (0.90) release: if you mean just formally appointing whoever the team members choose, then I'm fine with it, but it's not obvious for me as it's expressed. What about the other positions related to development, the team lead also need to appoint those? Until now we have never seen two people competing for a role, nor disagreement on a candidacy. - coordination with the Design and Deployment Teams on new features: do we really need that the team leads takes this responsibility as well? Or is assumed that the team lead will delegate it on others? There seems to be a miscommunication. My presumption is that this scope of work applies to the Development Team and that the role of the leader/coordinator is to ensure that there is a structure in place to accomplish these tasks. If those responsibilities belong to the team and the lead/coordinator is responsible only for making sure that the team is well setup to tackle them, then it looks fine to me. Given that we haven't had much success in past calls for team coordinators, I think we should be reducing this role to its minimum and let people surpass expectations as they see fit. Delegation is one way to do this. Others include setting a example (being a role model) that others can follow. Personally, I think we need a combination of approaches. But I don't think anyone expects that the leader will do everything his/herself. Regarding the important role of Release Manager, I don't think there is any argument that we need to fill that position and Simon has graciously offered to help bring the new person up to speed.
Re: [Sugar-devel] [IAEP] Announcing the Development Team Lead election
On Mon, May 17, 2010 at 16:45, Chris Ball c...@laptop.org wrote: Hi Tomeu, I actually stepped down as development team coordinator which is/was an administrative role, I wasn't the development team leader because that position has never existed before in our community. I tried to make it very clear on the email you cite. Sorry about that. I wasn't thinking of a strong distinction between the two; we started talking about electing a new lead in the SLOBS meeting, and the title stuck in my writing. - being a responsive upstream for work we receive from the community: this sounds like a rather big responsibility to me. For example, what will happen with modules that are unmaintained such as hulahop and browse? For this point, we were thinking about someone who makes sure that patches sent in for review are replied to and applied quickly (perhaps via delegation), rather than someone who will single-handedly maintain all the code we've received in the past. In short, we want to make sure that there's no bottleneck on community contributions of patches at the SL end. It's good to have someone caring about this and busy maintainers use to appreciate when they are pinged when some patch needs attention. Something I think that could be a tremendous improvement is moving the review report from dev.laptop.org to bugs.sugarlabs.org. By having an automated report that tells what is in the queue and for how long, maintainers have a very direct feedback without nobody having to do extra effort past the initial installation. - appointing a release manager for the next (0.90) release: if you mean just formally appointing whoever the team members choose, then I'm fine with it, but it's not obvious for me as it's expressed. What about the other positions related to development, the team lead also need to appoint those? Until now we have never seen two people competing for a role, nor disagreement on a candidacy. We talked in the SLOBS meeting on Friday about our urgent need to start planning 0.90, and decided that finding a release manager would be a good first task for the new development team lead/coordinator. If the development team is already able to appoint a new release manager, you should certainly go ahead and do that -- we were operating under the assumption that no-one had been found yet. But if the dev team cannot find a release manager, how could the dev team leader? Maybe I have been reading too much in the particular chose of words, as Walter said, and by appointing you meant just to keep the issue of the release manager in the TODO list and agenda until one is found. (I think part of the reason I had that assumption is that the wiki page for the development team only lists you and Simon as members.) http://wiki.sugarlabs.org/go/Development_Team/Contacts That's really unfortunate, hopefully this will get fixed soon. - coordination with the Design and Deployment Teams on new features: do we really need that the team leads takes this responsibility as well? Or is assumed that the team lead will delegate it on others? I think that team leads should take responsibility for this, but that the responsibility can be satisfied by delegating it to others. May I suggest that both candidates and voters are restricted to development team members? This would encourage interested people to join the team, strengthening it. I think that by giving some autonomy to teams we'll be encouraging them to take ownership of their areas. That sounds fine, if you're saying that standing/voting is still open to anyone, but that they should first sign up to join the team before doing either. Well, each team could put conditions on who can become a member, but I don't have a strong opinion on this. I agree is very important to find people interested on leading efforts and taking responsibilities, but I think is equally important to have a team structure that encourage division of work, diversity of opinions and pooling of resources. Makes sense. Sounds like we should defer to the Development Team in defining the role. I'm also not sure we need a full-blown election with selectricity. I'm thinking that open voting on the mailing list may be enough, unless we are expecting that people won't vote freely without anonymity. Okay. Let's continue gathering candidates as we were, and then the team can decide what to do with the result; whether to have an internal election, full election or something else. Sounds great, thanks again for stepping up with this. Regards, Tomeu Thanks to you for taking this important task, I'm very happy to see we are making progresses on this area. Hope the concerns I have raised above aren't seen as push back but as sincere opinions. No problem. - Chris. -- Chris Ball c...@laptop.org One Laptop Per Child
Re: [Sugar-devel] journal maintenance (was Re: [RFC PATCH v0 0/8] Journal sorting by file size and creation time.)
On Mon, May 17, 2010 at 9:04 AM, Aleksey Lim alsr...@member.fsf.org wrote: Should we consider the existing journal officially unmaintained and look for candidates? In fact I'm sure maintainer should have some vision about how project should grow, w/o such vision maintainer should pass his responsibility. In my case, I have such vision but it's incompatible with existed scheme (journal is only particular case) and will be lucky to pass Journal. That's a sad, but respectable position to take. Extending, enriching and transforming the Journal is a key thing for Sugar. Of course, it is good to see exploration and experimentation in Activities that do Journal-ish things, but the Journal is a central element of our usage model, so I hope it incorporates new tricks (perhaps new tricks explored in separate Activities). cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Fwd: [PATCH] use the spanish verb quitar for unmounting devices]
El Mon, 17-05-2010 a las 09:24 +0200, Tomeu Vizoso escribió: On Sun, May 16, 2010 at 20:07, Bernie Innocenti ber...@codewiz.org wrote: This was also supposed to be posted on the list: - Mensaje reenviado De: Bernie Innocenti ber...@codewiz.org Para: Tomeu Vizoso to...@sugarlabs.org Cc: Sayamindu Dasgupta sayami...@gmail.com, de...@lists.sugarlabs.org, Bernie Innocenti ber...@codewiz.org Asunto: [PATCH] use the spanish verb quitar for unmounting devices Fecha: Sun, 16 May 2010 13:44:05 -0400 In Sugar 0.88, the command for unmounting removable devices has been renamed from Unmount to Remove, which is used throughout the GUI with several slightly different meanings. The common translation for remove was eliminar, whose semantic meaning is eliminate, thus inappropriate for the unmount operation. Other languages may not be so lucky. We may have to keep the string for unmounting devices distinct from the others, along with a TRNAS comment to warn translators about the context. --- po/es.po |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/po/es.po b/po/es.po index 587608f..6702db6 100644 --- a/po/es.po +++ b/po/es.po @@ -975,7 +975,7 @@ msgstr Transferencia a %r #: ../src/jarabe/frame/clipboardmenu.py:52 ../src/jarabe/view/palettes.py:218 msgid Remove -msgstr Eliminar +msgstr Quitar Retirar would also work in Spanish from Spain, is slightly more formal than Quitar but is also a bit more specific. I would say to just ask around in your office and do whatever they tell you is best. I've ran a quick survey. Sebastian said: Expulsar is common in other OSs, Retirar is correct but not direct enough to be clear, and Quitar is too broad and also unclear. Jorge proposed: Extraer. In both cases, we need to make the strings distinct in the code. In C, I'd specify the context in which the string is used, like so: pgettext(Device Icon, Remove) However, Python's gettext module does not yet support pgettext(): http://bugs.python.org/issue2504 How is this handled in Sugar? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] Deja-Dup (duplicity) as a way to backup-restore Soas Mirabelle Home directory
El Sun, 16-05-2010 a las 11:30 -0700, Thomas C Gilliard escribió: Bernie; Will you make a .xo or rpm of your backup for standalone instances of Soas? All we need is a new control panel item in Sugar and add 3 scripts to ds-backup-client. I'm attaching patches to do both things. You can test this functionality in os180py. The current implementation works, but is way too crude for upstreaming it. My TODO list contains: 1) Discuss UI refinements proposed by Eben (see his post to sugar-devel) 2) Integrate the USB backup/restore functionality developed by Esteban for LATU. 3) Address the concerns of Martin Langhoff regarding destroying the current journal contents on restore. How would I convert it to a .xo file? Is there a reference I should consult? I am running from the command line now. Documentation for creating bundles is here: http://wiki.sugarlabs.org/go/Development_Team/Almanac/Activity_Bundles But I feel that backup/restore should be core Sugar functionality, not implemented as an activity. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ From 5a83859a66d5fb55e7587e4890b37cae13f39735 Mon Sep 17 00:00:00 2001 From: Martin Abente mabe...@paraguayeduca.org Date: Fri, 9 Apr 2010 14:18:42 -0400 Subject: [PATCH] Backup Restore front end for control panel Organization: Paraguay Educa Backported from 0.88 Signed-off-by: Martin Abente mabe...@paraguayeduca.org --- configure.ac |1 + data/icons/Makefile.am |1 + data/icons/module-journalmanagement.svg| 127 +++ extensions/cpsection/Makefile.am |2 +- extensions/cpsection/journalmanagement/Makefile.am |6 + extensions/cpsection/journalmanagement/__init__.py | 22 ++ extensions/cpsection/journalmanagement/model.py| 78 +++ extensions/cpsection/journalmanagement/view.py | 236 8 files changed, 472 insertions(+), 1 deletions(-) create mode 100644 data/icons/module-journalmanagement.svg create mode 100644 extensions/cpsection/journalmanagement/Makefile.am create mode 100644 extensions/cpsection/journalmanagement/__init__.py create mode 100644 extensions/cpsection/journalmanagement/model.py create mode 100644 extensions/cpsection/journalmanagement/view.py diff --git a/configure.ac b/configure.ac index 479056d..40442c6 100644 --- a/configure.ac +++ b/configure.ac @@ -53,6 +53,7 @@ extensions/cpsection/aboutcomputer/Makef extensions/cpsection/aboutme/Makefile extensions/cpsection/datetime/Makefile extensions/cpsection/frame/Makefile +extensions/cpsection/journalmanagement/Makefile extensions/cpsection/keyboard/Makefile extensions/cpsection/language/Makefile extensions/cpsection/modemconfiguration/Makefile diff --git a/data/icons/Makefile.am b/data/icons/Makefile.am index e1f8fa7..b982f2e 100644 --- a/data/icons/Makefile.am +++ b/data/icons/Makefile.am @@ -5,6 +5,7 @@ sugar_DATA =\ module-about_my_computer.svg\ module-date_and_time.svg\ module-frame.svg\ + module-journalmanagement.svg\ module-keyboard.svg \ module-language.svg \ module-modemconfiguration.svg \ diff --git a/data/icons/module-journalmanagement.svg b/data/icons/module-journalmanagement.svg new file mode 100644 index 000..9250c6f --- /dev/null +++ b/data/icons/module-journalmanagement.svg @@ -0,0 +1,127 @@ +?xml version=1.0 encoding=UTF-8 standalone=no? +svg + xmlns:dc=http://purl.org/dc/elements/1.1/; + xmlns:cc=http://creativecommons.org/ns#; + xmlns:rdf=http://www.w3.org/1999/02/22-rdf-syntax-ns#; + xmlns:svg=http://www.w3.org/2000/svg; + xmlns=http://www.w3.org/2000/svg; + xmlns:sodipodi=http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd; + xmlns:inkscape=http://www.inkscape.org/namespaces/inkscape; + enable-background=new 0 0 55 55 + height=55px + id=Layer_1 + version=1.1 + viewBox=0 0 55 55 + width=55px + x=0px + xml:space=preserve + y=0px + sodipodi:version=0.32 + inkscape:version=0.46 + sodipodi:docname=journalmanagement.svg + inkscape:output_extension=org.inkscape.output.svg.inkscapesodipodi:namedview + inkscape:window-height=827 + inkscape:window-width=1440 + inkscape:pageshadow=2 + inkscape:pageopacity=0.0 + guidetolerance=10.0 + gridtolerance=10.0 + objecttolerance=10.0 + borderopacity=1.0 + bordercolor=#66 + pagecolor=#ff + id=base + showgrid=false + inkscape:zoom=8.9818182 + inkscape:cx=7.7378543 + inkscape:cy=27.5 + inkscape:window-x=0 + inkscape:window-y=25 + inkscape:current-layer=Layer_1 /metadata + id=metadata35rdf:RDFcc:Work + rdf:about=dc:formatimage/svg+xml/dc:formatdc:type + rdf:resource=http://purl.org/dc/dcmitype/StillImage; //cc:Work/rdf:RDF/metadatadefs + id=defs33inkscape:perspective + sodipodi:type=inkscape:persp3d +
Re: [Sugar-devel] [SoaS] Deja-Dup (duplicity) as a way to backup-restore Soas Mirabelle Home directory
Bernie Innocenti wrote: El Sun, 16-05-2010 a las 11:30 -0700, Thomas C Gilliard escribió: Bernie; Will you make a .xo or rpm of your backup for standalone instances of Soas? All we need is a new control panel item in Sugar and add 3 scripts to ds-backup-client. I'm attaching patches to do both things. You can test this functionality in os180py. The current implementation works, but is way too crude for upstreaming it. My TODO list contains: 1) Discuss UI refinements proposed by Eben (see his post to sugar-devel) 2) Integrate the USB backup/restore functionality developed by Esteban for LATU. 3) Address the concerns of Martin Langhoff regarding destroying the current journal contents on restore. How would I convert it to a .xo file? Is there a reference I should consult? I am running from the command line now. Documentation for creating bundles is here: http://wiki.sugarlabs.org/go/Development_Team/Almanac/Activity_Bundles But I feel that backup/restore should be core Sugar functionality, not implemented as an activity. Bernie; Thanks for responding. I am still thinking of the sneakernet use case where there is no networking to use for backup. It does NOT backup or restore the journal. (It will restore to a new unchanged script created USB. (I am still testing). This would be useful if the overlay got corrupted or full.. The deja-dup functionality is neat: Features: • Support for local or remote backup locations, including Amazon S3 • Securely encrypts and compresses your data • Incrementally backs up, letting you restore from any particular backup • Schedules regular backups I have sugarized it so that it is listed in the f3 ring as an icon. The next step is to try to make it into a .xo bundle. Thanks for the link. deja-dup seems to requireit be used on the same version of Soas.iso ie: cannot restore RC3 to a RC2 soas stick. Does not seem to work with f12 Blueberry. (I installed it but get errors on restore) Seems to require the backup USB (fat32) to be paired with a specific stick. Tom Gilliard satellit still testing...: ) Link: http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/deja-dup ___ 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] Paint: patch to #1015
Thanks James!
Trying again...
From dd88a9833d7bf0a4de3dd64bf306c713db84711e Mon Sep 17 00:00:00 2001
From: Gonzalo Odiard gonz...@aronax.(none)
Date: Mon, 17 May 2010 20:43:05 -0300
Subject: [PATCH] fix #1015
---
icons/icon-fill.svg | 11 +++--
icons/icon-stroke.svg | 30 --
toolbox.py| 109
+
3 files changed, 34 insertions(+), 116 deletions(-)
diff --git a/icons/icon-fill.svg b/icons/icon-fill.svg
index bf1925a..d424356 100644
--- a/icons/icon-fill.svg
+++ b/icons/icon-fill.svg
@@ -1,5 +1,7 @@
-?xml version=1.0 encoding=UTF-8 standalone=no?
-!-- Generator: Adobe Illustrator 13.0.0, SVG Export Plug-In . SVG Version:
6.00 Build 14948) --
+?xml version=1.0 ?!DOCTYPE svg PUBLIC '-//W3C//DTD SVG 1.1//EN' '
http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd' [
+!ENTITY stroke_color #010101
+!ENTITY fill_color #FF
+]
svg
xmlns:dc=http://purl.org/dc/elements/1.1/;
xmlns:cc=http://web.resource.org/cc/;
@@ -48,9 +50,10 @@
inkscape:current-layer=svg2 /
path
- style=fill:#ff;display:inline
+ style=fill:fill_color;;display:inline;stroke-opacity:1
stroke-width=3
d=M 48.897307,33.594988 C 48.897307,44.525692 24.353188,48.898307
15.889502,42.513082 C 7.1635122,35.929969 8.1442163,21.098901
17.129718,14.87467 C 22.64423,11.054784 34.272782,10.165018
36.496363,19.452618 C 39.041402,30.082908 48.897307,22.664284
48.897307,33.594988 z
id=circle5
sodipodi:nodetypes=csssc /
-/svg
\ No newline at end of file
+/svg
+
diff --git a/icons/icon-stroke.svg b/icons/icon-stroke.svg
index 71545c8..cb6f5b4 100644
--- a/icons/icon-stroke.svg
+++ b/icons/icon-stroke.svg
@@ -1,5 +1,7 @@
-?xml version=1.0 encoding=UTF-8 standalone=no?
-!-- Generator: Adobe Illustrator 13.0.0, SVG Export Plug-In . SVG Version:
6.00 Build 14948) --
+?xml version=1.0 ?!DOCTYPE svg PUBLIC '-//W3C//DTD SVG 1.1//EN' '
http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd' [
+!ENTITY stroke_color #010101
+!ENTITY fill_color #FF
+]
svg
xmlns:dc=http://purl.org/dc/elements/1.1/;
xmlns:cc=http://web.resource.org/cc/;
@@ -28,29 +30,13 @@
rdf:resource=http://purl.org/dc/dcmitype/StillImage;
//cc:Work/rdf:RDF/metadatadefs
id=defs8
-/defssodipodi:namedview
- inkscape:window-height=941
- inkscape:window-width=1269
- inkscape:pageshadow=2
- inkscape:pageopacity=0.0
- guidetolerance=10.0
- gridtolerance=10.0
- objecttolerance=10.0
- borderopacity=1.0
- bordercolor=#66
- pagecolor=#ff
- id=base
- inkscape:zoom=6.8909091
- inkscape:cx=27.5
- inkscape:cy=15.890501
- inkscape:window-x=0
- inkscape:window-y=27
- inkscape:current-layer=svg2 /
+/defs
path
- style=fill:none;display:inline;stroke:#ff;stroke-opacity:1
+ style=fill:none;display:inline;stroke:fill_color;;stroke-opacity:1
stroke-width=3
d=M 48.897307,33.594988 C 48.897307,44.525692 24.353188,48.898307
15.889502,42.513082 C 7.1635122,35.929969 8.1442163,21.098901
17.129718,14.87467 C 22.64423,11.054784 34.272782,10.165018
36.496363,19.452618 C 39.041402,30.082908 48.897307,22.664284
48.897307,33.594988 z
id=circle5
sodipodi:nodetypes=csssc /
-/svg
\ No newline at end of file
+/svg
+
diff --git a/toolbox.py b/toolbox.py
index 9bed17b..3962b90 100644
--- a/toolbox.py
+++ b/toolbox.py
@@ -72,6 +72,7 @@ from sugar.graphics.toggletoolbutton import
ToggleToolButton
from sugar.graphics.combobox import ComboBox
from sugar.graphics.palette import Palette
from sugar.graphics.menuitem import MenuItem
+from sugar.graphics.colorbutton import ColorToolButton
from sugar.graphics.objectchooser import ObjectChooser
##Create toolbars for the activity
@@ -84,27 +85,27 @@ class Toolbox(ActivityToolbox):
self._edit_toolbar = DrawEditToolbar(activity)
self.add_toolbar(_('Edit'), self._edit_toolbar)
-self._edit_toolbar.show()
+self._edit_toolbar.show_all()
self._tools_toolbar = ToolsToolbar(activity)
self.add_toolbar(_('Tools'), self._tools_toolbar)
-self._tools_toolbar.show()
+self._tools_toolbar.show_all()
self._shapes_toolbar = ShapesToolbar(activity)
self.add_toolbar(_('Shapes'), self._shapes_toolbar)
-self._shapes_toolbar.show()
+self._shapes_toolbar.show_all()
self._text_toolbar = TextToolbar(activity)
self.add_toolbar(_('Text'), self._text_toolbar)
-self._text_toolbar.show()
+self._text_toolbar.show_all()
self._image_toolbar = ImageToolbar(activity)
self.add_toolbar(_('Image'), self._image_toolbar)
-self._image_toolbar.show()
+self._image_toolbar.show_all()
self._effects_toolbar = EffectsToolbar(activity)
self.add_toolbar(_('Effects'), self._effects_toolbar)
-self._effects_toolbar.show()
+self._effects_toolbar.show_all()
#self._view_toolbar = ViewToolbar(activity)
[Sugar-devel] Persistent home setting
Dear List, I am remastering SOAS and would like to set the persistent home to 50MB. What do I need to do? Walter Bender told me that it was set to 0 by default. Many thanks in advance. Mahesh ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Persistent home setting
On Mon, May 17, 2010 at 6:18 PM, Mahesh Jayachandra mahesh_jayachan...@yahoo.com wrote: Dear List, I am remastering SOAS and would like to set the persistent home to 50MB. What do I need to do? See http://wiki.sugarlabs.org/go/LiveOS_image. The persistent storage is set during image installation. 50 MB is quite small and may lead to rapid exhaustion of the write-once overlay. I once experimented with that size and found that I got Journal full messages on first boot. I now test with 100-MB persistent overlays and home directories. --Fred ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] patch #1902: OLPC- Paint Activ ity – Under tools tab, pencil size functional ity is not working.
From 9595fdfcd0c1b26eab566223ecc1ede348c084e9 Mon Sep 17 00:00:00 2001 From: Gonzalo Odiard gonz...@aronax.(none) Date: Mon, 17 May 2010 22:47:47 -0300 Subject: [PATCH] fix #1902 --- Area.py |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/Area.py b/Area.py index 1e5248d..613e66e 100644 --- a/Area.py +++ b/Area.py @@ -350,7 +350,7 @@ class Area(gtk.DrawingArea): if state gtk.gdk.BUTTON1_MASK and self.pixmap != None: if self.tool['name'] == 'pencil': -self.d.brush(widget, coords, self.last, 2, 'circle') +self.d.brush(widget, coords, self.last, self.line_size, 'circle') self.last = coords elif self.tool['name'] == 'eraser': self.d.eraser(widget, coords, self.last, self.line_size, self.tool['line shape']) -- 1.6.6.1 -- Gonzalo Odiard SugarLabs Argentina ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Paint: patch to #1015
On Mon, May 17, 2010 at 08:44:53PM -0300, Gonzalo Odiard wrote:
Thanks James!
Trying again...
The method you're using to include the patch in your HTML e-mail is
causing issues with whitespace, and wrapping of lines, so if you haven't
got a way to fix that (e.g. by using text e-mail), you may have to
resort to attachments.
Here is your patch reformatted back to plain text, and this does apply
for me in git. You can test this yourself:
1. clone the public repository,
2. extract the mail into a file, e.g. /tmp/patch
3. apply it with git am /tmp/patch
4. review the state of the repository using git log, gitk, or other
tools.
From 76e76d9c5a29500980a3fabb9768c5da9baf8f5e Mon Sep 17 00:00:00 2001
From: Gonzalo Odiard gonz...@aronax.(none)
Date: Mon, 17 May 2010 20:43:05 -0300
Subject: [PATCH] fix #1015
---
icons/icon-fill.svg | 11 +++--
icons/icon-stroke.svg | 30 --
toolbox.py| 109 +
3 files changed, 34 insertions(+), 116 deletions(-)
diff --git a/icons/icon-fill.svg b/icons/icon-fill.svg
index bf1925a..99b25c1 100644
--- a/icons/icon-fill.svg
+++ b/icons/icon-fill.svg
@@ -1,5 +1,7 @@
-?xml version=1.0 encoding=UTF-8 standalone=no?
-!-- Generator: Adobe Illustrator 13.0.0, SVG Export Plug-In . SVG Version:
6.00 Build 14948) --
+?xml version=1.0 ?!DOCTYPE svg PUBLIC '-//W3C//DTD SVG 1.1//EN' '
http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd' [
+!ENTITY stroke_color #010101
+!ENTITY fill_color #FF
+]
svg
xmlns:dc=http://purl.org/dc/elements/1.1/;
xmlns:cc=http://web.resource.org/cc/;
@@ -48,9 +50,10 @@
inkscape:current-layer=svg2 /
path
- style=fill:#ff;display:inline
+ style=fill:fill_color;;display:inline;stroke-opacity:1 stroke-width=3
d=M 48.897307,33.594988 C 48.897307,44.525692 24.353188,48.898307
15.889502,42.513082 C 7.1635122,35.929969 8.1442163,21.098901
17.129718,14.87467 C 22.64423,11.054784 34.272782,10.165018 36.496363,19.452618
C 39.041402,30.082908 48.897307,22.664284 48.897307,33.594988 z
id=circle5
sodipodi:nodetypes=csssc /
-/svg
\ No newline at end of file
+/svg
+
diff --git a/icons/icon-stroke.svg b/icons/icon-stroke.svg
index 71545c8..201a754 100644
--- a/icons/icon-stroke.svg
+++ b/icons/icon-stroke.svg
@@ -1,5 +1,7 @@
-?xml version=1.0 encoding=UTF-8 standalone=no?
-!-- Generator: Adobe Illustrator 13.0.0, SVG Export Plug-In . SVG Version:
6.00 Build 14948) --
+?xml version=1.0 ?!DOCTYPE svg PUBLIC '-//W3C//DTD SVG 1.1//EN' '
http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd' [
+!ENTITY stroke_color #010101
+!ENTITY fill_color #FF
+]
svg
xmlns:dc=http://purl.org/dc/elements/1.1/;
xmlns:cc=http://web.resource.org/cc/;
@@ -28,29 +30,13 @@
rdf:resource=http://purl.org/dc/dcmitype/StillImage;
//cc:Work/rdf:RDF/metadatadefs
id=defs8
-/defssodipodi:namedview
- inkscape:window-height=941
- inkscape:window-width=1269
- inkscape:pageshadow=2
- inkscape:pageopacity=0.0
- guidetolerance=10.0
- gridtolerance=10.0
- objecttolerance=10.0
- borderopacity=1.0
- bordercolor=#66
- pagecolor=#ff
- id=base
- inkscape:zoom=6.8909091
- inkscape:cx=27.5
- inkscape:cy=15.890501
- inkscape:window-x=0
- inkscape:window-y=27
- inkscape:current-layer=svg2 /
+/defs
path
- style=fill:none;display:inline;stroke:#ff;stroke-opacity:1
+ style=fill:none;display:inline;stroke:fill_color;;stroke-opacity:1
stroke-width=3
d=M 48.897307,33.594988 C 48.897307,44.525692 24.353188,48.898307
15.889502,42.513082 C 7.1635122,35.929969 8.1442163,21.098901
17.129718,14.87467 C 22.64423,11.054784 34.272782,10.165018 36.496363,19.452618
C 39.041402,30.082908 48.897307,22.664284 48.897307,33.594988 z
id=circle5
sodipodi:nodetypes=csssc /
-/svg
\ No newline at end of file
+/svg
+
diff --git a/toolbox.py b/toolbox.py
index 9bed17b..448847e 100644
--- a/toolbox.py
+++ b/toolbox.py
@@ -72,6 +72,7 @@ from sugar.graphics.toggletoolbutton import ToggleToolButton
from sugar.graphics.combobox import ComboBox
from sugar.graphics.palette import Palette
from sugar.graphics.menuitem import MenuItem
+from sugar.graphics.colorbutton import ColorToolButton
from sugar.graphics.objectchooser import ObjectChooser
##Create toolbars for the activity
@@ -84,27 +85,27 @@ class Toolbox(ActivityToolbox):
self._edit_toolbar = DrawEditToolbar(activity)
self.add_toolbar(_('Edit'), self._edit_toolbar)
-self._edit_toolbar.show()
+self._edit_toolbar.show_all()
self._tools_toolbar = ToolsToolbar(activity)
self.add_toolbar(_('Tools'), self._tools_toolbar)
-self._tools_toolbar.show()
+self._tools_toolbar.show_all()
self._shapes_toolbar = ShapesToolbar(activity)
self.add_toolbar(_('Shapes'), self._shapes_toolbar)
-self._shapes_toolbar.show()
+
Re: [Sugar-devel] [SoaS] Deja-Dup (duplicity) as a way to backup-restore Soas Mirabelle Home directory
Bernie Innocenti wrote: El Mon, 17-05-2010 a las 15:20 -0700, Thomas C Gilliard escribió: I am still thinking of the sneakernet use case where there is no networking to use for backup. It does NOT backup or restore the journal. (It will restore to a new unchanged script created USB. (I am still testing). This would be useful if the overlay got corrupted or full.. Why backup the entire OS when the user can only write to $HOME? You are right. I was experimenting... I will change the instructions to reflect only Home backups, * I have seen / full error messages on restore (Besides, the overlay should never get corrupted because it shouldn't even exist, but that's another story :-) The deja-dup functionality is neat: Yeah, I know it's good: I made everyone in the office use it for their computers. Besides, we use Duplicity to back up all Sugar Labs' servers. We could use Duplicity to backup to USB sticks and even Amazon S3, but I still think that the UI should be integrated with the control panel or perhaps with the Journal (through menu items Back up and Restore directly on the device icon). I agree. Unfortunately that is not something I am able to do Until you, or someone else, can incorporate that function into the CP A Sugarized deja-dup backup will have to do. Cordially; Tom Gilliard ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Paint: patch to #1015
Tested this patch on XO-1.5 with Sugar 0.84. In the Tools tab this patch changes the Tool Color button to Stroke Color, and uses a new colour chooser. Perhaps it should read Tool Color instead, I'm not sure. In the Shapes tab, this patch changes the Fill Color and the Stroke Color buttons, and uses a new colour chooser. Each of the colour choices made are effective for the next drawing operation. Tested-by: James Cameron qu...@laptop.org -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] patch #1902: OLPC- Paint Activity ? Under tools tab, pencil size functionality is not working.
Tested on XO-1.5 with Sugar 0.84. Produces the expected result When user selects different sizes, image thickness should change based on the pencil size selection. I suggest you fix your git config to include a real e-mail address for your patches, rather than gonz...@aronax.(none) git config --global user.email godi...@gmail.com Your patch was also whitespace corrupted. Fixed patch below. Tested-by: James Cameron qu...@laptop.org Reviewed-by: James Cameron qu...@laptop.org From 125a5dc57ab03bb8ac22cbcf259ede6b6857a338 Mon Sep 17 00:00:00 2001 From: Gonzalo Odiard gonz...@aronax.(none) Date: Mon, 17 May 2010 22:47:47 -0300 Subject: [PATCH] fix #1902 --- Area.py |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/Area.py b/Area.py index 1e5248d..613e66e 100644 --- a/Area.py +++ b/Area.py @@ -350,7 +350,7 @@ class Area(gtk.DrawingArea): if state gtk.gdk.BUTTON1_MASK and self.pixmap != None: if self.tool['name'] == 'pencil': -self.d.brush(widget, coords, self.last, 2, 'circle') +self.d.brush(widget, coords, self.last, self.line_size, 'circle') self.last = coords elif self.tool['name'] == 'eraser': self.d.eraser(widget, coords, self.last, self.line_size, self.tool['line shape']) -- 1.7.1 -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Paint: patch to #1015
Thank you. Must I close the bugs? Gonzalo On Mon, May 17, 2010 at 11:12 PM, James Cameron qu...@laptop.org wrote: Tested this patch on XO-1.5 with Sugar 0.84. In the Tools tab this patch changes the Tool Color button to Stroke Color, and uses a new colour chooser. Perhaps it should read Tool Color instead, I'm not sure. In the Shapes tab, this patch changes the Fill Color and the Stroke Color buttons, and uses a new colour chooser. Each of the colour choices made are effective for the next drawing operation. Tested-by: James Cameron qu...@laptop.org -- James Cameron http://quozl.linux.org.au/ -- Gonzalo Odiard Responsable de Desarrollo Sistemas Australes ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Paint: patch to #1015
On Tue, May 18, 2010 at 01:20:48AM -0300, Gonzalo Odiard wrote: Must I close the bugs? I don't know, but I don't think so. The next step is probably for a maintainer of the Paint activity to accept your patches. I don't know who the maintainer is and I've not found a method to determine that. In the git repository, the last commits to change code were by Aleksey and Simon in 2009-06. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Paint: patch to #1015
El Tue, 18-05-2010 a las 01:20 -0300, Gonzalo Odiard escribió: Thank you. Must I close the bugs? I think we first need to ask Manu to apply the patch in git. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Paint: patch to #1015
El Tue, 18-05-2010 a las 14:58 +1000, James Cameron escribió: On Tue, May 18, 2010 at 01:20:48AM -0300, Gonzalo Odiard wrote: Must I close the bugs? I don't know, but I don't think so. The next step is probably for a maintainer of the Paint activity to accept your patches. I don't know who the maintainer is and I've not found a method to determine that. I look for the maintainer of the project in git.sugarlabs.org. Let me know if you spot inconsistencies. Random Thought of the Day: we should really think of adding metadata such as maintainer, packager and author to activity.info and display this information in the drop-down menu of the activity close button. In the git repository, the last commits to change code were by Aleksey and Simon in 2009-06. If nobody is currently maintaining Paint, perhaps we could orphan it so Gonzalo could take it over from now on. (Gonzalo, if you have no past experience working with Gitorious, meet me on #sugar for a quick walk-through). -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Fwd: [PATCH] use the spanish verb quitar for unmounting devices]
2010/5/17 Bernie Innocenti ber...@codewiz.org: El Mon, 17-05-2010 a las 09:24 +0200, Tomeu Vizoso escribió: On Sun, May 16, 2010 at 20:07, Bernie Innocenti ber...@codewiz.org wrote: This was also supposed to be posted on the list: - Mensaje reenviado De: Bernie Innocenti ber...@codewiz.org Para: Tomeu Vizoso to...@sugarlabs.org Cc: Sayamindu Dasgupta sayami...@gmail.com, de...@lists.sugarlabs.org, Bernie Innocenti ber...@codewiz.org Asunto: [PATCH] use the spanish verb quitar for unmounting devices Fecha: Sun, 16 May 2010 13:44:05 -0400 In Sugar 0.88, the command for unmounting removable devices has been renamed from Unmount to Remove, which is used throughout the GUI with several slightly different meanings. The common translation for remove was eliminar, whose semantic meaning is eliminate, thus inappropriate for the unmount operation. I like ''extraer'' but ''quitar'' is used commonly in other interfaces for the same purpose, ''quitar'' would be my option, also because it's easier to understand for little children. Other languages may not be so lucky. We may have to keep the string for unmounting devices distinct from the others, along with a TRNAS comment to warn translators about the context. --- po/es.po | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/po/es.po b/po/es.po index 587608f..6702db6 100644 --- a/po/es.po +++ b/po/es.po @@ -975,7 +975,7 @@ msgstr Transferencia a %r #: ../src/jarabe/frame/clipboardmenu.py:52 ../src/jarabe/view/palettes.py:218 msgid Remove -msgstr Eliminar +msgstr Quitar Retirar would also work in Spanish from Spain, is slightly more formal than Quitar but is also a bit more specific. I would say to just ask around in your office and do whatever they tell you is best. I've ran a quick survey. Sebastian said: Expulsar is common in other OSs, Retirar is correct but not direct enough to be clear, and Quitar is too broad and also unclear. Jorge proposed: Extraer. In both cases, we need to make the strings distinct in the code. In C, I'd specify the context in which the string is used, like so: pgettext(Device Icon, Remove) However, Python's gettext module does not yet support pgettext(): http://bugs.python.org/issue2504 How is this handled in Sugar? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ 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] [RFC PATCH v0 0/8] Journal sorting by file size and creation time.
I'm unqualified to review your code, but I've included both your patch series both in my sugar-jhbuild environment and in my Sugar 0.88 packages for Fedora 11. El Sat, 01-05-2010 a las 16:33 -0300, Andrés Ambrois escribió: Andrés Ambrois (8): Journal: Retrieve ctime and filesize from the datastore. Add ctime and filesize columns to the journal list model. Add add_separator method for convenience. Add a ListViewButton to the journal search toolbar. Rename the date column to 'sort_column' Add sort_by method to the journal list view. Call sort_by in the list view when sorting is selected in the toolbar. Expandedentry: Try to use the filesize property. Tested-by: Bernie Innocenti ber...@codewiz.org Andrés Ambrois (2): Add ctime and timestamp properties to the index. Add migration from DS v0 code for the new properties. Tested-by: Bernie Innocenti ber...@codewiz.org Problems: * size display does not work on removable devices: all files are shown as empty. * I forgot to include the patch to increment CURRENT_LAYOUT_VERSION, which caused old journal entries to report an empty size, but no other problems. * The icon for the new toolbar button is missing -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
