<div dir="ltr">pygame aside, does it use sugar-toolkit (import sugar) or sugar-toolkit-gtk3 (import sugar3)?<br><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On 14 September 2013 23:38, laurent bernabe <span dir="ltr"><<a href="mailto:laurent.bernabe@gmail.com" target="_blank">laurent.bernabe@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">no it is a pygame activity built upon sugar olpc games</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra">
<br><br><div class="gmail_quote">2013/9/14 Daniel Narvaez <span dir="ltr"><<a href="mailto:dwnarvaez@gmail.com" target="_blank">dwnarvaez@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Is it a gtk2 activity? If not, is it using "from sugar3.activity import bundlebuilder" in the setup.py?<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 14 September 2013 22:06, Daniel Narvaez <span dir="ltr"><<a href="mailto:dwnarvaez@gmail.com" target="_blank">dwnarvaez@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">From terminal is fine, you are inside the chroot. Looks like a bug somewhere, investigating...<br></div>
<div class="gmail_extra"><div><div><br><br><div class="gmail_quote">On 14 September 2013 22:03, laurent bernabe <span dir="ltr"><<a href="mailto:laurent.bernabe@gmail.com" target="_blank">laurent.bernabe@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I don't think, as I started the sugar emulator with<div>$> ./osbuild run</div><div><br></div><div>
rather than running $> ./osbuild shell</div><div><br></div><div>And from the terminal activity, I enter the installation command for my own activity.</div>
</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/9/14 Daniel Narvaez <span dir="ltr"><<a href="mailto:dwnarvaez@gmail.com" target="_blank">dwnarvaez@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Did you run setup.py dev inside an osbuild shell? (Btw I don't develop activities myself so your feedback is very useful)<br><br>On Saturday, 14 September 2013, laurent bernabe wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hello,<div><br></div><div>I've just installed my own activity in sugar-build, by the command</div><div>$>python setup.py dev</div><div><br></div><div>But, though I've restarted Sugar-build, I can't see my own application, even looking at the table view of the activities. And I did not see any trace of my own activity in the logs.</div>
<div><br></div><div>Meanwhile, I launched "$> python setup.py dev" again, and I got the message "the activity is already installed in developpement mode".</div><div><br></div><div>Also, I looked into the sugar-build folder, but did not see the subfolder activities, letting me think that the application is not properly installed.</div>
<div><br></div><div>What did I misunderstood ?</div><div><br></div><div>Regards</div></div><span><font color="#888888">
</font></span></blockquote><span><font color="#888888"><br><br>-- <br>Daniel Narvaez<br><br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear="all"><span><font color="#888888"><br></font></span></div></div><span><font color="#888888"><span><font color="#888888">-- <br>Daniel Narvaez<br>
</font></span></font></span></div><span><font color="#888888">
</font></span></blockquote></div><span><font color="#888888"><br><br clear="all"><br>-- <br>Daniel Narvaez<br>
</font></span></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Daniel Narvaez<br>
</div></div></div></div></div>