Four multimedia plugins make WordPress more fun


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Four multimedia plugins make WordPress more fun
# 1  
Old 05-05-2008
Four multimedia plugins make WordPress more fun

Mon, 05 May 2008 08:00:00 GMT
WordPress plugins for multimedia can make your blog more interesting. These four plugins make it possible to automatically generate and configure multimedia, making your site a richer experience for your visitors and for you.


Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Disable multimedia access in Linux

is there a way on how to disable multimedia access in linux like ubuntu? in this way user will not be able to play media files. (via command line or grapical tool) (1 Reply)
Discussion started by: lhareigh890
1 Replies

2. UNIX for Dummies Questions & Answers

playing multimedia content under openbsd with Xvid and mplayer

hello. I just installed OpenBSD3.5 and now am using gnome2.4. i've installed mplayer from the openbsd.org packages directory and it seems to work with all kinds of media. The trouble is, it plays all videos too fast. The picture rate is too high and sound is too fast, too. I wonder if anyone... (1 Reply)
Discussion started by: sablot
1 Replies
Login or Register to Ask a Question
Module::Starter::Plugin(3pm)				User Contributed Perl Documentation			      Module::Starter::Plugin(3pm)

NAME
Module::Starter::Plugin -- how Module::Starter plugins work DESCRIPTION
This document is a guide to writing plugins for Module::Starter. Currently, as is evident, it isn't very comprehensive. It should provide enough information for writing effective plugins, though. After all, Module::Starter's guts are nice and simple. "Module::Starter->import" Module::Starter provides an import method, the arguments to which are plugins, in the order in which they should be loaded. If no plugins are given, Module::Starter::Simple (and only Module::Starter::Simple) is loaded. By default, the given modules are required and arranged in an is-a chain. That is, Module::Starter subclasses the last plugin given, which subclasses the second-to-last, up to the first plugin given, which is the base class. If a plugin provides a "load_plugins" method, however, the remaining plugins to be loaded are passed to that method, which is responsible for loading the rest of the plugins. This architecture suggests two kinds of plugins: engine plugins An engine is a plugin that stands alone, implementing the public "create_distro" method and all the functionality required to carry out that implementation. The only engine included with Module::Starter is Module::Starter::Simple, and I'm not sure any more will be seen in the wild any time soon. plain old plugins Other plugins are designed to subclass an engine and alter its behavior, just as a normal subclass alters its parent class's. These plugins may add features to Module::Starter engines, or may just provide general APIs for other plugins to exploit (like Module::Starter::Plugin::Template.) The template plugin is a simple example of a plugin that alters an engine to accept further plugins. Other plugins like template will probably be written in the near future, and plugins that exploit the API provided by Module::Starter::Plugin::Template will be available on the CPAN. AUTHOR
Ricardo SIGNES "<rjbs at cpan.org>" COPYRIGHT
Copyright 2005, Ricardo SIGNES. All Rights Reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.12.4 2010-05-28 Module::Starter::Plugin(3pm)