DEPRECATION WARNING

This documentation is not using the current rendering mechanism and is probably outdated. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.

EXT: CSS styled MULTIMEDIA

Author:Kasper Skårhøj
Created:2002-11-01T00:32:00
Changed by:Andreas Schwarzkopf
Changed:2005-09-29T18:05:15
Author:Andreas Schwarzkopf
Email:schwarzkopf@artplan21.de
Info 3:
Info 4:

EXT: CSS styled MULTIMEDIA

Extension Key: css_styled_multimedia

Copyright 2000-2002, Andreas Schwarzkopf, <schwarzkopf@artplan21.de>

This document is published under the Open Content License

available from http://www.opencontent.org/opl.shtml

The content of this document is related to TYPO3

- a GNU/GPL CMS/Framework available from www.typo3.com

Table of Contents

EXT: CSS styled MULTIMEDIA 1

Introduction 1

What does it do? 1

Screenshots 1

Users manual 2

FAQ 2

Configuration 2

Reference 2

Known problems 3

To-Do list 3

Changelog 3

Introduction

What does it do?

The extension is an addon for CSS Syled Content and implements an xhtml and accessibility compliant, css based MULTIMEDIA cObject.

Screenshots

img-1

Users manual

Select the type of your content element as usual – Multimedia. Then you will see a couple of fields related to your user right:

select the multimedia file or upload one

enter the width and the height of the plugin area, or leave it blank for default size

put the alternative description of the multimedia content for accessibility reasons, in this field you can also put a notice for people who have not installed the right plugin with a link to the plugin vendor; you don't need to enter HTML markup here, because paragraphs will be added automatically, http and mail links will be resolved correctly as a link in the frontend etc.

the next field – plugin parameters – is sometimes needed for some plugins or applications, e.g. the path to the application source files etc. Start each parameter on a new line, so they can be organized in separate html elements.

the last field is for application parameters if needed, e.g. you can submit to your some links and texts to your flash animation wich are added to the file name this way: flashfile.swf?parameter1=someText&parameter2=http://www.yourlink.net

FAQ

  • Wich HTML element is used to output the source code of the page in the frontend?

    - OBJECT, because EMBED is not standard compliant

  • Wich browser can support this multimedia element in the frontend?

    - flash, videos and java applets are supported by every modern browser, including IE, Firefox, Opera. Netscape 4 have big problems with it; IE can not support images and some other stuff

Configuration

The extension can only be installed if the extension css_styled_content is already running on your system, because it is the base technology for this extension.

If you install the extension, you will be asked, whether you wish to use DAM reference technology or / and the traditional file system. You can choose both or only DAM reference, if you have installed DAM in a version >= 0.3.0.

The first step after the installation is to activate the default TypoScript configuration of this extension. You can do it in your main template: choose the entry “CSS Styled MULTIMEDIA (css_styled_multimedia)” in the field “Include static (from extensions)”. Then you can override some TypoScript settings, if you wish.

The most part of the TypoScript settings is taken unchanged from css_styled_content, so refer to the TSRef part about cObject element “MULTIMEDIA”. Additional configuration you will find here.

Reference

userFunc: tx_cssstyledmultimedia->cssMULTIMEDIA

width

a

width

b

string / stdWrap

c

Width of the multimedia object element in the frontend. By default the global constant styles.content.imgtext.maxW is used here, the backend field “Width” overrides this setting.

d

height

a

height

b

string / stdWrap

c

Height of the multimedia object element in the frontend. By default the global constant styles.content.imgtext.maxW is used here, the backend field “Height” overrides this setting.

d

stdWrap

a

stdWrap

b

stdWrap

c

Wraps the whole object element

d

wrap=<div class="multimedia">|</div>

alternative

a

alternative

b

string / stdWrap

c

Alternative description of multimedia content, wich will be displayd inside of the object element, so the user see it if he has not the right plugin.

The backend field “Alternative Description” is taken by default.

d

addParams

a

addParams

b

string / stdWrap

c

additional param elements wich can be configured in the TS template

d

addAttribs

a

addAttribs

b

string / stdWrap

c

additional attributes in the object element wich can be configured in the TS template

d

aparams

a

aparams

b

string / stdWrap

c

Application parameters wich will be submitted as URL query string.

The backend field “application parameters” will be taken by default.

d

DAM reference configuration

a

DAM reference configuration

b

->tx_dam

->tx_damttcontent

c

If you use this extension together with DAM reference, check the appropriate documentation: some TypoScript will be added for getting the dam file references.

d

[tsref:(cObject).MULTIMEDIA]

((generated))
Example

default configuration:

includeLibs.tx_cssstyledmultimedia = EXT:css_styled_multimedia/class.tx_cssstyledmultimedia.php
tt_content.multimedia.20 = USER
tt_content.multimedia.20.userFunc = tx_cssstyledmultimedia->cssMULTIMEDIA
tt_content.multimedia.20 {
  width = {$styles.content.imgtext.maxW}
  width.override.field = imagewidth
  height = {$styles.content.imgtext.maxW}
  height.override.field = imageheight
  stdWrap.wrap = <div class="multimedia">|</div>
  alternative.field = imagecaption
  alternative.parseFunc = < lib.parseFunc_RTE
  aparams.field = tx_cssstyledmultimedia_parameters
}

Known problems

Older versions (<0.1.2) have a bug: the Flexform field is broken if you install this extension. Install the current version.

To-Do list

More testing of different multimedia types, browser checking, debugging.

Changelog

  • 0.1.0 initial TER version
  • 0.1.3 pi_flexform bug fixed, new field is added to tt_content – for application parameters

img-2 EXT: CSS styled MULTIMEDIA - 3