[sugar] A Launcher Activity
Mon Aug 13 21:25:19 EDT 2007
In the "good reason to not do it category": this will not work on the
final system. Anybody other than Sugar itself trying to start an
activity will simply be ignored. You will be unable to see the other
activities directly anyway.
On Aug 13, 2007, at 9:12 PM, Carlos Neves wrote:
> The Activity Center is a standalone activity as things are now, and
> continue to be unless there is some good reason to change this.
> It's the
> only MaMaMedia activity launched from the Home view.
> The relation to other activities, which are already not launched from
> the Home view, is implicit. There is a hard coded list of
> activities the
> Center known about, and checks for them at startup. If the activity is
> there, it can be launched, and if not a 'Coming soon...' notice
> We envision that eventually an auto download will be implemented for
> activities not already installed, but that's something for future
> At it's present state, the Center has another task on it's hands. It
> holds code and data (images) that are common to MaMaMedia
> activities, so
> they are not duplicated in the filesystem.
> The other activities are not invisible to Home though, they are simply
> not launched from there. This way we reuse the code already done for
> managing the running apps, and Sugar Activity factories are free to do
> their magic and optimizations. This makes each Activity appear
> transparently in the Home donut, if you share the activity it can be
> remotely launched from the Mesh view and you can (not any more, but
> soon) restart an activity from the Journal, without any extra
> effort on
> the Center part, as this is all handled by Sugar. That's the extra
> etoys needs to do for supporting the Journal that we get for free.
> Samuel Klein wrote:
>> Aggregating modules and activities outside of the home view is
>> generally important; we should do this cleanly in terms of
>> journalling, allowing anyone to define a cluster of related
>> Have you thought about packageing the Activity Center as its own
>> standalone activity that loads activity-sets? Then the activity
>> center could be a more core app that takes in clusters of activities
>> (which would themselves implicitly be invisible from Home;
>> each cluster could get one group activity icon in the home view).
>> approaching this problem from the other side, I wonder how we can be
>> better about journalling what projects within etoys are being
>> and shared.
>> On 8/13/07, Carlos Neves <cn at sueste.net> wrote:
>>> One of the things I developed for World Wide Workshop was a launcher
>>> activity, called the MMM Activity Center (MMM stands for MaMaMedia),
>>> which aggregates all relevant activities as a bundle to be
>>> launched only
>>> from there, much like etoys does.
>>> Unlike etoys, each activity there is a full blown standalone Sugar
>>> activity, that could very well be launched from the Home view
>>> (and in
>>> fact is). The simplicity of this approach in terms of mesh
>>> sharing and
>>> journal support tilted us into the current solution.
>>> I'm using bundlebuilder.py to find out if the activities are
>>> which has worked well from the start, except for the fact this
>>> particular file has been a moving target between versions... The
>>> code checks for it in 3 different locations.
>>> But my actual problem is different. The approach I'm using works on
>>> build 432, by using
>>> handler = activityfactory.create
>>> self._c1 = handler.connect("success",
>>> self._launch_success_cb, handler)
>>> self._c2 = handler.connect("error",
>>> handler, idx)
>>> self.bubble_label.show(_("Loading %s...") % BUBBLE_SET
>>> c = gtk.gdk.Cursor(gtk.gdk.WATCH)
>>> The problem with current builds, specifically 542, is twofold:
>>> - the 'success' and 'error' signals no longer exist and
>>> - Home view is brought to front
>>> Looking at the code for the Shell, I see that the notifications
>>> are now
>>> only delivered to _shell and it pops itself to front every time an
>>> activity is launched, period.
>>> What I would like to see, although I fully agree with the current
>>> approach for things launched from the Journal or the Mesh, is a
>>> way to
>>> avoid showing the Home view and getting the launched and error
>>> notifications under controlled circumstances.
>>> for example,
>>> could take an extra 'listener' argument that was then passed to the
>>> ActivityCreationHandler._launch_activity would call NotifyLaunch not
>>> only on the shell proxy but also on that listener (if not None, of
>>> course) and the same goes for _create_error_handler/
>>> I could use a NotifyLaunchSuccess on top of _create_reply_handler
>>> if that's not asking too much :)
>>> This would make the notifications work optionally without the
>>> although implementing signals (again) would work great too. I'm
>>> towards this approach because this way the
>>> ActivityCreationHandler knows
>>> it should signal the shell in order to not pop up front, but
>>> adding an
>>> optional bool on the NotifyLaunch method or something.
>>> Am I being completely unreasonable here? I really think that
>>> being able
>>> to aggregate activities outside the Home view is important, as
>>> there is
>>> only so much space there, and this Activity Center is actually
>>> for us.
>>> Best regards,
>>> Carlos Neves
>>> cn at sueste.net
>>> Sugar mailing list
>>> Sugar at lists.laptop.org
> Sugar mailing list
> Sugar at lists.laptop.org
More information about the Sugar-devel