Deprecated: Assigning the return value of new by reference is deprecated in /homepages/37/d13445233/htdocs/wordpress/wp-settings.php on line 520

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/37/d13445233/htdocs/wordpress/wp-settings.php on line 535

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/37/d13445233/htdocs/wordpress/wp-settings.php on line 542

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/37/d13445233/htdocs/wordpress/wp-settings.php on line 578

Deprecated: Function set_magic_quotes_runtime() is deprecated in /homepages/37/d13445233/htdocs/wordpress/wp-settings.php on line 18

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/37/d13445233/htdocs/wordpress/wp-includes/wp-db.php on line 306

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/37/d13445233/htdocs/wordpress/wp-includes/cache.php on line 431

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/37/d13445233/htdocs/wordpress/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/37/d13445233/htdocs/wordpress/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/37/d13445233/htdocs/wordpress/wp-includes/http.php on line 61

Strict Standards: Non-static method K2::init() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/themes/k2/functions.php on line 17

Strict Standards: Non-static method K2::register_scripts() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/themes/k2/app/classes/k2.php on line 64

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Options::init() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-includes/plugin.php on line 339

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2SBM::init() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-includes/plugin.php on line 339

Strict Standards: Non-static method K2SBM::load_modules() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/themes/k2/app/classes/widgets.php on line 41

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Header::init() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-includes/plugin.php on line 339

Strict Standards: Non-static method K2Header::get_header_width() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/themes/k2/app/classes/header.php on line 15

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GoogleSitemapGeneratorLoader::Enable() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-includes/plugin.php on line 339

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2::add_custom_query_vars() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2::dynamic_content() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-includes/plugin.php on line 339
JW Player « Webwatch Onvion
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Header::output_header_css() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-includes/plugin.php on line 339

Strict Standards: Non-static method K2Header::get_header_image_url() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/themes/k2/app/classes/header.php on line 113


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 55
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/37/d13445233/htdocs/wordpress/wp-includes/functions.php on line 41
class="post hentry category-tools tag-drupal tag-flash tag-jw-flv-media-player p1 y2009 m03 d28 h14">

JW Player


Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::the_content() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-includes/plugin.php on line 166

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 514

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 514

Strict Standards: Non-static method GA_Filter::ga_parse_link() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 503

Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 478

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 514

Strict Standards: Non-static method GA_Filter::ga_parse_link() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 503

Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 478

Wer ein Video auf seine eigene Website einbetten möchte, hat heute eine Reihe von Möglichkeiten. Der einfachste Weg ist sicherlich auf einen Dienst wie YouTube zurück zu greifen. Man läd den Film dort hoch und erhält einen Code, den man nur an passender Stelle in die eigenen Webseite oder den Blog einfügt.

Wenn man allerdings nicht auf diese Dienste zurück greifen möchte, sondern die Videodatei selber hostet oder auf einem anderen Server zur Verfügung gestellt bekommt, kann man sie in den meisten Fällen ganz normal über die im HTML-4 Standart festgelegten Befehle einbauen. Oder man besorgt sich einen passenden Player, der dann für den Nutzer der Website oder des Blogs mehr komfort bietet. Für flv Dateien ist so ein Player zum Beispiel der JW FLV Media Player. Den kann man für private Seiten kostenlos nutzen und über Skins an die eigenen Vorstellungen anpassen. Der Player muß dazu in ein zur Website gehörendes Verzeichnis hoch geladen werden und der dazu gehörige Code wird angepasst, unter anderem müssen der Name und Speicherort der flv Datei eingesetzt werden, und in die entsprechende html Seite eingebaut.

Der JW FLV Media Player kann aber auch mit Drupal verwendet werden. Eine Anleitung dazu gibt es im deutschen Drupal Handbuch.

1 Responses to “JW Player”


Leave a Reply





Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::spool_analytics() should not be called statically in /homepages/37/d13445233/htdocs/wordpress/wp-includes/plugin.php on line 339