Search results

plone4artists-fileimage-1.0.2-3.lbn19.noarch

p4a.file is a field/widget pair for handling fields that contain binary data.

plone4artists-fileimage-1.0.2-3.lbn25.noarch

p4a.file is a field/widget pair for handling fields that contain binary data.

plone4artists-ploneaudio-1.1rc1-5.lbn13.noarch

The p4a.ploneaudio egg is a Plone product built to expose the p4a.audio framework in a Plone setting. In a nutshell it provides the following features: File support Uploaded File objects are scanned for audio mime types and are audio enhanced automatically if a registered mime type is found. Audio container support Any folder or smart folder can be media activated which turns it into an audio container which knows how to display an overview for all contained audio. Embedded media player support MP3 and Ogg audio files can be played inline within the browser. Audio metadata support Audio information is read from and written to MP3 and Ogg audio files. Podcasting support Audio containers (activated folders or smart folders) can have ther contents broadcast using RSS with enclosures representing the individual audio files. Content Licensing support All audio content can automatically be licensed using the ContentLicensing product.

plone4artists-ploneaudio-1.1rc1-5.lbn19.noarch

The p4a.ploneaudio egg is a Plone product built to expose the p4a.audio framework in a Plone setting. In a nutshell it provides the following features: File support Uploaded File objects are scanned for audio mime types and are audio enhanced automatically if a registered mime type is found. Audio container support Any folder or smart folder can be media activated which turns it into an audio container which knows how to display an overview for all contained audio. Embedded media player support MP3 and Ogg audio files can be played inline within the browser. Audio metadata support Audio information is read from and written to MP3 and Ogg audio files. Podcasting support Audio containers (activated folders or smart folders) can have ther contents broadcast using RSS with enclosures representing the individual audio files. Content Licensing support All audio content can automatically be licensed using the ContentLicensing product.

plone4artists-ploneaudio-1.1rc1-5.lbn25.noarch

The p4a.ploneaudio egg is a Plone product built to expose the p4a.audio framework in a Plone setting. In a nutshell it provides the following features: File support Uploaded File objects are scanned for audio mime types and are audio enhanced automatically if a registered mime type is found. Audio container support Any folder or smart folder can be media activated which turns it into an audio container which knows how to display an overview for all contained audio. Embedded media player support MP3 and Ogg audio files can be played inline within the browser. Audio metadata support Audio information is read from and written to MP3 and Ogg audio files. Podcasting support Audio containers (activated folders or smart folders) can have ther contents broadcast using RSS with enclosures representing the individual audio files. Content Licensing support All audio content can automatically be licensed using the ContentLicensing product.

plone4artists-plonecalendar-2.1b1-3.lbn13.noarch

p4a.plonecalendar is a project which extends the p4a.calendar framework to run natively within a Plone environment. It contains the extensions that require Plone, and the adaptions to Plone. This is mainly support for Plone event types and iCalendar import/export. Plone4Artists calendar can import an iCalendar file over http into a Plone calendar. This is useful for example if another site presents a schedule that you also want to present or integrate into your site. An example url for importing an icalendar file over http is:: http://path/to/calendar/import_from_url?url=http://url/to/icalendarfile.ics This will open up a connection to the other site, get the icalendar file called "icalendarfile.ics" and import it into the folder located at /path/to/calendar/

plone4artists-plonecalendar-2.1-1.lbn19.noarch

p4a.plonecalendar is a project which extends the p4a.calendar framework to run natively within a Plone environment. It contains the extensions that require Plone, and the adaptions to Plone. This is mainly support for Plone event types and iCalendar import/export. Plone4Artists calendar can import an iCalendar file over http into a Plone calendar. This is useful for example if another site presents a schedule that you also want to present or integrate into your site. An example url for importing an icalendar file over http is:: http://path/to/calendar/import_from_url?url=http://url/to/icalendarfile.ics This will open up a connection to the other site, get the icalendar file called "icalendarfile.ics" and import it into the folder located at /path/to/calendar/

plone4artists-plonecalendar-2.1-1.lbn25.noarch

p4a.plonecalendar is a project which extends the p4a.calendar framework to run natively within a Plone environment. It contains the extensions that require Plone, and the adaptions to Plone. This is mainly support for Plone event types and iCalendar import/export. Plone4Artists calendar can import an iCalendar file over http into a Plone calendar. This is useful for example if another site presents a schedule that you also want to present or integrate into your site. An example url for importing an icalendar file over http is:: http://path/to/calendar/import_from_url?url=http://url/to/icalendarfile.ics This will open up a connection to the other site, get the icalendar file called "icalendarfile.ics" and import it into the folder located at /path/to/calendar/

plone4artists-ploneevent-0.7.4-2.lbn13.noarch

This package contains extensions to the standard Event of Plone. Currently only the extension is included: Recurrence.

plone4artists-ploneevent-0.7.4-2.lbn19.noarch

This package contains extensions to the standard Event of Plone. Currently only the extension is included: Recurrence.