Re: [Sugar-devel] Development Meetings
On Tue, Oct 26, 2010 at 08:39:48AM +1300, Tim McNamara wrote: > 14:00 UTC is 2am for me.. It is 1am for me. I won't be attending because /dev/brain will have shut down for the day. -- 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] [Dextrose] Pending patchs for Paint
On Mon, Oct 25, 2010 at 01:07:20PM +0100, Gary Martin wrote: > On Monday, October 25, 2010, James Cameron wrote: > > (composite reply to several postings in thread) > > On Fri, Oct 22, 2010 at 03:16:49PM +0100, Gary Martin wrote: > >> On 20 Oct 2010, at 21:56, James Cameron wrote: > >> > On Wed, Oct 20, 2010 at 04:56:41PM +0100, Gary Martin wrote: > >> > > ? http://git.sugarlabs.org/projects/paint/repos/mainline > >> > > > >> > > I noticed that the activity.info file is still for version 27. As > >> > > Paint-28 has been released I'd expect to mainline to at least be > >> > > up to date with those commits. Maybe the rest of the source is > >> > > current, and it's just the activity.info file change that was not > >> > > pushed? > >> > > >> > While it would be nice if every release of every activity has a > >> > matching tag and sources in the respective repository, we've had > >> > situations where that has not been desirable, such as when a version > >> > of Record was released for a deployment via activities.sugarlabs.org > >> > but the changes were not accepted into mainline because consensus > >> > had not been reached. > >> > >> In such cases git.sugarlabs.org provides very easy cloning of any rep > >> where deployments can have full control and create, say, a custom > >> Record-Peru. > > > > It might not have been easy enough, because it wasn't chosen as the > > solution to the issue at the time. > > > >> > A release of an activity is not done using the master repository, it > >> > is done using a local clone of the repository. ?Therefore during > >> > testing and diagnosis I've always presumed that the source code > >> > shipped in the .xo file might be different to the tagged source in > >> > the master repository. > >> > >> Hmm, I'd have to disagree. This seems like a terrible workflow for a > >> community. [...] > > > > How would you make activities be released from a master repository? ?You > > would automate the release mechanism somehow? ?You would add one more > > person to the release sequence? ?Or you would refuse to list activities > > on activities.sugarlabs.org unless they match a master repository? > > No, I was just trying to suggest that it is a very good habit to keep > master in sync with the activity bundle releases. Yes, good habit, but it doesn't always happen, and I would not expect it to happen for 100% of releases. There have been exceptions, and so there will be more exceptions. > FWIW, it's actually much easier for a maintainer (my opinion) to > review and merge work when it's been made in a clone in gitiorus, I disagree. I find it much easier to review patches than to work with a clone. The patches have already arrived in mail. The clone is on the other end of a network link. We should not discriminate against remote contributors, especially given the focus of the project on learners from remote areas. > think it's also easier for who ever is making the patches as well > given all the git fu has seems to be needed to email patches... Really, it's not that hard. How have we failed to explain it? Edit source, commit, format-patch and add to mail, or try git send-email if you have a working e-mail configuration. -- 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] Moving forward.
Hi David and all. On Mon, Oct 25, 2010 at 7:30 PM, David Farning wrote: > Yesterday I sent a rather blunt email on my concerns about the > project. It seems the observations resonated with many people while > striking several nerves. The volume of private mail or CCed mail (to > a subset of the Sugar Labs participants) responses was unexpectedly > high. > > The five main themes of the responses are: > 1. "Could you possibility be any more abstract?" > 2. "Several of the points are valid. Here are my > responses/suggestions. This should be on a public thread, but someone > else will have to start it." > 3. "The core problem is trust." > 4. "This conversation is like an iceberg, the 'community' only sees > 10% and not the other 90%." > 5. "Dave you are just a jerk, now shut up." > > For better of worse, all five points are valid. I am a bumbling jerk > who is struggling to rebuild community trust without airing anyone's > dirty laundry, including my own. > > To put all of my cards on the table: > 1. The ideas driving OLPC and Sugar are sound. > 2. Sugar Labs will continue to fragment until the issue of trust is > resolved. > 3. Because of this, I left Sugar Labs to start a business which > provides service and support for Sugar. > 4. I need Sugar to succeed. I need OLPC to succeed. > 5. I have been trying to operate 'under the radar' because some in > Sugar Labs and OLPC have contacted individuals I am working with and > 'suggested' that they not work with me. > > Talk about the pot calling the kettle black. I get pissed off about > the lack of trust and community building in Sugar Labs, so I go off > and form a fork which operates largely in secret. > > Two years ago, I suggested that the over sight board appoint Walter > Bender as Executive Director of Sugar Labs so he would be able to > speak on behalf of Sugar Labs. He had three skills which Sugar Labs > needed. 1) He was able to clearly and effectively communicate the > goals of Sugar and the mission of Sugar Labs. 2) He was able to create > an identity for Sugar Labs outside of OLPC. 3) He was a tireless > advocate for Sugar. In the past two years Sugar Labs has progressed, > largely because of Walter. The goal of sugar and Sugar labs is well > understood. Sugar Labs has a clear identity. > > Now, Sugar Labs has different needs; pragmatic bridge building between > individuals and organization. It is time to look for someone with > those particular skill to lead/herd Sugar Labs forward. As such I > would like to recommend that SLOB ask and appoint Adam Holt as the > next Executive Director of Sugar Labs. > david > In the last email you mentioned key points of possible actual weakness of Sugar Labs, in my opinion changing executive Director doesn't address all these points, we need more community discussions about those. ___ > 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] Mailman's admin and archive interfaces are horrible - suggest GroupServer.org
On 10/17/2010 07:15 PM, Tim McNamara wrote: > I'm assuming the infrastructure team are part of this list. We are, sorry for the long reply time. > The archives are easily searchable, attached files are converted to links to > the server so that people's inboxes are not flooded. Removing inline attachments may break PGP/MIME, (although I haven't checked) and some people consider being able to read a message offline in its entirety a feature. I hope that behavior is configurable. > I welcome any feedback. I think that a migration like this will make the > mailing lists far more accessible as a knowledge archive. I've been assured > that there is a migration path from mailman[4]. From what I know of Dan, its > lead developer, it should be fairly easy & reliable. I'll take a look at it. For it to be seriously considered, a mailman path would be needed. The linked tweet notwithstanding, I've not seen any documentation on such a migration. -- ╒═╕ │Luke Faraone ╭Debian / Ubuntu Developer╮│ │http://luke.faraone.cc╰Sugar Labs, Systems Admin╯│ │PGP: 5189 2A7D 16D0 49BB 046B DC77 9732 5DD8 F9FD D506 │ ╘═╛ 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] [Dextrose] [PATCH v5 sugar] Pulsing icon delayed by 5 seconds or so SL#2080
On Sun, 2010-10-24 at 18:47 +0100, Gary Martin wrote: > We did play around with a few ideas when Wade last worked on the pulse > optimisation/enhancements. He landed improvements for speed by > minimising the area being redrawn, and landed the addition of the > "failed to launch" check and button/message. He also found a few extra > cpu seconds worth of improvement that didn't land in time. The trick > was to fade in, _hold_, fade out, _hold_, the effect is still of > pulsing activity but you can get away with less frames as you don't > need to redraw anything during the hold. The actual problem is that rendering complex svg icons takes so long on the XO-1 that when we exit from the update hook, it's already time to render the next frame. Thus, the event loop never goes idle, which is where gtk normally updates the display. A possible workaround consists in adjusting the frame rate dynamically in the Animator class, based on how long it took to render the previous frame. It's a simple technique used by video players and games. It shouldn't take more than 2 lines of code, but I can't predict how well it will work in this case, because from Anurag's measurements it looks like it would take several seconds on the XO-1 to render just one frame of the animation. If this turns out to be true, we might want to completely disable both zooming and flashing on machines that are obviously too slow to support it decently. > This doesn't effect the initial start-up however, which I believe was > the original ticket... FWIW I think F14 builds have regressed for some > other reason here, perhaps it's the window manager being laggy (I > occasionally see window bezels before things go full screen). The bug also occurs in F11, with Dextrose 2 and OLPC OS 10.2.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] Moving forward.
Yesterday I sent a rather blunt email on my concerns about the project. It seems the observations resonated with many people while striking several nerves. The volume of private mail or CCed mail (to a subset of the Sugar Labs participants) responses was unexpectedly high. The five main themes of the responses are: 1. "Could you possibility be any more abstract?" 2. "Several of the points are valid. Here are my responses/suggestions. This should be on a public thread, but someone else will have to start it." 3. "The core problem is trust." 4. "This conversation is like an iceberg, the 'community' only sees 10% and not the other 90%." 5. "Dave you are just a jerk, now shut up." For better of worse, all five points are valid. I am a bumbling jerk who is struggling to rebuild community trust without airing anyone's dirty laundry, including my own. To put all of my cards on the table: 1. The ideas driving OLPC and Sugar are sound. 2. Sugar Labs will continue to fragment until the issue of trust is resolved. 3. Because of this, I left Sugar Labs to start a business which provides service and support for Sugar. 4. I need Sugar to succeed. I need OLPC to succeed. 5. I have been trying to operate 'under the radar' because some in Sugar Labs and OLPC have contacted individuals I am working with and 'suggested' that they not work with me. Talk about the pot calling the kettle black. I get pissed off about the lack of trust and community building in Sugar Labs, so I go off and form a fork which operates largely in secret. Two years ago, I suggested that the over sight board appoint Walter Bender as Executive Director of Sugar Labs so he would be able to speak on behalf of Sugar Labs. He had three skills which Sugar Labs needed. 1) He was able to clearly and effectively communicate the goals of Sugar and the mission of Sugar Labs. 2) He was able to create an identity for Sugar Labs outside of OLPC. 3) He was a tireless advocate for Sugar. In the past two years Sugar Labs has progressed, largely because of Walter. The goal of sugar and Sugar labs is well understood. Sugar Labs has a clear identity. Now, Sugar Labs has different needs; pragmatic bridge building between individuals and organization. It is time to look for someone with those particular skill to lead/herd Sugar Labs forward. As such I would like to recommend that SLOB ask and appoint Adam Holt as the next Executive Director of Sugar Labs. david ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Vizualisation of the Write activity develpment (gource)
On Mon, 2010-10-25 at 12:58 +0200, Bastien wrote: > http://olpc-france.org/blog/2010/10/visualiser-le-developpement-de-sugar/ Gnash doesn't seem to work with Vimeo's flash player, so I can't watch the videos. Maybe switch to HTML5? -- // 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] [ASLO] Release Turtle Blocks-101
Activity Homepage: http://activities.sugarlabs.org/addon/4027 Sugar Platform: 0.82 - 0.90 Download Now: http://activities.sugarlabs.org/downloads/file/27086/turtle_art-101.xo Release notes: * set text color to foreground color (#2448) * more resilience to bad block descriptions (#2447) * fixed typo in Python sample code (#2449) * only allow one start block per project * show box values on box label * moved import/export functions off activity toolbar onto journal toolbar * new DE translations Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Vizualisation of the Write activity develpment (gource)
Bernie Innocenti writes: > On Mon, 2010-10-25 at 13:02 -0400, Walter Bender wrote: >> > If that's useful I'll try to translate this entry in english, but I'm >> > still unsure about our policy for having a bilingual blog. Will keep >> > you posted. >> >> We host many non-English blogs in out planet. Yours would be quite welcome :) > > Indeed. See: > > http://wiki.sugarlabs.org/go/Sysadmin/Planet_syndication_request Done - thanks for the link! -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release Visual Match-27
Activity Homepage: http://activities.sugarlabs.org/addon/4246 Sugar Platform: 0.82 - 0.90 Download Now: http://activities.sugarlabs.org/downloads/file/27085/visual_match-27.xo Release notes: 27 * smiley-face "reward" for finishing a game * work around datastore.find issue on 0.84 builds * work around chooser issues with old Sugar builds (#2398) * improved workflow for importing custom cards Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Vizualisation of the Write activity develpment (gource)
On Mon, 2010-10-25 at 13:02 -0400, Walter Bender wrote: > > If that's useful I'll try to translate this entry in english, but I'm > > still unsure about our policy for having a bilingual blog. Will keep > > you posted. > > We host many non-English blogs in out planet. Yours would be quite welcome :) Indeed. See: http://wiki.sugarlabs.org/go/Sysadmin/Planet_syndication_request -- // 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] [PATCH v8] Downgrading activities not allowed. (SL #2164)
On Mon, Oct 25, 2010 at 07:31:27PM +0530, shan...@seeta.in wrote:
> From: Shanjit Singh Jajmann , Anubhav Aggarwal
>
>
> Activity can be downgraded on the availability of an older .xo version of an
> activity. An alert pops up when trying to install an older .xo file of an
> activity, which asks the user to make a selection on whether to move to an
> older activity version or not.
>
> Co-authored-by: Shanjit Singh Jajmann
> Co-authored-by: Anubhav Aggarwal
Thanks, pushed
(with minor renaming tweak,
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/5490d41ec310543b1819165f5209020e15411863)
> ---
>
> v1 -> v2. Inline function used, signal emission condition revised and global
> variables removed. Recommendations by James Cameron and Aleksey Lim added.
>
> v2 -> v3. Used misc.resume.
>
> v3 -> v4. Changes in the copyright of the new file.
>
> v4 -> v5. Alert shown in the same window as the journal.
>
> v5 -> v6. Static variable removed, name of the functions changed.
> Recommendations by James Cameron and Aleksey Lim added.
>
> v6 -> v7. Logic for the alert pop up made simpler.
> Recommendations by Aleksay Lim added.
>
> v7 -> v8. Missing file added.
> ---
> src/jarabe/journal/journalactivity.py |5 ++-
> src/jarabe/journal/journalwindow.py | 34 +++
> src/jarabe/journal/misc.py| 47 ++--
> src/jarabe/model/bundleregistry.py|7 +++-
> 4 files changed, 80 insertions(+), 13 deletions(-)
> create mode 100644 src/jarabe/journal/journalwindow.py
>
> diff --git a/src/jarabe/journal/journalactivity.py
> b/src/jarabe/journal/journalactivity.py
> index 44cc018..beb0962 100644
> --- a/src/jarabe/journal/journalactivity.py
> +++ b/src/jarabe/journal/journalactivity.py
> @@ -44,6 +44,7 @@ from jarabe.journal.journalentrybundle import
> JournalEntryBundle
> from jarabe.journal.objectchooser import ObjectChooser
> from jarabe.journal.modalalert import ModalAlert
> from jarabe.journal import model
> +from jarabe.journal.journalwindow import JournalWindow
>
> J_DBUS_SERVICE = 'org.laptop.Journal'
> J_DBUS_INTERFACE = 'org.laptop.Journal'
> @@ -102,10 +103,10 @@ class JournalActivityDBusService(dbus.service.Object):
> def ObjectChooserCancelled(self, chooser_id):
> pass
>
> -class JournalActivity(Window):
> +class JournalActivity(JournalWindow):
> def __init__(self):
> logging.debug("STARTUP: Loading the journal")
> -Window.__init__(self)
> +JournalWindow.__init__(self)
>
> self.set_title(_('Journal'))
>
> diff --git a/src/jarabe/journal/journalwindow.py
> b/src/jarabe/journal/journalwindow.py
> new file mode 100644
> index 000..3c718c2
> --- /dev/null
> +++ b/src/jarabe/journal/journalwindow.py
> @@ -0,0 +1,34 @@
> +#Copyright (C) 2010 Software for Education, Entertainment and Training
> +#Activities
> +#
> +# This program is free software; you can redistribute it and/or modify
> +# it under the terms of the GNU General Public License as published by
> +# the Free Software Foundation; either version 2 of the License, or
> +# (at your option) any later version.
> +#
> +# This program is distributed in the hope that it will be useful,
> +# but WITHOUT ANY WARRANTY; without even the implied warranty of
> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> +# GNU General Public License for more details.
> +#
> +# You should have received a copy of the GNU General Public License
> +# along with this program; if not, write to the Free Software
> +# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
> +
> +import gtk
> +from sugar.graphics.window import Window
> +
> +_journal_window = None
> +
> +
> +class JournalWindow(Window):
> +
> +def __init__(self):
> +
> +global _journal_window
> +Window.__init__(self)
> +_journal_window = self
> +
> +
> +def get_journal_window():
> +return _journal_window
> diff --git a/src/jarabe/journal/misc.py b/src/jarabe/journal/misc.py
> index 32a2847..122feca 100644
> --- a/src/jarabe/journal/misc.py
> +++ b/src/jarabe/journal/misc.py
> @@ -27,8 +27,10 @@ from sugar.activity import activityfactory
> from sugar.activity.activityhandle import ActivityHandle
> from sugar.graphics.icon import get_icon_file_name
> from sugar.graphics.xocolor import XoColor
> +from sugar.graphics.alert import ConfirmationAlert
> from sugar import mime
> from sugar.bundle.activitybundle import ActivityBundle
> +from sugar.bundle.bundle import AlreadyInstalledException
> from sugar.bundle.contentbundle import ContentBundle
> from sugar import util
>
> @@ -36,6 +38,7 @@ from jarabe.view import launcher
> from jarabe.model import bundleregistry, shell
> from jarabe.journal.journalentrybundle import JournalEntryBundle
> from jarabe.journal import model
> +from jarabe.journal import journalwindow
>
> def _get_icon_for_mime(mime_type):
> generic_types = mime.get
Re: [Sugar-devel] Development Meetings
Excerpts from Tim McNamara's message of Mon Oct 25 21:39:48 +0200 2010: > 14:00 UTC is 2am for me.. If I have anything to contribute on the agenda > items, should I send an email to sugar-devel or the meeting chair? Would you like to participate regularly and/or this time? For a specific topic or the whole meeting? What times would be preferred by resp. acceptable for you? Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Development Meetings
On Tue, Oct 26, 2010 at 08:39:48AM +1300, Tim McNamara wrote:
> On 26 October 2010 02:45, Aleksey Lim wrote:
>
> > On Mon, Oct 25, 2010 at 01:29:07PM +, Walter Bender wrote:
> > > On Mon, Oct 25, 2010 at 12:59 PM, Aleksey Lim
> > wrote:
> > > > On Mon, Oct 25, 2010 at 08:13:24AM -0400, Walter Bender wrote:
> > > >> On Mon, Oct 25, 2010 at 8:09 AM, Aleksey Lim
> > wrote:
> > > >> > Hi all,
> > > >> >
> > > >> > Since we don't have team lead (for a long time) there a bunch of
> > > >> > questions that need to be fixed.
> > > >> >
> > > >> > (imho, we might not even need team lead for Development Team, all
> > > >> > questions might be solved in process while, weekly/daily on-purpose
> > > >> > meetings. Lead is required eg for community relationships or an
> > > >> > architect)
> >
> > For me, default time is ok
> >
> >Wednesday
> >2010-10-27, 14:00 UTC
> >irc://irc.freenode.net#sugar-meeting
>
>
> 14:00 UTC is 2am for me..
Is it ok for you? 14:00 UTC because it is default time for Development
Team meetings assuming that it was convenient for majority of developers
in the past.
> If I have anything to contribute on the agenda
> items, should I send an email to sugar-devel or the meeting chair?
Just add-new/extend-existed topics on
http://wiki.sugarlabs.org/go/Development_Team/Meetings#Upcoming_Agenda
("sign" it with "" substring in entered text)
--
Aleksey
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release Labyrinth-10
Activity Homepage: http://activities.sugarlabs.org/addon/4078 Sugar Platform: 0.82 - 0.90 Download Now: http://activities.sugarlabs.org/downloads/file/27084/labyrinth-10.xo Release notes: Change to black the default foreground text color. Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Development Meetings
Excerpts from Aleksey Lim's message of Mon Oct 25 15:45:21 +0200 2010: > For me, default time is ok > > Wednesday > 2010-10-27, 14:00 UTC > irc://irc.freenode.net#sugar-meeting > > How about other possible attenders? Mon-Wed is fine with me in general. Thu evening (CET ~= UTC) and Fri-Sun are OK, but not preferred. Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Development Meetings
On 26 October 2010 02:45, Aleksey Lim wrote: > On Mon, Oct 25, 2010 at 01:29:07PM +, Walter Bender wrote: > > On Mon, Oct 25, 2010 at 12:59 PM, Aleksey Lim > wrote: > > > On Mon, Oct 25, 2010 at 08:13:24AM -0400, Walter Bender wrote: > > >> On Mon, Oct 25, 2010 at 8:09 AM, Aleksey Lim > wrote: > > >> > Hi all, > > >> > > > >> > Since we don't have team lead (for a long time) there a bunch of > > >> > questions that need to be fixed. > > >> > > > >> > (imho, we might not even need team lead for Development Team, all > > >> > questions might be solved in process while, weekly/daily on-purpose > > >> > meetings. Lead is required eg for community relationships or an > > >> > architect) > > For me, default time is ok > >Wednesday >2010-10-27, 14:00 UTC >irc://irc.freenode.net#sugar-meeting 14:00 UTC is 2am for me.. If I have anything to contribute on the agenda items, should I send an email to sugar-devel or the meeting chair? Tim ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] SL Bug# 2063 : Sugar should bring up an alert when an unhandled Python exception occurs
Probably that is not a good ticket to start to hack in Sugar.
Actually, there are a few python process running all the time,
sugar-session, datastore-service, and in sugar < 0.90,
sugar-presence-service.
Gonzalo
On Mon, Oct 25, 2010 at 3:29 PM, Mukul Gupta wrote:
> Bernie,
>
> Wish to have your feedback on the design aspect of the ticket 2063 (Sugar
> should bring up an alert when an unhandled Python exception occurs) - please
> find the git diff attached below. This is an attempt to display an alert
> when an unhandled Python exception occurs in the journal. Unfortunately,
> when the exception takes place in journalactivity.py , I am neither unable
> to notice the Journal Icon (it disappears),
>
> Please find my explanations on the code added as comments.
>
> diff --git a/journalactivity.py b/journalactivity.py
> index 44cc018..36a2e2e 100644
> --- a/journalactivity.py
> +++ b/journalactivity.py
> @@ -358,8 +358,20 @@ class JournalActivity(Window):
> self.show_main_view()
> self.search_grab_focus()
>
> ''' Defining an Error Alert function in the Journal Activity Class which
> displays the message as
>
> Operation could not be performed
> Please check the logviewer activity for details
> and an OK button
> '''
>
>
> +def uncaught_exception_alert(self):
> +alert = ErrorAlert(title="Operation could not be performed",
> msg="Please check the logviewer activity for details ")
> +alert.connect('response', self.__alert_response_cb)
> +self.add_alert(alert)
> +alert.show()
> +
> _journal = None
>
> '''
> Defining a function which logs the unhandled exception as well as calls the
> Error Alert in the Journal whenever any uncaught exception occurs
> '''
>
> +def _alert_excepthook(exc_type, exc_value, traceback):
> +logging.exception('Unhandled Python exception: %s', repr((exc_type,
> exc_value, traceback)))
> +_journal.uncaught_exception_alert()
> +
> '''
> When an exception is raised and uncaught, sys.excepthook is called with
> three arguments, the exception class, exception instance, and a traceback
> object.The function _alert_excepthook is called only when an unhandled
> exception occurs.
> '''
> +sys.excepthook = _alert_excepthook
> +
> def get_journal():
> global _journal
> if _journal is None:
>
>
> I wish to request you to please review the code and suggest desired
> changes, if any.
>
> Moreover, I have two important questions regarding the bug.
>
> 1. To catch all unhandled python exceptions in sugar, where exactly should
> we be looking forward to be the venue for adding the functionality?
>
> Adding it in journalactivity.py doesn't seem to serve all purposes. It
> has to be added somewhere which is being used all the time.
>
> 2. Wish if you could recommend on the GUI feature that could be used for
> displaying the alert message to the user.
>
> Looking forward to for your valuable suggestions,
>
>
> Regards,
>
> Mukul Gupta
> Research Engineer,SEETA
>
> ___
> 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] [DESIGN] SL Bug# 2063 : Sugar should bring up an alert when an unhandled Python exception occurs
Bernie,
Wish to have your feedback on the design aspect of the ticket 2063 (Sugar
should bring up an alert when an unhandled Python exception occurs) - please
find the git diff attached below. This is an attempt to display an alert
when an unhandled Python exception occurs in the journal. Unfortunately,
when the exception takes place in journalactivity.py , I am neither unable
to notice the Journal Icon (it disappears),
Please find my explanations on the code added as comments.
diff --git a/journalactivity.py b/journalactivity.py
index 44cc018..36a2e2e 100644
--- a/journalactivity.py
+++ b/journalactivity.py
@@ -358,8 +358,20 @@ class JournalActivity(Window):
self.show_main_view()
self.search_grab_focus()
''' Defining an Error Alert function in the Journal Activity Class which
displays the message as
Operation could not be performed
Please check the logviewer activity for details
and an OK button
'''
+def uncaught_exception_alert(self):
+alert = ErrorAlert(title="Operation could not be performed",
msg="Please check the logviewer activity for details ")
+alert.connect('response', self.__alert_response_cb)
+self.add_alert(alert)
+alert.show()
+
_journal = None
'''
Defining a function which logs the unhandled exception as well as calls the
Error Alert in the Journal whenever any uncaught exception occurs
'''
+def _alert_excepthook(exc_type, exc_value, traceback):
+logging.exception('Unhandled Python exception: %s', repr((exc_type,
exc_value, traceback)))
+_journal.uncaught_exception_alert()
+
'''
When an exception is raised and uncaught, sys.excepthook is called with
three arguments, the exception class, exception instance, and a traceback
object.The function _alert_excepthook is called only when an unhandled
exception occurs.
'''
+sys.excepthook = _alert_excepthook
+
def get_journal():
global _journal
if _journal is None:
I wish to request you to please review the code and suggest desired changes,
if any.
Moreover, I have two important questions regarding the bug.
1. To catch all unhandled python exceptions in sugar, where exactly should
we be looking forward to be the venue for adding the functionality?
Adding it in journalactivity.py doesn't seem to serve all purposes. It
has to be added somewhere which is being used all the time.
2. Wish if you could recommend on the GUI feature that could be used for
displaying the alert message to the user.
Looking forward to for your valuable suggestions,
Regards,
Mukul Gupta
Research Engineer,SEETA
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [RELEASE] Turtle Blocks 101
More bug fixes and also, inspired by my latest school visit, variable blocks show their content. == Source == http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-101.tar.bz2 == News == BUG FIXES: * set text color to foreground color (#2448) * more resilience to bad block descriptions (#2447) * fixed typo in Python sample code (#2449) * only allow one start block per project NEW FEATURE: * show block value in variable block label, e.g., heading = 90 MISC: * moved import/export functions off overcrowded activity toolbar onto journal toolbar * new DE translations -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Vizualisation of the Write activity develpment (gource)
On Mon, Oct 25, 2010 at 6:58 AM, Bastien wrote: > Hi all, > > Bastien writes: > >> Thanks! I'm nearly done with producing the video from Michael's repo. >> I will also produce one from Marco's, it will be more useful. > > I just published a blog entry with the gource video about the Write > activité and the one about the Sugar core modules (from Marco's repo): > > http://olpc-france.org/blog/2010/10/visualiser-le-developpement-de-sugar/ > > If that's useful I'll try to translate this entry in english, but I'm > still unsure about our policy for having a bilingual blog. Will keep > you posted. We host many non-English blogs in out planet. Yours would be quite welcome :) -walter > > Enjoy, > > -- > Bastien > __ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Development Meetings
On Mon, Oct 25, 2010 at 10:56 AM, Martin Jose Abente Lahaye wrote: > Great initiative :) See you all there. > > On Mon, Oct 25, 2010 at 10:45 AM, Aleksey Lim > wrote: >> >> On Mon, Oct 25, 2010 at 01:29:07PM +, Walter Bender wrote: >> > On Mon, Oct 25, 2010 at 12:59 PM, Aleksey Lim >> > wrote: >> > > On Mon, Oct 25, 2010 at 08:13:24AM -0400, Walter Bender wrote: >> > >> On Mon, Oct 25, 2010 at 8:09 AM, Aleksey Lim >> > >> wrote: >> > >> > Hi all, >> > >> > >> > >> > Since we don't have team lead (for a long time) there a bunch of >> > >> > questions that need to be fixed. >> > >> > >> > >> > (imho, we might not even need team lead for Development Team, all >> > >> > questions might be solved in process while, weekly/daily on-purpose >> > >> > meetings. Lead is required eg for community relationships or an >> > >> > architect) >> > >> > >> > >> > So, I'm proposing to have weekly on-purpose meetings. All people >> > >> > who have >> > >> > questions for Development Team, that might be useful to discuss >> > >> > having a >> > >> > concilium of interested in developers, are welcome. All people who >> > >> > take >> > >> > part in core coding are welcome as well. >> > >> > >> > >> > I've added topics that are important for me[1], add that is >> > >> > important >> > >> > for you. >> > >> > >> > >> > >> > >> > http://wiki.sugarlabs.org/go/Development_Team/Meetings#Upcoming_Agenda >> > >> > >> > >> > -- >> > >> > Aleksey >> > >> > ___ >> > >> > Sugar-devel mailing list >> > >> > Sugar-devel@lists.sugarlabs.org >> > >> > http://lists.sugarlabs.org/listinfo/sugar-devel >> > >> > >> > >> >> > >> +1 >> > >> >> > >> When is the next meeting? Wednesday? >> > > >> > > [1] says on Mondays, but I guess we can make an exclusion. >> > > >> > > Wednesday sounds reasonable for me, I guess it is enough to let people >> > > a time to be prepared to announced (current and possibly new) topics. >> > >> > I guess I didn't see a date for the upcoming meeting on [1]... I was >> > just guessing Wednesday. What time? #sugar-meeting, I presume. >> >> For me, default time is ok >> >> Wednesday >> 2010-10-27, 14:00 UTC >> irc://irc.freenode.net#sugar-meeting >> >> How about other possible attenders? >> >> -- >> 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 > > I'll be there as an observer Steven ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Development Meetings
Great initiative :) See you all there. On Mon, Oct 25, 2010 at 10:45 AM, Aleksey Lim wrote: > On Mon, Oct 25, 2010 at 01:29:07PM +, Walter Bender wrote: > > On Mon, Oct 25, 2010 at 12:59 PM, Aleksey Lim > wrote: > > > On Mon, Oct 25, 2010 at 08:13:24AM -0400, Walter Bender wrote: > > >> On Mon, Oct 25, 2010 at 8:09 AM, Aleksey Lim > wrote: > > >> > Hi all, > > >> > > > >> > Since we don't have team lead (for a long time) there a bunch of > > >> > questions that need to be fixed. > > >> > > > >> > (imho, we might not even need team lead for Development Team, all > > >> > questions might be solved in process while, weekly/daily on-purpose > > >> > meetings. Lead is required eg for community relationships or an > > >> > architect) > > >> > > > >> > So, I'm proposing to have weekly on-purpose meetings. All people who > have > > >> > questions for Development Team, that might be useful to discuss > having a > > >> > concilium of interested in developers, are welcome. All people who > take > > >> > part in core coding are welcome as well. > > >> > > > >> > I've added topics that are important for me[1], add that is > important > > >> > for you. > > >> > > > >> > > http://wiki.sugarlabs.org/go/Development_Team/Meetings#Upcoming_Agenda > > >> > > > >> > -- > > >> > Aleksey > > >> > ___ > > >> > Sugar-devel mailing list > > >> > Sugar-devel@lists.sugarlabs.org > > >> > http://lists.sugarlabs.org/listinfo/sugar-devel > > >> > > > >> > > >> +1 > > >> > > >> When is the next meeting? Wednesday? > > > > > > [1] says on Mondays, but I guess we can make an exclusion. > > > > > > Wednesday sounds reasonable for me, I guess it is enough to let people > > > a time to be prepared to announced (current and possibly new) topics. > > > > I guess I didn't see a date for the upcoming meeting on [1]... I was > > just guessing Wednesday. What time? #sugar-meeting, I presume. > > For me, default time is ok > >Wednesday >2010-10-27, 14:00 UTC >irc://irc.freenode.net#sugar-meeting > > How about other possible attenders? > > -- > 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
[Sugar-devel] [PATCH v8] Downgrading activities not allowed. (SL #2164)
From: Shanjit Singh Jajmann , Anubhav Aggarwal
Activity can be downgraded on the availability of an older .xo version of an
activity. An alert pops up when trying to install an older .xo file of an
activity, which asks the user to make a selection on whether to move to an
older activity version or not.
Co-authored-by: Shanjit Singh Jajmann
Co-authored-by: Anubhav Aggarwal
---
v1 -> v2. Inline function used, signal emission condition revised and global
variables removed. Recommendations by James Cameron and Aleksey Lim added.
v2 -> v3. Used misc.resume.
v3 -> v4. Changes in the copyright of the new file.
v4 -> v5. Alert shown in the same window as the journal.
v5 -> v6. Static variable removed, name of the functions changed.
Recommendations by James Cameron and Aleksey Lim added.
v6 -> v7. Logic for the alert pop up made simpler.
Recommendations by Aleksay Lim added.
v7 -> v8. Missing file added.
---
src/jarabe/journal/journalactivity.py |5 ++-
src/jarabe/journal/journalwindow.py | 34 +++
src/jarabe/journal/misc.py| 47 ++--
src/jarabe/model/bundleregistry.py|7 +++-
4 files changed, 80 insertions(+), 13 deletions(-)
create mode 100644 src/jarabe/journal/journalwindow.py
diff --git a/src/jarabe/journal/journalactivity.py
b/src/jarabe/journal/journalactivity.py
index 44cc018..beb0962 100644
--- a/src/jarabe/journal/journalactivity.py
+++ b/src/jarabe/journal/journalactivity.py
@@ -44,6 +44,7 @@ from jarabe.journal.journalentrybundle import
JournalEntryBundle
from jarabe.journal.objectchooser import ObjectChooser
from jarabe.journal.modalalert import ModalAlert
from jarabe.journal import model
+from jarabe.journal.journalwindow import JournalWindow
J_DBUS_SERVICE = 'org.laptop.Journal'
J_DBUS_INTERFACE = 'org.laptop.Journal'
@@ -102,10 +103,10 @@ class JournalActivityDBusService(dbus.service.Object):
def ObjectChooserCancelled(self, chooser_id):
pass
-class JournalActivity(Window):
+class JournalActivity(JournalWindow):
def __init__(self):
logging.debug("STARTUP: Loading the journal")
-Window.__init__(self)
+JournalWindow.__init__(self)
self.set_title(_('Journal'))
diff --git a/src/jarabe/journal/journalwindow.py
b/src/jarabe/journal/journalwindow.py
new file mode 100644
index 000..3c718c2
--- /dev/null
+++ b/src/jarabe/journal/journalwindow.py
@@ -0,0 +1,34 @@
+#Copyright (C) 2010 Software for Education, Entertainment and Training
+#Activities
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
+
+import gtk
+from sugar.graphics.window import Window
+
+_journal_window = None
+
+
+class JournalWindow(Window):
+
+def __init__(self):
+
+global _journal_window
+Window.__init__(self)
+_journal_window = self
+
+
+def get_journal_window():
+return _journal_window
diff --git a/src/jarabe/journal/misc.py b/src/jarabe/journal/misc.py
index 32a2847..122feca 100644
--- a/src/jarabe/journal/misc.py
+++ b/src/jarabe/journal/misc.py
@@ -27,8 +27,10 @@ from sugar.activity import activityfactory
from sugar.activity.activityhandle import ActivityHandle
from sugar.graphics.icon import get_icon_file_name
from sugar.graphics.xocolor import XoColor
+from sugar.graphics.alert import ConfirmationAlert
from sugar import mime
from sugar.bundle.activitybundle import ActivityBundle
+from sugar.bundle.bundle import AlreadyInstalledException
from sugar.bundle.contentbundle import ContentBundle
from sugar import util
@@ -36,6 +38,7 @@ from jarabe.view import launcher
from jarabe.model import bundleregistry, shell
from jarabe.journal.journalentrybundle import JournalEntryBundle
from jarabe.journal import model
+from jarabe.journal import journalwindow
def _get_icon_for_mime(mime_type):
generic_types = mime.get_all_generic_types()
@@ -159,19 +162,16 @@ def resume(metadata, bundle_id=None):
bundle = ActivityBundle(file_path)
if not registry.is_installed(bundle):
logging.debug('Installing activity bundle')
-registry.install(bundle)
+try:
+registry.install(bundle)
+except AlreadyInstalledException:
+_downgrade_option_alert(bundle)
+return
else:
Re: [Sugar-devel] Development Meetings
On Mon, Oct 25, 2010 at 01:29:07PM +, Walter Bender wrote: > On Mon, Oct 25, 2010 at 12:59 PM, Aleksey Lim wrote: > > On Mon, Oct 25, 2010 at 08:13:24AM -0400, Walter Bender wrote: > >> On Mon, Oct 25, 2010 at 8:09 AM, Aleksey Lim > >> wrote: > >> > Hi all, > >> > > >> > Since we don't have team lead (for a long time) there a bunch of > >> > questions that need to be fixed. > >> > > >> > (imho, we might not even need team lead for Development Team, all > >> > questions might be solved in process while, weekly/daily on-purpose > >> > meetings. Lead is required eg for community relationships or an > >> > architect) > >> > > >> > So, I'm proposing to have weekly on-purpose meetings. All people who have > >> > questions for Development Team, that might be useful to discuss having a > >> > concilium of interested in developers, are welcome. All people who take > >> > part in core coding are welcome as well. > >> > > >> > I've added topics that are important for me[1], add that is important > >> > for you. > >> > > >> > http://wiki.sugarlabs.org/go/Development_Team/Meetings#Upcoming_Agenda > >> > > >> > -- > >> > Aleksey > >> > ___ > >> > Sugar-devel mailing list > >> > Sugar-devel@lists.sugarlabs.org > >> > http://lists.sugarlabs.org/listinfo/sugar-devel > >> > > >> > >> +1 > >> > >> When is the next meeting? Wednesday? > > > > [1] says on Mondays, but I guess we can make an exclusion. > > > > Wednesday sounds reasonable for me, I guess it is enough to let people > > a time to be prepared to announced (current and possibly new) topics. > > I guess I didn't see a date for the upcoming meeting on [1]... I was > just guessing Wednesday. What time? #sugar-meeting, I presume. For me, default time is ok Wednesday 2010-10-27, 14:00 UTC irc://irc.freenode.net#sugar-meeting How about other possible attenders? -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Development Meetings
On Mon, Oct 25, 2010 at 12:59 PM, Aleksey Lim wrote: > On Mon, Oct 25, 2010 at 08:13:24AM -0400, Walter Bender wrote: >> On Mon, Oct 25, 2010 at 8:09 AM, Aleksey Lim wrote: >> > Hi all, >> > >> > Since we don't have team lead (for a long time) there a bunch of >> > questions that need to be fixed. >> > >> > (imho, we might not even need team lead for Development Team, all >> > questions might be solved in process while, weekly/daily on-purpose >> > meetings. Lead is required eg for community relationships or an >> > architect) >> > >> > So, I'm proposing to have weekly on-purpose meetings. All people who have >> > questions for Development Team, that might be useful to discuss having a >> > concilium of interested in developers, are welcome. All people who take >> > part in core coding are welcome as well. >> > >> > I've added topics that are important for me[1], add that is important >> > for you. >> > >> > http://wiki.sugarlabs.org/go/Development_Team/Meetings#Upcoming_Agenda >> > >> > -- >> > Aleksey >> > ___ >> > Sugar-devel mailing list >> > Sugar-devel@lists.sugarlabs.org >> > http://lists.sugarlabs.org/listinfo/sugar-devel >> > >> >> +1 >> >> When is the next meeting? Wednesday? > > [1] says on Mondays, but I guess we can make an exclusion. > > Wednesday sounds reasonable for me, I guess it is enough to let people > a time to be prepared to announced (current and possibly new) topics. I guess I didn't see a date for the upcoming meeting on [1]... I was just guessing Wednesday. What time? #sugar-meeting, I presume. -walter > > -- > Aleksey > -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release Edit-6
Activity Homepage: http://activities.sugarlabs.org/addon/4349 Sugar Platform: 0.82 - 0.90 Download Now: http://activities.sugarlabs.org/downloads/file/27083/edit-6.xo Release notes: Wow, a new release already! This release adds automatic syntax highlighting with GtkSourceView. Files with mimetypes of "text/plain" (initially made with Edit) should look identical in Version 6 and Version 5: if they don't, email me. Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release Watch Me-3
Activity Homepage: http://activities.sugarlabs.org/addon/4205 Sugar Platform: 0.82 - 0.88 Download Now: http://activities.sugarlabs.org/downloads/file/26996/watch_me-3.xo Release notes: Version 3 adds error messages if the dependencies (x11vnc and gtk-vnc-python) are not properly installed. Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release Record-86
Activity Homepage: http://activities.sugarlabs.org/addon/4081 Sugar Platform: 0.84 - 0.84 Download Now: http://activities.sugarlabs.org/downloads/file/27004/record-86.xo Release notes: Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release Measure-32
Activity Homepage: http://activities.sugarlabs.org/addon/4197 Sugar Platform: 0.82 - 0.88 Download Now: http://activities.sugarlabs.org/downloads/file/27012/measure-32.xo Release notes: * added missing tooltip * updated depreciated fields in activity.info file Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Systems] [Marketing] A little change to www.sugarlabs.org
Sure--if it helps I can change that. I should be able to make that change, along with the new page, early this week, I'll keep everyone posted. Christian On Fri, Oct 22, 2010 at 7:23 AM, Simon Schampijer wrote: > On 10/15/2010 04:00 PM, Christian Marc Schmidt wrote: > >> Hi--I can add this information this weekend. >> >> Christian >> > > Christian - can you change the page to not open the links in a new window? > That would be great, it really hurts us a lot! > > Regards, > Simon > -- anyth...@christianmarcschmidt.com 917/ 575 0013 http://www.christianmarcschmidt.com http://www.linkedin.com/in/christianmarcschmidt http://twitter.com/cms_ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH v7] Downgrading activities not allowed. (SL #2164)
On Mon, Oct 25, 2010 at 02:39:31AM +0530, shan...@seeta.in wrote:
> From: Shanjit Singh Jajmann
>
> Activity can be downgraded on the availability of an older .xo version of an
> activity. An alert pops up when trying to install an older .xo file of an
> activity, which asks the user to make a selection on whether to move to an
> older activity version or not.
>
> Co-authored-by: Shanjit Singh Jajmann
> Anubhav Aggarwal
> ---
>
> v1 -> v2. Inline function used, signal emission condition revised and global
> variables removed. Recommendations by James Cameron and Aleksey Lim added.
>
> v2 -> v3. Used misc.resume.
>
> v3 -> v4. Changes in the copyright of the new file.
>
> v4 -> v5. Alert shown in the same window as the journal.
>
> v5 -> v6. Static variable removed, name of the functions changed.
> Recommendations by James Cameron and Aleksey Lim added.
>
> v6 -> v7. Logic for the alert pop up made simpler.
> Recommendations by Aleksay Lim added.
> ---
> src/jarabe/journal/journalactivity.py |5 ++-
> src/jarabe/journal/misc.py| 47 ++--
> src/jarabe/model/bundleregistry.py|7 +++-
looks like you forgot to add journalwindow.py
(patch posted by anubhav looks different to this one)
> 3 files changed, 46 insertions(+), 13 deletions(-)
>
> diff --git a/src/jarabe/journal/journalactivity.py
> b/src/jarabe/journal/journalactivity.py
> index 44cc018..beb0962 100644
> --- a/src/jarabe/journal/journalactivity.py
> +++ b/src/jarabe/journal/journalactivity.py
> @@ -44,6 +44,7 @@ from jarabe.journal.journalentrybundle import
> JournalEntryBundle
> from jarabe.journal.objectchooser import ObjectChooser
> from jarabe.journal.modalalert import ModalAlert
> from jarabe.journal import model
> +from jarabe.journal.journalwindow import JournalWindow
>
> J_DBUS_SERVICE = 'org.laptop.Journal'
> J_DBUS_INTERFACE = 'org.laptop.Journal'
> @@ -102,10 +103,10 @@ class JournalActivityDBusService(dbus.service.Object):
> def ObjectChooserCancelled(self, chooser_id):
> pass
>
> -class JournalActivity(Window):
> +class JournalActivity(JournalWindow):
> def __init__(self):
> logging.debug("STARTUP: Loading the journal")
> -Window.__init__(self)
> +JournalWindow.__init__(self)
>
> self.set_title(_('Journal'))
>
> diff --git a/src/jarabe/journal/misc.py b/src/jarabe/journal/misc.py
> index 32a2847..1d73fa8 100644
> --- a/src/jarabe/journal/misc.py
> +++ b/src/jarabe/journal/misc.py
> @@ -27,8 +27,10 @@ from sugar.activity import activityfactory
> from sugar.activity.activityhandle import ActivityHandle
> from sugar.graphics.icon import get_icon_file_name
> from sugar.graphics.xocolor import XoColor
> +from sugar.graphics.alert import ConfirmationAlert
> from sugar import mime
> from sugar.bundle.activitybundle import ActivityBundle
> +from sugar.bundle.bundle import AlreadyInstalledException
> from sugar.bundle.contentbundle import ContentBundle
> from sugar import util
>
> @@ -36,6 +38,7 @@ from jarabe.view import launcher
> from jarabe.model import bundleregistry, shell
> from jarabe.journal.journalentrybundle import JournalEntryBundle
> from jarabe.journal import model
> +from jarabe.journal import journalwindow
>
> def _get_icon_for_mime(mime_type):
> generic_types = mime.get_all_generic_types()
> @@ -159,19 +162,16 @@ def resume(metadata, bundle_id=None):
> bundle = ActivityBundle(file_path)
> if not registry.is_installed(bundle):
> logging.debug('Installing activity bundle')
> -registry.install(bundle)
> +try:
> +registry.install(bundle)
> +except AlreadyInstalledException:
> +_downgrade_option_alert(bundle)
> +return
> else:
> logging.debug('Upgrading activity bundle')
> registry.upgrade(bundle)
>
> -logging.debug('activityfactory.creating bundle with id %r',
> -bundle.get_bundle_id())
> -installed_bundle = registry.get_bundle(bundle.get_bundle_id())
> -if installed_bundle:
> -launch(installed_bundle)
> -else:
> -logging.error('Bundle %r is not installed.',
> - bundle.get_bundle_id())
> +_install_bundle(bundle)
>
> elif is_content_bundle(metadata) and bundle_id is None:
>
> @@ -215,6 +215,17 @@ def resume(metadata, bundle_id=None):
> launch(bundle, activity_id=activity_id, object_id=object_id,
> color=get_icon_color(metadata))
>
> +def _install_bundle(bundle):
> +registry = bundleregistry.get_registry()
> +logging.debug('activityfactory.creating bundle with id %r',
> + bundle.get_bundle_id())
> +installed_bundle = registry.get_bundle(bundle.get_bundle_id())
> +if installed_bundle:
> + launch(installed_bundle)
> +else:
>
Re: [Sugar-devel] Development Meetings
On Mon, Oct 25, 2010 at 08:13:24AM -0400, Walter Bender wrote: > On Mon, Oct 25, 2010 at 8:09 AM, Aleksey Lim wrote: > > Hi all, > > > > Since we don't have team lead (for a long time) there a bunch of > > questions that need to be fixed. > > > > (imho, we might not even need team lead for Development Team, all > > questions might be solved in process while, weekly/daily on-purpose > > meetings. Lead is required eg for community relationships or an > > architect) > > > > So, I'm proposing to have weekly on-purpose meetings. All people who have > > questions for Development Team, that might be useful to discuss having a > > concilium of interested in developers, are welcome. All people who take > > part in core coding are welcome as well. > > > > I've added topics that are important for me[1], add that is important > > for you. > > > > http://wiki.sugarlabs.org/go/Development_Team/Meetings#Upcoming_Agenda > > > > -- > > Aleksey > > ___ > > Sugar-devel mailing list > > Sugar-devel@lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > > +1 > > When is the next meeting? Wednesday? [1] says on Mondays, but I guess we can make an exclusion. Wednesday sounds reasonable for me, I guess it is enough to let people a time to be prepared to announced (current and possibly new) topics. -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Dextrose] Pending patchs for Paint
On Sat, Oct 23, 2010 at 4:21 AM, Sascha Silbe wrote: >> If something's controversial it may not be on 'master' but there's no >> reason to have it in the sugarlabs git repos where everyone looks for >> src. > > I suppose this should have read "*not* to have it"? The dastardly double-negative. You're right. 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] Development Meetings
On Mon, Oct 25, 2010 at 12:09:22PM +, Aleksey Lim wrote: > Hi all, > > Since we don't have team lead (for a long time) there a bunch of > questions that need to be fixed. > > (imho, we might not even need team lead for Development Team, all > questions might be solved in process while, weekly/daily on-purpose > meetings. Lead is required eg for community relationships or an > architect) > > So, I'm proposing to have weekly > on-purpose meetings. if there is an upcomming agenda[1] > All people who have > questions for Development Team, that might be useful to discuss having a > concilium of interested in developers, are welcome. All people who take > part in core coding are welcome as well. > > I've added topics that are important for me[1], add that is important > for you. [1] http://wiki.sugarlabs.org/go/Development_Team/Meetings#Upcoming_Agenda -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Development Meetings
On Mon, Oct 25, 2010 at 8:09 AM, Aleksey Lim wrote: > Hi all, > > Since we don't have team lead (for a long time) there a bunch of > questions that need to be fixed. > > (imho, we might not even need team lead for Development Team, all > questions might be solved in process while, weekly/daily on-purpose > meetings. Lead is required eg for community relationships or an > architect) > > So, I'm proposing to have weekly on-purpose meetings. All people who have > questions for Development Team, that might be useful to discuss having a > concilium of interested in developers, are welcome. All people who take > part in core coding are welcome as well. > > I've added topics that are important for me[1], add that is important > for you. > > http://wiki.sugarlabs.org/go/Development_Team/Meetings#Upcoming_Agenda > > -- > Aleksey > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > +1 When is the next meeting? Wednesday? -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Development Meetings
Hi all, Since we don't have team lead (for a long time) there a bunch of questions that need to be fixed. (imho, we might not even need team lead for Development Team, all questions might be solved in process while, weekly/daily on-purpose meetings. Lead is required eg for community relationships or an architect) So, I'm proposing to have weekly on-purpose meetings. All people who have questions for Development Team, that might be useful to discuss having a concilium of interested in developers, are welcome. All people who take part in core coding are welcome as well. I've added topics that are important for me[1], add that is important for you. http://wiki.sugarlabs.org/go/Development_Team/Meetings#Upcoming_Agenda -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Dextrose] Pending patchs for Paint
On Monday, October 25, 2010, James Cameron wrote: > (composite reply to several postings in thread) > > On Fri, Oct 22, 2010 at 03:16:49PM +0100, Gary Martin wrote: >> On 20 Oct 2010, at 21:56, James Cameron wrote: >> > On Wed, Oct 20, 2010 at 04:56:41PM +0100, Gary Martin wrote: >> > > http://git.sugarlabs.org/projects/paint/repos/mainline >> > > >> > > I noticed that the activity.info file is still for version 27. As >> > > Paint-28 has been released I'd expect to mainline to at least be >> > > up to date with those commits. Maybe the rest of the source is >> > > current, and it's just the activity.info file change that was not >> > > pushed? >> > >> > While it would be nice if every release of every activity has a >> > matching tag and sources in the respective repository, we've had >> > situations where that has not been desirable, such as when a version >> > of Record was released for a deployment via activities.sugarlabs.org >> > but the changes were not accepted into mainline because consensus >> > had not been reached. >> >> In such cases git.sugarlabs.org provides very easy cloning of any rep >> where deployments can have full control and create, say, a custom >> Record-Peru. > > It might not have been easy enough, because it wasn't chosen as the > solution to the issue at the time. > >> > A release of an activity is not done using the master repository, it >> > is done using a local clone of the repository. Therefore during >> > testing and diagnosis I've always presumed that the source code >> > shipped in the .xo file might be different to the tagged source in >> > the master repository. >> >> Hmm, I'd have to disagree. This seems like a terrible workflow for a >> community. [...] > > How would you make activities be released from a master repository? You > would automate the release mechanism somehow? You would add one more > person to the release sequence? Or you would refuse to list activities > on activities.sugarlabs.org unless they match a master repository? No, I was just trying to suggest that it is a very good habit to keep master in sync with the activity bundle releases. FWIW, it's actually much easier for a maintainer (my opinion) to review and merge work when it's been made in a clone in gitiorus, think it's also easier for who ever is making the patches as well given all the git fu has seems to be needed to email patches... but I'm digressing OT into the email patch storm we seem to have sailed into. Regards, --Gary > In my opinion, the problem does not happen frequently enough to warrant > this attention, but for diagnosis and testing I must continue to check > that the source matches the master repository. To not do so in the > absence of strict controls would be negligent. > > On Fri, Oct 22, 2010 at 06:45:06PM +0200, Sascha Silbe wrote: >> Excerpts from James Cameron's message of Wed Oct 20 22:56:04 +0200 2010: >> >> > While it would be nice if every release of every activity has a >> > matching tag and sources in the respective repository, [...] >> >> I certainly hope that each bundle released by Sugar Labs or associated >> organisations (OLPC, etc). has a corresponding commit and tag in a >> discoverable git repository. > > As I said, this wasn't the case. The frequency of such exceptions is > low though. > >> It doesn't need to be the on the master branch or even inside the >> mainline repository. What matters is there is >> a) a corresponding commit in a public git repository >> b) the commit belonging to a particular bundle is discoverable within >> a reasonable amount of time. > > It certainly wasn't. > > On Sat, Oct 23, 2010 at 10:21:11AM +0200, Sascha Silbe wrote: >> As a developer, it's important to me that the corresponding source >> code for each released object (e.g. activity bundles) is easily >> accessible. > > On the other hand, the .xo file does contain the source. > > -- > 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] Vizualisation of the Write activity develpment (gource)
Hi all, Bastien writes: > Thanks! I'm nearly done with producing the video from Michael's repo. > I will also produce one from Marco's, it will be more useful. I just published a blog entry with the gource video about the Write activité and the one about the Sugar core modules (from Marco's repo): http://olpc-france.org/blog/2010/10/visualiser-le-developpement-de-sugar/ If that's useful I'll try to translate this entry in english, but I'm still unsure about our policy for having a bilingual blog. Will keep you posted. Enjoy, -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [RELEASE] Browse-120
On 25 October 2010 09:25, Simon Schampijer wrote: > On 10/25/2010 09:31 AM, Jonas Smedegaard wrote: >> >> On Sun, Oct 24, 2010 at 06:51:15PM -0400, Lucian Branescu Mihaila wrote: >>> >>> >>> http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-120.tar.bz2 >>> >> >> Please push a tag for that release. > > Hmm, somehow the history seems strange too. Lucian, can you verify that? > Please, don't forget to do the release on the 0.90 branch. > > Btw, you can use the release script at [1]. Helps you not to forget the > tagging etc, sends the email... > > Regards, > Simon > > [1] > http://git.sugarlabs.org/projects/sugar-tools/repos/mainline/blobs/master/release I used the release script on the 0.90 branch. The history does look weird. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [RELEASE] Browse-120
On 10/25/2010 09:31 AM, Jonas Smedegaard wrote: On Sun, Oct 24, 2010 at 06:51:15PM -0400, Lucian Branescu Mihaila wrote: http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-120.tar.bz2 Please push a tag for that release. Hmm, somehow the history seems strange too. Lucian, can you verify that? Please, don't forget to do the release on the 0.90 branch. Btw, you can use the release script at [1]. Helps you not to forget the tagging etc, sends the email... Regards, Simon [1] http://git.sugarlabs.org/projects/sugar-tools/repos/mainline/blobs/master/release ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [RELEASE] sugar-base-0.90.1
On 10/12/2010 03:42 PM, Jonas Smedegaard wrote: On Wed, Sep 29, 2010 at 05:54:25PM +0200, Simon Schampijer wrote: Sorry the header should have been sugar-base of course. On 09/29/2010 05:53 PM, Simon Schampijer wrote: == Source == http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.90.1.tar.bz2 Please push the git tag. - Jonas Done. Sorry had been created locally only. Thanks for pointing out. Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ANNOUNCE] Sucrose 0.90.2 Tarballs Due
Dear Sucrose Maintainers, we will have our second bug fix release in the 0.90 development cycle October the 27th [1]. For more info on the current schedule see as well the thread at [2]. Please provide the Sucrose 0.90.2 tarballs by Monday night (25th of October) and announce them as explained at [3]. Thanks, Simon [1] http://wiki.sugarlabs.org/go/0.90/Roadmap#Schedule [2] http://lists.sugarlabs.org/archive/sugar-devel/2010-October/027547.html [3] http://sugarlabs.org/go/Development_Team/Release#Module_release ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ANNOUNCE] Sucrose 0.90.1 Bugfix Release
Dear Sugar community, This is our first bugfix release in the 0.90 development cycle. Full release notes can be found at [1]. Thanks everyone for your great contributions! On behalf of the Sugar community, Your Release Team [1] http://wiki.sugarlabs.org/go/0.90/0.90.1_Notes ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [RELEASE] Browse-120
On 10/25/2010 09:31 AM, Jonas Smedegaard wrote: On Sun, Oct 24, 2010 at 06:51:15PM -0400, Lucian Branescu Mihaila wrote: http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-120.tar.bz2 Please push a tag for that release. Also, it seems work has been done at the 0.84 branch of Browse - please remember to release that as tarball and tag it, when ready for consumption. FWIW, for new 0.84 activity releases we want to land the new numbering scheme first to avoid other messy solutions here. Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [RELEASE] Browse-120
On Sun, Oct 24, 2010 at 06:51:15PM -0400, Lucian Branescu Mihaila wrote: http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-120.tar.bz2 Please push a tag for that release. Also, it seems work has been done at the 0.84 branch of Browse - please remember to release that as tarball and tag it, when ready for consumption. Thanks for allthe great work! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
