You are here

Home » API reference » Embedded Media Field 6

README.txt in Embedded Media Field 6

Same filename in this branch
  1. 6 README.txt
  2. 6 contrib/emimport/README.txt
  3. 6 contrib/emthumb/README.txt
  4. 6 contrib/emaudio/README.txt
  5. 6 contrib/eminline/README.txt
  6. 6 contrib/emimage/README.txt
  7. 6 contrib/emvideo/README.txt
  8. 6 contrib/video_cck/readme.txt
  9. 6 contrib/emwave/README.txt
  10. 6 contrib/image_ncck/readme.txt
Same filename and directory in other branches
  1. 6.3 contrib/emimage/README.txt
  2. 6.2 contrib/emimage/README.txt
/********************/
 Embedded Image Field
/********************/

Author: Aaron Winborn
Development Began 2007-06-13

Requires: Drupal 5, Content (CCK), Embedded Media Field
Optional: Views

This extensible module will create a field for node content types that can be used to display images from various third party
image providers. When entering the content, the user will simply paste the URL or embed code of the image, and the module will
automatically determine which content provider is being used. When displaying the image, the proper embedding format will be
used, calling any necessary API's.

The module already supports Flicker, Imageshack, and Photobucket image formats. More are planned to be supported soon. An api allows other
third party providers to be supported using simple include files and provided hooks. (Developers: examine the documentation of
/providers/flikr.inc for help in adding support for new providers).

The administer of a site may decide whether to allow all content providers, or only a certain number of them. They may
further be limited when configuring the field.

On the Display Fields settings page, the administrator may further choose how to display the image, for teasers and body.
Images may be displayed in a thumbnail, preview, or full size, each of configurable sizes. Unfortunately, for now, because
images are not stored locally, we don't have access to the powerful features of imagecache.

Some providers may provide other features that are supported by Image Neighborhood CCK. You can find those settings at
admin/content/emfield, in the fieldset for the specific provider.

Questions can be directed to winborn at advomatic dot com

File

contrib/emimage/README.txt
View source 
  1. 

  2. /********************/

  3.  Embedded Image Field

  4. /********************/

  5. 

  6. Author: Aaron Winborn

  7. Development Began 2007-06-13

  8. 

  9. Requires: Drupal 5, Content (CCK), Embedded Media Field

  10. Optional: Views

  11. 

  12. This extensible module will create a field for node content types that can be used to display images from various third party

  13. image providers. When entering the content, the user will simply paste the URL or embed code of the image, and the module will

  14. automatically determine which content provider is being used. When displaying the image, the proper embedding format will be

  15. used, calling any necessary API's.

  16. 

  17. The module already supports Flicker, Imageshack, and Photobucket image formats. More are planned to be supported soon. An api allows other

  18. third party providers to be supported using simple include files and provided hooks. (Developers: examine the documentation of

  19. /providers/flikr.inc for help in adding support for new providers).

  20. 

  21. The administer of a site may decide whether to allow all content providers, or only a certain number of them. They may

  22. further be limited when configuring the field.

  23. 

  24. On the Display Fields settings page, the administrator may further choose how to display the image, for teasers and body.

  25. Images may be displayed in a thumbnail, preview, or full size, each of configurable sizes. Unfortunately, for now, because

  26. images are not stored locally, we don't have access to the powerful features of imagecache.

  27. 

  28. Some providers may provide other features that are supported by Image Neighborhood CCK. You can find those settings at

  29. admin/content/emfield, in the fieldset for the specific provider.

  30. 

  31. Questions can be directed to winborn at advomatic dot com