On Wednesday, May 18, 2011 16:20:02 Aaron J. Seigo wrote:
* one source per service, e.g. youtube
NO! :D
For this kind of stuff, we should completely (== as much as possible) ignore
the service itself. So instead of a youtube engine, we create a videoengine
(which itself uses youtube
On Thursday, May 19, 2011 11:26:36 Aaron J. Seigo wrote:
On Thursday, May 19, 2011 10:40:11 Sebastian Kügler wrote:
On Wednesday, May 18, 2011 16:20:02 Aaron J. Seigo wrote:
* one source per service, e.g. youtube
NO! :D
For this kind of stuff, we should completely
Hello,
I would like to write a youtube player plasmoid (simple search form and
video view), like does minitube (http://flavio.tordini.org/minitube)
The plan is to write the applet in QML/JS
What is more problematic for me is writing the dataengine : i've some lack
to understand how it really
Hi Jérôme,
On Wednesday, May 18, 2011 15:36:38 Jérôme Pigeot wrote:
I would like to write a youtube player plasmoid (simple search form and
video view), like does minitube (http://flavio.tordini.org/minitube)
The plan is to write the applet in QML/JS
That sounds like a good choice. :)
What
On Wednesday, May 18, 2011 15:36:38 Jérôme Pigeot wrote:
If the search get a certain number of videos, how do you integrate it in the
dataengine??? and then in the applet??
in that case, the DataEngine would create multiple key/value entries. however,
what i would really recommend is doing it
Thanks for your answers guys, your indications will be very usefull for me!!
Right i never looked around plasma-mediacenter to see how they manage video
services and it can be a good start.
I really think that splitting applet/dataengine is the good way to offer
flexibles solutions.
Let's start
