scratch team mailing list archive

[Derek O'Connell <doc@xxxxxxxxxxxxxxxxx>]

Hi Bert,

thanks for the attachments.

>GStreamer is not really meant to be used for generated sound. It's more
of a media decoding framework.

True but it was a such a common request that a year ago the GSt
developers finally promoted the "App Library"  containing the
appsrc/appsink plugins to the "base" set which mean they then became
officially supported. I think it was around the second half of 2009 by
the time they made it into Ubuntu as standard and could therefore be
relied upon by application developers. Here's some links, the first
being the request to move them into base:

https://bugzilla.gnome.org/show_bug.cgi?id=564421
http://www.gstreamer.net/data/doc/gstreamer/head/gst-plugins-base-libs/html/gstreamer-app.html
http://www.gstreamer.net/data/doc/gstreamer/head/gst-plugins-base-libs/html/gst-plugins-base-libs-appsrc.html
http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-base-libs/html/gst-plugins-base-libs-appsink.html

-D



On 11/02/2010 08:23, Bert Freudenberg wrote:
> On 10.02.2010, at 22:39, Derek O'Connell wrote:
>   
>> I know very little about the Debian packaging &
>> distribution process let alone RPM, though I guess they are two separate
>> processes and the RPM package has it's own maintainer/s?
>>     
> Each distribution has their own package maintainers, yes. In general it's not needed (and effectively impossible) for an open-source project to even know all the ways your software gets packaged.
>
> For example, I try to keep track of in which distros Squeak and Etoys pops up, though it generally isn't expected of an "upstream" project to even get involved directly with bugs found in a particular packaging:
>
> http://wiki.squeakland.org/display/sq/Bug+Tracking
>
>   
>>> As for DBus, I made a changeset that makes it work in current Scratch. It's part of my sugarization work. What would you need it for though?
>>>
>>>       
>> In the first instance receiving and reacting sensibly to critical system
>> messages, eg, "battery-low".
>>     
> Ah, makes sense.
>
>   
>> Could otherwise be useful in the future for
>> greater platform integration and for communicating with other
>> applications. It seems to be almost standard now to send hw sensor data
>> over DBus... instant thought... does the XO send a msg when the screen
>> is folded back into tablet mode?
>>     
> Likely, but I'm not sure.
>
>
>   
>> **** Btw, I'm just checking mail archives and getting confused. Did
>> anyone see my reply to Bert's email from 2nd Feb that ended with...
>>
>>     
>>> Nice! Do you possibly have changesets for this to migrate it to a
>>>       
>> current image?
>>     
>>> Also, I just noticed that linux@xxxxxxxxxxxxxxx is an alias for the
>>>       
>> launchpad list? Had me confused ...
>>
>> ...I replied to linux@xxxxxxxxxxxxxxx with the change-sets attached but cannot seem to locate the post in mail archives. Please let me know if not.
>>     
> I got them, though I didn't base mine on it since I had already started porting and you said it your's wasn't finished yet. 
>
>   
>> I will repost after this email just to be sure. The attachments may be redundant if Bert has already done the migration but I don't like the fact that it appears I have not bothered replying. Btw, Bert, where can I get your version?
>>     
> Not published yet, attaching. I wouldn't consider this "stable" yet. In fact, when I just tried, it didn't work anymore :/
>
> Anyway, it's two changesets, one to add compatibility methods and one for the actual DBus bindings.
>
>   
>> @Amos: I guess we are now all using linux@xxxxxxxxxxxxxxx ?
>>     
> What's the difference to scratch@xxxxxxxxxxxxxxxxxxx ?
>
>   
>>>> You mentioned previously about utilising mainstream VM, is there any
>>>> progress or plan for that? Is the Scratch plug-in going to be pushed
>>>> upstream?
>>>>
>>>>         
>>> You need to communicate with the VM maintainers about that. Also read this thread:
>>>
>>> http://lists.squeakfoundation.org/pipermail/vm-dev/2009-September/003182.html
>>>
>>>       
>> I realise your comment was probably aimed at Amos but I was simply
>> looking for a date when it might happen. Is the licence issue resolved?
>>     
> I don't think I ever heard back from John on the matter. It seemed like a good idea but there was not much interest except mine, so I have not been pushing the issue.
>
> - Bert -
>   
>
>
> This body part will be downloaded on demand.