Slashdot Mirror

← Back to Stories (view on slashdot.org)

Is There a Guide for Writing XMMS Plugins?

Posted by Cliff on from the extending-the-functionality dept.

Anthanos asks: "I was recently asked to put together a Winamp and an XMMS plugin to do some pretty cool things. Having never done plugin development for either I went to their respective webpages and began looking for samples and/or SDKs to make use of. Winamp provided very well put together documentation and SDKs, but I can't find anything similar for XMMS. Has any such documentation or guide been put together? All I have found reference to so far are existing projects. I was hoping for the equivalent of 'Hello World!' for XMMS."

7 comments

  1. try google by milgram · · Score: 2

    There were a few guides there. For free!

  2. I believe by Beowulf_Boy · · Score: 2

    XMMS and WinAMp use the same plugins, so just use the Winamp Documentation for XMMS plugins, and it should work.

    1. Re:I believe by crazney · · Score: 3

      except for the fact that plugins are binaries, and being binaries they have to be compiled.. and in the current world, they are compiled using C or C++, or some other language that is platform dependant... so, they cant just me "compatible" considering code from one platform (windows) is not 100% portable to another platforum (unix os', linux, freebsd etc)..

      just a thought.

      --
      stuff
    2. Re:I believe by Xunker · · Score: 4

      Uhm. No.

      They *started* out being similar, because Justin needed a framework to work off of, but it hasn't been line this since WinAmp moved to 2.x -- true, it may still supports 1.x plugins, but..

      And at the same time, XMMS (x11amp) has been evolving, too, and extending itself and it's API.

      Maybe it's worth someomes' time to design a uniform IPC API for media players? That would be a very interesting propsition.
      .

      --
      Hilary Rosen's speech was about her love of money and her desire to roll around naked in a pile of money.
  3. Re:The cheesy spectrum analyzer plugin... by Anonymous Coward · · Score: 3

    Source code != API documentation.

    The reason you want API docs is to use said API fully. The poster may need to use features of the API not used in the spectrum analyzer. In fact, if its as cheesy as you say, wouldn't you WANT him to make more use of the API?

    When will people learn you should not code to interfaces you don't fully comprehend.

  4. Use The Source. by WWWWolf · · Score: 3
    Regrettably XMMS plugin API isn't documented too well. However, if I had had a proper API documentation when participating in the XMMS plugin competition, I would have saved maybe 2 hours when making the plugin. (I wrote the whole plugin within 24 hour period, just before the deadline - it was a SID plugin, and this whole mess was pretty strange because I made the plugin without knowing anything about XMMS, GLib or Sidplay - and in case of each library, the documentation just plain sucked. Your Mileage Might Vary.)

    It's fairly straightforward... just take a look at the existing plugins. First, define a *Plugin struct (see plugin.h), and then make functions to which you pointed to from the structure.

  5. The cheesy spectrum analyzer plugin... by ameoba · · Score: 4

    isn't there because it's an interesting bit of code. Granted it could be better commented, but it's all fairly self-explanatory. The other plugins that ship with it are also fairly simple. When combined with actually looking at the players sources should give you more than enough info on writing a plugin.


    [insert snide comment about posting to /. for something that could be discovered with 5min of research]

    --
    my sig's at the bottom of the page.