Posted by aaron on June 21, 2007 at 6:21pm
Embedded Media Field
44% (17 votes)
Embedded Social Media Field
10% (4 votes)
Media CCK
10% (4 votes)
Remote Media Field
26% (10 votes)
Remotely Embedded Media Field
8% (3 votes)
Social Media Field
0% (0 votes)
Other (Suggest name in comment)
3% (1 vote)
Total votes: 39
Comments
Since other modules may
Since other modules may embed local media, remote media seems like a better name. Unless this module provides an API for any module to embed media..
It does actually provide an
It does actually provide an API for any module to embed media via a system of hooks. From the core module's standpoint (or even the contributed modules), there's no reason that the actual file needs to be remote. There just needs to be a php include file that invokes the hooks and tells it where the file is and how to get it there. There have been conversations about using the single field to also upload files to be displayed. Ultimately, as Drupal's filesystem matures, I could envision it using a popup to browse the filesystem for files to embed.
Granted, all of that is out of the initial scope of what's being presented with this module, and begins to seem too much all-in-one, especially since there are already excellent solutions for embedding local media. However, I don't want to rule out options, particularly when I can see the use for something more integrated.
Aaron Winborn
Advomatic, Web Design for Progressive Advocacy, Grassroots Movements, and Really Cool Causes
Aaron Winborn
Drupal Multimedia (my book, available now!)
AaronWinborn.com
Advomatic
Agreed that the scope of
Agreed that the scope of this module should be limited for now. I am interested to see how this module if/can be integrated with existing modules like audio.module, at the same time, I don't see THAT much overlap. One CCK field that handles URL parsing, embedding, player options, file uploads, attaching existing files, and additional metadata storage would be a nightmare. There are just too many things to keep track of, and too many variations on how people would want to use it. I think keeping things as modular and small as possible will make it easier to understand and maintain, and make it easier to integrate/merge together down the road.
The only other name
I would give it a collective name like "embeded multimedia feild"
Embed Media field
The past tense of the word Embed is not as elegant or as descriptive as the present tense.
The reason to use the module is to Embed a Media Field. The result is an Embeded Media Field.
Can anyone think of a object in real life that is named after a past tense of a word?
BTW, I voted for "Embeded Media Field" ... with the change to present tense, it is a great name.
And thanks for writing the actual module!
I disagree. The reason to
I disagree. The reason to use the module isn't to Embed a Media Field. It is to have a field that supports embedded media. The field itself isn't embedded. Its just another field like any other CCK field.
We don't call the email field "Embed Email Field"
Remote social media CCK
With a focus on searchability and recognizability by newcomers, I submit that "remote social media CCK" might be the best overall name, combining the best of the other suggestions.
http://www.constitution.org
http://www.pynthan.com
http://www.constitution.org
http://www.pynthan.com
Couldn't you also...
You also be pulling from local sources and use this module.
And what, pray anyone on this thread tell, does embedded video and audio have to do with "Social" Media beyond the current trend of building Social Media sites with these capabilities?
Ok, last comment on this one... not calling you out personally Jon Roland, but your post is an excellent place in the thread to say something.
No offense, just saying. ;-)
Jonathan