[prev in list] [next in list] [prev in thread] [next in thread] 

List:       olpc-sugar
Subject:    Re: [Sugar-devel] [Sur] Introducing SimpleActivity / Introduciendo SimpleActivity
From:       Agustin Zubiaga Sanchez <aguz () sugarlabs ! org>
Date:       2013-11-25 20:55:32
Message-ID: CAJaa_4Vc-EaTpUfxL11Wxc9Husd3cCPLb3=1TheTHUKEgtzAkQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi, now the StopButton is added automatically you don't have to call
self.add_stopbutton anymore :)

Regards,
aguz


2013/11/25 Manuel Quiñones <manuq@laptop.org>

> 2013/11/24 Agustin Zubiaga Sanchez <aguz@sugarlabs.org>:
> > Manu,
> > I just added the __init__.py file.
> >
> > About the StopButton, I added the function add_stopbutton in order to be
> > called when the activity developer finish its toolbar, because
> > SimpleActivity can't know where it's ready, I think the only way to do
> this
> > is when the user adds any item to the toolbar, move (actually, remove and
> > insert again) the stopbutton with its separator to the end of the
> toolbar,
> > but we would doing that every time an item is added and I think it
> doesn't
> > make sense.
> > If there is a way to fix an item position, please let me know.
>
> I guess you can consider this in the implementation of the add_to*
> methods of SimpleActivity.
>
> What I would do:
>
> - in the constructor of simple activity, add the main toolbar and the
> items that are always required: activity button, separator, stop
> button.
>
> - in the add_to* methods, consider the separator and stop button when
> inserting the new elements.  Insert them before.
>
> > About new signals style:
> > They look nicer, when I want to define a signal without a function, I
> can do
> > my_signal = GObject.Signal('my_signal', arg_types=(int)) as you said,
> then
> > where I should put that?
> >
> > self.mysignal  = GObject.Signal(.... ?
>
> Yes, making the signal an attribute of the class sounds right.
>
> --
> .. manuq ..
> _______________________________________________
> Lista olpc-Sur
> olpc-Sur@lists.laptop.org
> http://lists.laptop.org/listinfo/olpc-sur
>

[Attachment #5 (text/html)]

<div dir="ltr"><div>Hi, now the StopButton is added automatically you don&#39;t have \
to call self.add_stopbutton anymore :)<br><br></div>Regards,<br>aguz<br></div><div \
class="gmail_extra"><br><br><div class="gmail_quote">2013/11/25 Manuel Quiñones <span \
dir="ltr">&lt;<a href="mailto:manuq@laptop.org" \
target="_blank">manuq@laptop.org</a>&gt;</span><br> <blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">2013/11/24 \
Agustin Zubiaga Sanchez &lt;<a \
href="mailto:aguz@sugarlabs.org">aguz@sugarlabs.org</a>&gt;:<br> <div class="im">&gt; \
Manu,<br> &gt; I just added the __init__.py file.<br>
&gt;<br>
&gt; About the StopButton, I added the function add_stopbutton in order to be<br>
&gt; called when the activity developer finish its toolbar, because<br>
&gt; SimpleActivity can&#39;t know where it&#39;s ready, I think the only way to do \
this<br> &gt; is when the user adds any item to the toolbar, move (actually, remove \
and<br> &gt; insert again) the stopbutton with its separator to the end of the \
toolbar,<br> &gt; but we would doing that every time an item is added and I think it \
doesn&#39;t<br> &gt; make sense.<br>
&gt; If there is a way to fix an item position, please let me know.<br>
<br>
</div>I guess you can consider this in the implementation of the add_to*<br>
methods of SimpleActivity.<br>
<br>
What I would do:<br>
<br>
- in the constructor of simple activity, add the main toolbar and the<br>
items that are always required: activity button, separator, stop<br>
button.<br>
<br>
- in the add_to* methods, consider the separator and stop button when<br>
inserting the new elements.  Insert them before.<br>
<div class="im"><br>
&gt; About new signals style:<br>
&gt; They look nicer, when I want to define a signal without a function, I can do<br>
&gt; my_signal = GObject.Signal(&#39;my_signal&#39;, arg_types=(int)) as you said, \
then<br> &gt; where I should put that?<br>
&gt;<br>
&gt; self.mysignal  = GObject.Signal(.... ?<br>
<br>
</div>Yes, making the signal an attribute of the class sounds right.<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
.. manuq ..<br>
_______________________________________________<br>
Lista olpc-Sur<br>
<a href="mailto:olpc-Sur@lists.laptop.org">olpc-Sur@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/olpc-sur" \
target="_blank">http://lists.laptop.org/listinfo/olpc-sur</a><br> \
</div></div></blockquote></div><br></div>



_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[prev in list] [next in list] [prev in thread] [next in thread]