Closed (fixed)
Project:
Drupal.org CVS applications
Component:
new project application
Priority:
Normal
Category:
Task
Assigned:
Issue tags:
Reporter:
Created:
29 Jan 2010 at 04:44 UTC
Updated:
16 Apr 2023 at 18:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
xmacinfoAs requested, a compressed version of the module.
Comment #2
avpadernoComment #3
xmacinfo@kiamlaluno: Your post was empty. Did I forgot something? Thanks.
Comment #4
avpaderno@xmacinfo: No, you didn't. I simply added the review tags; that is why my comment appears empty.
Comment #5
beeradb commentedHave you filed a patch for emfield? out of the box it already has support for a ton of providers, it would seem this functionality would work best as a patch to that module.
Comment #6
xmacinfoI will ask them.
However there are two reasons an independent module would be preferable.
1. They (emfield) provide an API that allows other third party video providers to be supported using simple include files and provided hooks.
2. The megavideo module is an example of an independent module using the emfield API. http://drupal.org/project/media_megavideo
Comment #7
xmacinfoIssue opened at #704128: Integration of a new video provide TagTele.
Comment #8
avpadernoThere have not been replies from the OP in the past 7 days. I am marking this report as .
Comment #9
xmacinfoWhat is OP?
Comment #10
avpadernoOP means original poster, which is you.
I forgot to set the status of this report as per my previous comment.
Comment #11
xmacinfoI did post an issue to the emfield issue queue and I got no response.
However I still think that we need to be able to post plug ins since emfield provides an API to do so. Please see my comment on #6.
Currently Drupal.org is hosting more than twelve emfield plug ins:
http://drupal.org/project/media_viddler
http://drupal.org/project/media_megavideo
http://drupal.org/project/media_hulu
http://drupal.org/project/media_flickr
http://drupal.org/project/media_brightcove
http://drupal.org/project/media_videojug
http://drupal.org/project/media_youku
http://drupal.org/project/media_smugmug
http://drupal.org/project/media_screencast
http://drupal.org/project/media_archive
http://drupal.org/project/media_8tracks
http://drupal.org/project/media_brightcove
and more...
My request is to add at least one more, which is TagTélé.
So if there are already more than 12 emfield plug ins on Drupal.org, why not let me add more?
Comment #12
avpadernoThe CVS application was closed because it didn't get any feedback.
Considering that the maintainer of Embedded Media Field is creating some projects for the integration between Embedded Media Field and media providers, I think it doesn't create any problem to have also this project hosted on Drupal.org.
Comment #13
xmacinfoFair enough.
Actually, there are more than 5 maintainers for the various media providers projects hosted on Drupal.org, this in addition to the main emfield maintainers.
Is there anything else I need to do to get this forward?
I am looking forward to add more media providers, TagTélé being the first one maintained by me.
Comment #14
xmacinfoStill waiting for approval.
Media module and Emfield module are moving away from integrated media providers. Media providers are instead released by various maintainers separately for both emfield (D6) and the new Media module (D7).
I will create the D7 version of my media provider module.
Comment #15
aaron commentedYikes!
Sorry to take so long to reply here; ticket ended up dropping below my radar.
The Embedded Media Module is now in the process of dropping all its providers, in favor of providers being supported external to the module. The Media module has already done this (which will be the successor to emfield). That's because it's a real pain to hold up releases because some rinky-dink provider changes their API, and to encourage more developers to help maintain the sucker.
I haven't reviewed the code yet, but I plan to today.
Thanks,
Aaron
Comment #16
avpadernoFunction names, constants, and Drupal variable names should be prefixed by the module name; the module name is media_tagtele.module, then the function names need to start with media_tagtele_, the constant names must start with MEDIA_TAGTELE_, and Drupal variable names need to start with media_tagtele_ (when the variable is the one defined from the module, not when the variable is defined from another module, and used from the proposed module).
The license file must be removed, as it is not possible to commit such files.
Comment #17
aaron commentedThe module works as advertised, and the code is clean. A few misc comments (not blockers, but things that should probably be addressed before a release).
* The README needs to wrap at 80 characters.
* Not sure about the
// TagTélé feature has been created by xmacinfo(http://drupal.org/user/12131)comment in the module; at the least it should be in the /** section, and more likely in the README.* The provider does not support thumbnails, and considering from my experience, that's the number one issue with various providers in the queues, you should at the very least mention that in the $features of emvideo_tagtele_info().
I looked a bit into the thumbnail issue, and found that it *appears* there may be a standard format for image urls: for instance, the thumbnail for http://www.tagtele.com/videos/voir/52415 currently resides at http://s1.ttimg.com/img/videos/thumbs192x108/52415_default.jpg?201002251.... I'm not certain if the thumbnail server farm changes periodically (it often does with other providers), but if with testing this turns out not to be the case, you could implement something like:
Alas, it probably won't be so simple. I hunted around for an API, but couldn't find one easily. Might be worth contacting them; I've found in the past that most providers (other than YouTube) have been responsive to requests.
In any case, these issues are minor and easily resolved, so I'll mark this RTBC.
Thanks,
Aaron
Comment #18
aaron commentedSorry kiamlaluno, didn't mean to cross-post.
In the .inc file, unfortunately, the current API for emfield breaks the rules (due to legacy) for function names. Thus, we have things like hook emvideo_PROVIDER_info, where the emvideo_ trumps the usual rule. Sorry about that; it's addressed in the Media module.
Perhaps you'd like to wait for a d7 version to review? xmacinfo indicated an upcoming version for that?
Comment #19
aaron commentedah yes, the LICENSE.txt file (as has been pointed out) needs to be dropped, as do the following in the .info file, which will be added by the packager:
version = "6.x-1.0"
project = media_tagtele
Comment #20
avpadernoIt would also be enough that the module file is renamed to emvideo_tagtele.module. The file for new module would have then a different name.
Comment #21
xmacinfoThanks for all the comments.
I will submit a new version for emvideo D6 in the next few days for review. Hopefully by Saturday.
As for media D7, I plan to do it, but not in short term.
Comment #22
xmacinfoI tried to rename the module to "emvideo_tagtele.module", to no avail. Looks like emvideo does not discover the module, even tough it's properly enabled. So I switched back to "media_tagtele.module".
I am currently investigating the $features supported by TagTélé. But the features are currently very limited. So I may indeed do a version that do not support thumbnails and mention it in the info part.
Not ready for a review yet. :-)
Comment #23
avpadernoThere have not been replies in the last week. I am marking this application as .
Comment #24
xmacinfoGive me some more time. :-)
Comment #25
xmacinfoHere is a new version of the module for review.
I am already using this module in production on two web sites and there are no issue reported.
Comment #26
xmacinfoStill waiting for a review. :-)
Comment #27
aaron commentedThis looks great to me. The issues w/ emvideo naming will be addressed in v2 of emfield, but for now, see #18 and #22 for the reasons for the function names; that's a mistake of the legacy emfield api, not of xmacinfo.
Comment #28
avpadernoComment #31
avpaderno