#2716 BLOC Trial-3: .xo install from Browse
Zarro Boogs per Child
bugtracker at laptop.org
Wed Sep 5 10:00:15 EDT 2007
#2716: .xo install from Browse
----------------------+-----------------------------------------------------
Reporter: dcbw | Owner: danw
Type: defect | Status: reopened
Priority: blocker | Milestone: Trial-3
Component: sugar | Version:
Resolution: | Keywords: review+
Verified: 0 |
----------------------+-----------------------------------------------------
Comment (by Eben):
Replying to [comment:8 tomeu]:
> Replying to [comment:7 HoboPrimate]:
> > In an updated sugar-jhbuild, this is what happens:
> >
> > 1. Click .xo link in Browse. A Data object appears in the clipboard
frame and in the journal.
>
> Bug in the clipboard: #3175. Thanks!
>
> > 2. Once the download is complete, nothing happens (The activity isn't
in ~/Activities ).
>
> It worked for me, so I suspect your bundle is incorrect or you already
had an activity with the same service name installed. There's no
exceptions in the logs?
For clarification, a new version of an installed bundle should simply
overwrite the one already installed on disk. This is a problem with
sugar-install-bundle in general: overwriting existing bundles is a chore.
> > 3. Resuming the .xo file from the journal does nothing.
>
> This is normal if the bundle wasn't installed before. Any other logs?
Normal or not, this is not correct. If an activity lives inside the
Journal, than it ''is'' installed (or should be) by definition.
"Resuming" an activity (.xo) object should actually just create a new
instance of that activity, as if it were launched from the frame. We can
change the text on the rollover for the resume button to "Start" in this
case, to clarify that behavior.
> > 4. Choosing "Add to Journal" from the clipboard icon menu, installs
the activity, making it appear in the bottom frame.
Rock on. This is good news in general. Of course, once we have in-
progress entries within the Journal, this object won't appear in the
clipboard at all (from Browse), but there will be other cases where this
will be important for sure.
--
Ticket URL: <http://dev.laptop.org/ticket/2716#comment:9>
One Laptop Per Child <http://laptop.org/>
More information about the Bugs
mailing list