Re: [Sugar-devel] [Design] Bulletin Board - Design Review
Yes we don't require three buttons as such. *self.board.share_button* is just the activity sharing button which is also available in the description panel but I had put it here too because I wanted all of them to be at one place so that user have to share the activity before using the bulletin board. I will remove it and let the one present in description panel be used. *self.board.box_button* just opens up the chat entry panel as shown in the video. *self.board.button* is the main button which hide/unhide the bulletin board i.e, the friends and clipboard tray, chat interface, entry, etc. I can modify the bulletin button to do hiding/unhiding of bulletin board as well as the chat entry panel. This would allow us to include all the functionalities with just one button. I am not aware about the collaboration panel as I was never able to share any activity due to the proxy issue which isn't resolved yet. On Mon, Jul 21, 2014 at 6:12 PM, Walter Bender wrote: > /me thinks these buttons could go on the collaboration panel (which is on > the activity toolbar), appearing when the activity is shared. > > > On Sun, Jul 20, 2014 at 10:51 PM, Gonzalo Odiard > wrote: > >> The main toolbar should not b used for this functionality. >> What you think about use the activity toolbar (the toolbar used to show >> the title, >> the description, and the share button) >> Also, you really need 3 buttons? >> What are the functions of the *self.board.box_button, >> self.board.share_button and self.board.button* >> Is not clear for me, can you explain? >> I think this would be all integrated in a single palette, like we did >> with the description button. >> Regards, >> >> Gonzalo >> >> >> >> On Sun, Jul 20, 2014 at 2:48 PM, Athar Haque wrote: >> >>> Thanks for the feedback. I was also thinking about the space issue in >>> the main toolbar. For this I have made the bulletin button as a toggle >>> button which would hide/unhide the other two buttons as well as the >>> bulletin board. So only when the bulletin board is active all the three >>> buttons would take up space in the main toolbar. >>> >>> I have included a demo in the wiki - http://youtu.be/-25pC3nCA3Y . This >>> would depict it better. >>> >>> If space is still an issue then I can leave two buttons (Bulletin and >>> chat entry) on the main toolbar and adjust the third one (sharing) with the >>> chat entry. Will this solve the space issue? >>> >>> >>> On Sun, Jul 20, 2014 at 1:13 AM, Gonzalo Odiard >>> wrote: >>> What you think about put all the buttons needed in the same container, making a little smaller the entry? That could be easier the integration in the activities, just add a single widget, and you don't need change the main toolbar. Usually the space in the main toolbar is scarce, and you need make the activity work with the screen rotated too. Gonzalo On Sat, Jul 19, 2014 at 1:13 PM, Athar Haque wrote: > Hello everyone, > > I have made a wiki page on Bulletin Board and would require feedback > on the design from you all. > > Link - http://wiki.sugarlabs.org/go/Summer_of_Code/2014/bulletinboard > > > would request you all to go through it and give your valuable > suggestions. > -- > Regards, > Nazrul > irc - native93 > > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > -- Gonzalo Odiard SugarLabs - Software for children learning >>> >>> >>> >>> -- >>> Regards, >>> Nazrul >>> >>> >>> ___ >>> Sugar-devel mailing list >>> Sugar-devel@lists.sugarlabs.org >>> http://lists.sugarlabs.org/listinfo/sugar-devel >>> >>> >> >> >> -- >> Gonzalo Odiard >> >> SugarLabs - Software for children learning >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > -- Regards, Nazrul ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Pootle SOS
I too have a dentist appointment Tue, not sure how long. I could make it Friday 15UTC, would that be ok? Regards, Sebastian El dom, 20 de jul 2014 a las 1:58 PM, Martin Abente escribió: I am OK with Tue 22 at 15:00 UTC. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Apache down on sunjammer
I connected this morning after reading this message and restarted apache. However I did not have time to investigate the root cause. El lun, 21 de jul 2014 a las 9:20 AM, Bernie Innocenti escribió: +systems@ On 07/21/2014 08:26 AM, Martin Abente wrote: Hello, Any idea why the services at sunjammer were stopped? The server is up an running, so I wonder if anyone is working there (deploying or updating something)?. Someone must have fixed it overnight while I was sleeping. Who's the good samaritan? In the future, if something important is down, do not hesitate to ring my phone, even at night. Downtime is bad for users. -- Bernie Innocenti Sugar Labs Infrastructure Team http://wiki.sugarlabs.org/go/Infrastructure_Team ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Apache down on sunjammer
+systems@ On 07/21/2014 08:26 AM, Martin Abente wrote: > Hello, > > Any idea why the services at sunjammer were stopped? The server is up an > running, so I wonder if anyone is working there (deploying or updating > something)?. Someone must have fixed it overnight while I was sleeping. Who's the good samaritan? In the future, if something important is down, do not hesitate to ring my phone, even at night. Downtime is bad for users. -- Bernie Innocenti Sugar Labs Infrastructure Team http://wiki.sugarlabs.org/go/Infrastructure_Team ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] getting image from gStreamer
yes, I guess you are right Gonzalo.I too was thinking that there would be
some pipeline issue because of which I am not able to get the image.Thanks
for the help :-)
On Mon, Jul 21, 2014 at 5:43 PM, Gonzalo Odiard
wrote:
> I think yoou should get the photo data from the gstreamer side,
> not from the widget where you are displaying it.
> If you look at the Record activity code,
> the logic used to take the photo is in glive.py take_photo method,
> and adding a sink to a tee in the gstreamer pipeline,
> and getting the data from there (_photo_handoff method)
>
> Gonzalo
>
>
> On Mon, Jul 21, 2014 at 2:50 AM, James Cameron wrote:
>
>> On Mon, Jul 21, 2014 at 11:14:16AM +0530, Puneet Kaur wrote:
>> >
>> >
>> >
>> > On Mon, Jul 21, 2014 at 10:56 AM, James Cameron
>> wrote:
>> >
>> > On Mon, Jul 21, 2014 at 02:07:15AM +0530, Puneet Kaur wrote:
>> > > Hey all,
>> > >
>> > > I was able to get the webcam stream using gStreamer through this :
>> > >
>> > > self.src = Gst.ElementFactory.make('autovideosrc', None)
>> > > self.sink = Gst.ElementFactory.make('autovideosink', None)
>> > >
>> > > (and more related corde...)
>> >
>> > Good.
>> >
>> > > but how to modify in order to store the image (on click) to a
>> file /
>> > buffer ?
>> > >
>> > > I tried :
>> > >
>> > > 1) gdk_display = GdkX11.X11Display.get_default()
>> > > gdk_window = GdkX11.X11Window.foreign_new_for_display
>> > (gdk_display,self.xid)
>> >
>> >
>> > the above two lines for fetching gdk window from a given xid
>> >
>> >
>> > > width = gdk_window.get_width()
>> > > height = gdk_window.get_height()
>> >
>> >
>> > width and height of the gdk window
>> >
>> >
>> > > ims = cairo.ImageSurface(cairo.FORMAT_ARGB32, width,
>> height)
>> >
>> >
>> > make a cairo surface
>> >
>> >
>> > > pb = Gdk.pixbuf_get_from_window(gdk_window, 0, 0, width,
>> height)
>> >
>> >
>> > get the pixbuf from the gdk window
>> >
>> >
>> > > cr = cairo.Context(ims)
>> >
>> >
>> > set the cairo context
>> >
>> >
>> >
>> > > Gdk.cairo_set_source_pixbuf(cr, pb, 0, 0)
>> >
>> >
>> > set cairo source
>> >
>> >
>> > > cr.paint()
>> >
>> >
>> >
>> > paint on the cairo context and then save the surface by :
>> ims.write_to_png
>> > ('testimage'+self.snapshot_name()+'.png')
>> >
>> >
>> >
>> >
>> > How are you copying the camera image to the surface? I can't see
>> how
>> > you do that in the above example.
>> >
>> >
>> >
>> > ^
>>
>> Sorry, I don't understand. Yes, I agree with the comments you added
>> to the code, but I don't see how you are copying the camera image to
>> the surface. As far as I can tell, you _must_ end up with a blank
>> surface if you don't put anything on it.
>>
>> --
>> James Cameron
>> http://quozl.linux.org.au/
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>
>
>
> --
> Gonzalo Odiard
>
> SugarLabs - Software for children learning
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Design] Bulletin Board - Design Review
/me thinks these buttons could go on the collaboration panel (which is on the activity toolbar), appearing when the activity is shared. On Sun, Jul 20, 2014 at 10:51 PM, Gonzalo Odiard wrote: > The main toolbar should not b used for this functionality. > What you think about use the activity toolbar (the toolbar used to show > the title, > the description, and the share button) > Also, you really need 3 buttons? > What are the functions of the *self.board.box_button, > self.board.share_button and self.board.button* > Is not clear for me, can you explain? > I think this would be all integrated in a single palette, like we did with > the description button. > Regards, > > Gonzalo > > > > On Sun, Jul 20, 2014 at 2:48 PM, Athar Haque wrote: > >> Thanks for the feedback. I was also thinking about the space issue in the >> main toolbar. For this I have made the bulletin button as a toggle button >> which would hide/unhide the other two buttons as well as the bulletin >> board. So only when the bulletin board is active all the three buttons >> would take up space in the main toolbar. >> >> I have included a demo in the wiki - http://youtu.be/-25pC3nCA3Y . This >> would depict it better. >> >> If space is still an issue then I can leave two buttons (Bulletin and >> chat entry) on the main toolbar and adjust the third one (sharing) with the >> chat entry. Will this solve the space issue? >> >> >> On Sun, Jul 20, 2014 at 1:13 AM, Gonzalo Odiard >> wrote: >> >>> What you think about put all the buttons needed in the same container, >>> making a little smaller the entry? >>> That could be easier the integration in the activities, just add a >>> single widget, >>> and you don't need change the main toolbar. >>> Usually the space in the main toolbar is scarce, >>> and you need make the activity work with the screen rotated too. >>> >>> Gonzalo >>> >>> >>> On Sat, Jul 19, 2014 at 1:13 PM, Athar Haque >>> wrote: >>> Hello everyone, I have made a wiki page on Bulletin Board and would require feedback on the design from you all. Link - http://wiki.sugarlabs.org/go/Summer_of_Code/2014/bulletinboard would request you all to go through it and give your valuable suggestions. -- Regards, Nazrul irc - native93 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel >>> >>> >>> -- >>> Gonzalo Odiard >>> >>> SugarLabs - Software for children learning >>> >> >> >> >> -- >> Regards, >> Nazrul >> >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> > > > -- > Gonzalo Odiard > > SugarLabs - Software for children learning > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] (no subject)
Hello, Any idea why the services at sunjammer were stopped? The server is up an running, so I wonder if anyone is working there (deploying or updating something)?. Saludos, tch. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] getting image from gStreamer
I think yoou should get the photo data from the gstreamer side,
not from the widget where you are displaying it.
If you look at the Record activity code,
the logic used to take the photo is in glive.py take_photo method,
and adding a sink to a tee in the gstreamer pipeline,
and getting the data from there (_photo_handoff method)
Gonzalo
On Mon, Jul 21, 2014 at 2:50 AM, James Cameron wrote:
> On Mon, Jul 21, 2014 at 11:14:16AM +0530, Puneet Kaur wrote:
> >
> >
> >
> > On Mon, Jul 21, 2014 at 10:56 AM, James Cameron
> wrote:
> >
> > On Mon, Jul 21, 2014 at 02:07:15AM +0530, Puneet Kaur wrote:
> > > Hey all,
> > >
> > > I was able to get the webcam stream using gStreamer through this :
> > >
> > > self.src = Gst.ElementFactory.make('autovideosrc', None)
> > > self.sink = Gst.ElementFactory.make('autovideosink', None)
> > >
> > > (and more related corde...)
> >
> > Good.
> >
> > > but how to modify in order to store the image (on click) to a file
> /
> > buffer ?
> > >
> > > I tried :
> > >
> > > 1) gdk_display = GdkX11.X11Display.get_default()
> > > gdk_window = GdkX11.X11Window.foreign_new_for_display
> > (gdk_display,self.xid)
> >
> >
> > the above two lines for fetching gdk window from a given xid
> >
> >
> > > width = gdk_window.get_width()
> > > height = gdk_window.get_height()
> >
> >
> > width and height of the gdk window
> >
> >
> > > ims = cairo.ImageSurface(cairo.FORMAT_ARGB32, width,
> height)
> >
> >
> > make a cairo surface
> >
> >
> > > pb = Gdk.pixbuf_get_from_window(gdk_window, 0, 0, width,
> height)
> >
> >
> > get the pixbuf from the gdk window
> >
> >
> > > cr = cairo.Context(ims)
> >
> >
> > set the cairo context
> >
> >
> >
> > > Gdk.cairo_set_source_pixbuf(cr, pb, 0, 0)
> >
> >
> > set cairo source
> >
> >
> > > cr.paint()
> >
> >
> >
> > paint on the cairo context and then save the surface by :
> ims.write_to_png
> > ('testimage'+self.snapshot_name()+'.png')
> >
> >
> >
> >
> > How are you copying the camera image to the surface? I can't see how
> > you do that in the above example.
> >
> >
> >
> > ^
>
> Sorry, I don't understand. Yes, I agree with the comments you added
> to the code, but I don't see how you are copying the camera image to
> the surface. As far as I can tell, you _must_ end up with a blank
> surface if you don't put anything on it.
>
> --
> James Cameron
> http://quozl.linux.org.au/
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
--
Gonzalo Odiard
SugarLabs - Software for children learning
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
