Hi Kristian, Kristian Lippert a écrit : > Hi Oliver > I hope it is fine to send you a direct mail because this is not a > typical "forum help" or a "bug report". Please correct me in this matter > if you find it necessary!
I'm forwarding this answer to the Elisa public mailing list as others will for sure be interested in your work, the questions you have and their answers. > I tried to create a plugin for my explicitly entered mms-streams. > It is based on the SHOUTcast plugin, but a lot simpler with a 1-layer > content model > I did it on my windows machine and had the plugin appear under > Music/Internet after the SHOUTcast plugin > So when starting "elisa" the icon was after the SHOUTcast icon, but it > did not work (as for seen) when activated so I wanted to debug it on my > Ubuntu 8.10 (I now know how PDB works there :-) Have you read our plugin developer documentation (https://elisa.fluendo.com/wiki/Docs/PluginTutorial)? It is a good entry point and will guide you through the necessary steps to write and package a plugin properly. As it is still a young document, any feedback on what could be improved in it is more than welcome. > So I moved the egg-folder and the plugin folder to the Linux box in: > egg: elisa_plugin_mystream-0.1.egg-info (it was originaly > elisa_plugin_mystream.egg-info on the Windows Box) > plugin: /usr/share/pyshared/elisa/plugins/mystream When developing on linux, as a rule of thumb, never temper with the root file system. You should have a local development copy of elisa and your plugin should be deployed in ~/.elisa-0.5/plugins/. All this is explained in the documentation. > But on the Linux box the icon did not appear (and I could not activate it)? > > What am I doing wrong and what am I missing? > > I could see the the Linux version has a SOURCES.txt file that is extra > compared to the windows version. It tried to create this for my Linux > version of the MyStream plugin, but that did not help That should not be an issue. > Please advice? I had a very quick look at the code you sent me. I would say that it can be done in a much simpler way. If you already have the URLs to the MMS streams then you don't need a resource provider and new models. A simple controller that lists the streams and passes a PlayableModel to the player should do (in a first step, let's make things simple first, and then enrich them!). The player, being gstreamer-based, is perfectly able to handle MMS streams. > Best Regards, > Kristian > > P.S: I have attached the "real-ugly" MyStream plugin and egg that I have > on my Windows XP box Keep up the good work, and don't hesitate to ask for help on this mailing list or our IRC channel (freenode/#elisa). Cheers, Olivier
