[Sugar-devel] [Sugar emulator][Ubuntu 11.04] I can't install an activity (with the setup.py)

[laurent bernabe]

Thank you,

You're right, I just want to develop activities, not hacking Sugar (at
least, not right now, as I am just starting).

My current Linux system is Xubuntu :

   - First, I had tried the sugar-emulator provided by Canonical => I did
   not find which package to install in order to have the sugar python modules
   - Many Pippy examples does not work with the Canonical package, whereas
   I managed with Sweet

But I'll uninstall sweet right now, and try to find the missing package in
order to be able to use the sugar-emulator on the one hand, and use most
Pippy examples on the other hand.

And I will read again the chapter explaining the environement setup more
accurately.

2011/12/5 James Simmons <nicestep at gmail.com>

> Laurent,
>
> This may be an issue with sweets.  If you are using Fedora then all you
> really need to do is to install the Sugar RPM's that come with the
> distribution.  Other distributions should have something similar.  The
> module sugar.activity is a set of Python classes.  It should be available
> to anyone developing Python code, whether Sugar is running or not.  It is a
> fundamental library.  You can't make a Sugar Activity without it.
>
> I don't know what "Sweets" is doing, but if I was in your position I'd
> uninstall it and install the Sugar that comes with the distribution.
>  Fedora does a very good job packaging Sugar.  Their version of Sugar is
> actually newer than most kids use in the field.  If your goal is to develop
> Activities there is no reason to use anything else.  If you want to hack on
> the Sugar environment itself you would need something newer, but I'd do
> Activities first.  New or improved Activities will have a more immediate
> benefit to more students than working on Sugar itself, and you'll
> understand how to hack Sugar better if you've developed Activities first.
>
> There is a chapter on setting up a development environment in the book.
>  If you skipped over it give it another look.
>
> James Simmons
>
>
> On Mon, Dec 5, 2011 at 2:00 PM, laurent bernabe <laurent.bernabe at gmail.com
> > wrote:
>
>> Unfortunately, I can't launch setup.py from the host system terminal
>> => no module called sugar.activity
>>
>> And that error disappear if I launch setup.py from the sugar emulator
>>
>>
>> 2011/12/5 laurent bernabe <laurent.bernabe at gmail.com>
>>
>>> Ok, thank you for your answer, I've well understood.
>>> I'm going to apply your advice.
>>>
>>> Regards
>>>
>>>
>>> 2011/12/5 James Simmons <nicestep at gmail.com>
>>>
>>>> Laurent,
>>>>
>>>> I don't have experience with Sweets, but normally you would install the
>>>> version of Sugar that comes with your distribution.  When you launch this
>>>> Sugar comes up in a window.  So you have your GNOME desktop where you do
>>>> your development work, plus you have this window that contains a Sugar
>>>> environment that you use for testing.
>>>>
>>>> You run setup.py dev from a normal terminal window, not the one that
>>>> Sugar provides.  This creates a symbolic link between your source directory
>>>> and where Sugar wants your program to be.  After that any changes you make
>>>> in your source directory will be reflected in what runs under Sugar.
>>>>  You'll probably need to stop and restart your Activity to see your changes
>>>> take effect.
>>>>
>>>> James Simmons
>>>>
>>>>
>>>> On Mon, Dec 5, 2011 at 11:28 AM, laurent bernabe <
>>>> laurent.bernabe at gmail.com> wrote:
>>>>
>>>>> Hello everyone,
>>>>>
>>>>> I am following the ActivitiesGuideSugar pdf from august 2010.
>>>>>
>>>>>
>>>>>    - I've fetched tutorial source code for etext activity (chapter 5
>>>>>    : inheriting from Activity.activity)
>>>>>    - I've modified, carefully i think, the svg picture with Inkscape
>>>>>    and edited the xml structure
>>>>>    - I installed the Sugar Sweets distribution
>>>>>
>>>>> But when I try to setup the activity from the emulator terminal, I get
>>>>> an error saying that there is no module called sugar.activity
>>>>> (the line in fault : "from sugar.activity import bundlebuilder".
>>>>>
>>>>> Have I forgotten an important step in my sugar environment ?
>>>>>
>>>>> Regards
>>>>>
>>>>> _______________________________________________
>>>>> Sugar-devel mailing list
>>>>> Sugar-devel at lists.sugarlabs.org
>>>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20111205/d9b0fb70/attachment.html>