Needs work
Project:
Embedded Media Field
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
25 Jul 2009 at 04:38 UTC
Updated:
25 Mar 2010 at 03:13 UTC
Jump to comment: Most recent file
Comments
Comment #1
vadbars@drupal.org commentedI wrote about my experiences here - http://groups.drupal.org/node/24621#comment-85175
Comment #2
bcn commentedHere is a patch that has even more cruft removed. Still needs some work, but it's ready to test.
Comment #3
bcn commentedUpdated patch... Mostly a cleanup, but also added the ability to have multiple waves embedded, either with multiple fields, or multiple items on a single field.
Since not many people have access to wavesandbox.com yet, it might make sense to first develop this at http://drupal.org/project/wave instead of committing code underneath the emfield project. One question this brings up is whether or not a emfield contrib module has to live inside
/emfield/contrib, or not?Comment #4
bcn commentedscreenshot
Comment #5
aaron commentedi would love to be able to review this, but google never responded to my request for a beta account some time back. anyone want to invite aaronwinborn@gm...? :P
Comment #6
bcn commented@arron:
Would love to send you an invite, but (AFAIK) google hasn't given anyone invites to give out... I know that starting tomorrow, they are moving all of us over from the sandbox domain to wave.google.com, and we /might/ have the ability to 'nominate' others. We'll see what happens...
There are some details at http://www.readwriteweb.com/archives/everything_you_need_to_know_about_t...
Comment #7
aaron commentedI have a google wave account, and went ahead and committed this module, since it's self-contained, just to get some more development eyes and interest on the project.
However, it currently only works for the Google Wave Sandbox, at https://www.google.com/a/wavesandbox.com/ServiceLogin and not the actual Google Wave at https://wave.google.com/wave/ -- I can easily modify the provider file accordingly, but don't see how to embed waves in the first place from its interface -- perhaps that's something that can only be accomplished from the sandbox?
Comment #8
aaron commentedmarking as needs work until we resolve the question re. embedding normal waves.
Comment #9
bcn commentedThanks Aaron for committing this.
1) As you mentioned, this is not working yet for wave.google.com embeds...
I see a few options here, i) change to allow for embeds from either sandbox or production servers (either by writing another provider .inc file, or a radio select in the field setting), or ii) change to allow embeds only from production (ie wave.google.com) servers.
2) Is it possible to have settings on a per embedded wave (and presumably per-node) basis?
It could be nice to be able change the wave look (color/size) on a per wave basis, or (dis)allow other wave embed api features on a per wave basis. Has this came up before, or how do other emfield modules deal with this?
3) How to build off, or coordinate with drupal.org/project/wave, and consider what other integrations/implementations (e.g. wave 'as a node-type' vs wave 'as a field') might make sense.
Comment #10
juliendorra commented@noahb and Aaron :
Wave is going to be used with many servers (that's why there is server name in the Wave ID : googlewave.com!w+7peNoPc-I for example) in the next months or so .
So a solution that can use the server name in the ID is probably more suitable.
It's probably not much of an issue right now... but we should keep that in mind anyway.
Comment #11
summit commentedSubscribing, greetings, Martijn
Comment #12
ck9 commentedHi can you very briefly describe what this does please? I'd like to create an intranet type site where project nodes have attached google waves, to which users can request being added.
Comment #13
dan.crouthamel commentedSubscribing -- so does this work with the production servers yet?
Comment #14
gausarts commentedSubscribing. Thanks