Yes, that is exactly the use-case: Someone copies a bundle to the journal and (if everything corresponds) voilá!
Another use-case could be while received from another sugar user (through send-to), and so on. What I explained in the previous email was just the general case, or what I could recall hehe... On Tue, Feb 14, 2012 at 7:35 AM, Ajay Garg <[email protected]> wrote: > Thanks Martin for the reply. > > So, the use-case of installation happening when the ".xo" is simply > copied (say, from a pen-drive to the journal) is ok? > I am not being judgemental, just wanting to know that if this is an > already-discussed, accepted use-case. > > Regards, > Ajay > > On Tue, Feb 14, 2012 at 3:55 PM, Martin Abente > <[email protected]> wrote: > > The journal is constantly watching for the new entries that are created > or > > updated. For every newly created or updated journal entry, it checks > whether > > or not this entry is a bundle (ie, an activity bundle). > > > > IF this journal entry is an bundle, it checks if the activity is already > > installed or not, if not installed, it just installs it. > > > > That is basically how the magic activities installation works, IIRC. > > > > On Tue, Feb 14, 2012 at 7:12 AM, Ajay Garg <[email protected]> > wrote: > >> > >> Hi all. > >> > >> I will be grateful, if someone could please let me know the purpose of > >> the following method : (A somewhat step-by-step use-case explanation > >> will be really useful :-) ) > >> > >> """ > >> def _check_for_bundle(self, object_id) > >> """ > >> > >> in "/usr/lib/python2.7/site-packages/jarabe/journal/journalactivity.py". > >> > >> > >> > >> Regards, > >> Ajay > >> _______________________________________________ > >> Sugar-devel mailing list > >> [email protected] > >> http://lists.sugarlabs.org/listinfo/sugar-devel > > > > >
_______________________________________________ Sugar-devel mailing list [email protected] http://lists.sugarlabs.org/listinfo/sugar-devel
