This document provides an overview of Grilo, a framework for integrating multimedia content into applications. Grilo aims to provide a single API for accessing media from various services, hiding differences in APIs, protocols and technologies. This allows application developers to write code that works across multiple supported media sources. The presentation discusses challenges in media integration, how individual developers currently solve them, and how Grilo provides a shared platform for collaboration. A demo then shows Grilo in use before discussing how it benefits both application and backend/plugin developers.

1. GRILO
static void
_f_do_barnacle_install_properties(GObjectClass
*gobject_class)
{
GParamSpec *pspec;
Integrating multimedia
content in applications
/* Party code attribute */
pspec = g_param_spec_uint64
(F_DO_BARNACLE_CODE,
"Barnacle code.",
"Barnacle code",
0,
G_MAXUINT64,
G_MAXUINT64 /*
default value */,
G_PARAM_READABLE
| G_PARAM_WRITABLE |
G_PARAM_PRIVATE);
g_object_class_install_property (gobject_class,
F_DO_BARNACLE_PROP_CODE,
Embedded Linux Conference Europe
Cambridge, October 2010
Iago Toral Quiroga
itoral@igalia.com

2. Index
➔
Media Integration
➔
Overview of Grilo
➔
Demo
➔
Grilo for application developers
➔
Grilo for backend developers

3. Media Integration

4. Media Integration: services

5. Media Integration: hardware

6. Media Integration: Present
➔
What are the challenges?
➔
Homogeneous, integrated user experience.
➔
Easy to use.
➔
Service scalability.
➔
Decrease development and maintenance effort.

7. Media Integration: Present
➔
What are the problems?
➔
Lots of heteregeneous services.
➔
Lots of APIs and protocols.
➔
Lots of technologies.

8. Media Integration: Present
➔
What are we doing now?
➔
Individual makers developing in-house solutions.
➔
Not efficient.
➔
Slow development.
➔
Not scalable.
➔
Expensive maintenance.

9. Media Integration: Future
➔
What can we do about this?
➔
Platform level solution for accessing media content.
➔
Stop reinventing the wheel, start reusing code.
➔
A place where interested actors can collaborate.

10. Media Integration: Future
➔
What are the benefits?
➔
Reduce and share maintenance effort.
➔
Focus on added value.
➔
Faster development.
➔
Scalability.

11. Grilo: Overview

12. Grilo: Overview
➔
➔
➔
➔
➔
A framework for easing access to multimedia content.
Application developers want to browse / search
content from many services...
...but they don't want to know how they work internally
(APIs, protocols, technologies, limitations, ...)
Single API to access media content, hiding
differences among media providers.
Application developers write their solution once and it
will work for any service supported in Grilo.

13. Grilo: Overview

14. Demo

15. Grilo for application developers

16. Grilo for plugin developers

17. Resources
➔
Wiki:
➔
➔
http://live.gnome.org/Grilo
Git repositories:
➔
➔
➔
git://git.gnome.org/grilo
git://git.gnome.org/grilo-plugins
IRC:
➔
➔
Mailing list:
➔
➔
grilo @ GIMPNet
http://mail.gnome.org/mailman/listinfo/grilo-list
Bugzilla:
➔
http://bugzilla.gnome.org
●
Category: Other, Product: grilo

18. Image Credits
➔
Easy button: Jason Gulledge, www.flickr.com
➔
➔
Dead end: AJC1, www.flickr.com
➔
➔
http://www.flickr.com/photos/thinkpublic/3042777307/sizes/
m/in/photostream
Headache: www.freeclipartnow.com
➔
➔
http://www.flickr.com/photos/ajc1/3019611194
Collaboration: thinkpublic, www.flickr.com
➔
➔
http://www.flickr.com/photos/ramdac/373881476
http://www.freeclipartnow.com/science/medicine/people/hea
dache.jpg.html
Thumbs up: Stefano Valle, www.freedigitalphotos.net
➔
http://www.freedigitalphotos.net/images/Gestures_g185Two_Hands_Thumbs_Up_p20593.html

19. ?