Closed (won't fix)
Project:
Drupal.org CVS applications
Component:
Miscellaneous
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
14 Oct 2009 at 19:17 UTC
Updated:
3 Dec 2009 at 05:16 UTC
Jump to comment: Most recent file
Comments
Comment #1
langecornu commentedThis is not ready to be released yet, it is a development Snapshot
Comment #2
avpadernoComment #3
avpadernoComment #4
avpadernoComment #5
langecornu commentedHi Kiam
What file are you referring to?
Comment #6
avpadernoProbably, also the other .php files are available from third-party sites too.
Comment #7
langecornu commentedNo I create the other .php file but i used this file created by Andrea Giammarchi and used with his permission, only this one was not made by me
I left his header only to give him credit on that class.
Andrea released this class under MIT License (http://www.opensource.org/licenses/mit-license.php)
Peraps, I should just remove the header in the file
Comment #8
langecornu commentedUpdated file
Comment #9
avpadernoRemoving the header doesn't change who is the author, or the fact the file is available from third-party sites.
Files licensed under a license different from GPL License v2+ should not be committed in Drupal.org CVS.
Comment #10
langecornu commentedMaybe I can make some modifications to the file since I am allowed to do so anyway under MIT Licence, I will submit a corrected version.
"Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so"
Comment #11
avpadernoYou can edit it, but you cannot change the license under which the file is released.
If then it would be just a question of editing a file, I could edit the files of the jQuery UI, and commit all of them.
The fact they are available from third-party sites doesn't change, even if I would edit them.
Comment #12
langecornu commentedI found another way to do it without using this class
Here is an updated version
Comment #13
langecornu commentedPlease keep in mind this is only a pre-alpha version, not yet ready to be released.
It will be thoroughly tested before releasing it.
Thank you again and have a good week end :)
Comment #14
avpadernoRemember to change the status, when you upload new code.
Comment #15
dave reidI would actually love to see a little collaboration between this and http://drupal.org/project/filefield considering FileField is now included in Drupal 7 core and is the module for uploading images/files/video.
Comment #16
langecornu commentedYes Dave, I am considering this already.
I just wanted to avoid having a dependency on another module in order to work to make it as broadly available as possible. The Release for version 7 will definitely use the filefield features.
Comment #17
langecornu commentedHere is also my first draft at the user guide that will accompany the module.
Comment #18
dave reidActually it looks like there is Divx support in http://drupal.org/project/video which seems to be quite active and supported. Also found documentation on how to migrate from Video to FileField with Divx support at http://drupal.org/node/298835.
At this point I'm leaning toward declining the application based on the fact that we want to encourage coordination and cooperation instead of duplication. I'll let someone else agree with me first before that decision is made however.
Comment #19
avpadernoI agree with Dave (how many times don't I agree with him?).
We tend to avoid duplication, and that is clearly stated on Apply for contributions CVS access.
Comment #20
langecornu commentedThis Drupal module will be part of a product we will release (We as DivX) which will include a drupal module, a wordpress plug-in and a joomla module. We really want to have a Drupal version in the pack, it would be very unfortunate if we cant.
Comment #21
dave reid@langecornu: Could you please try out the video.module and explain why and how your module is different then? We like to encourage cooperation and coordination instead of duplication. It's a big part of being a contributing member of our community.
Comment #22
avpadernoI am changing the status as per previous Dave's comment.
Comment #23
langecornu commentedI installed the video module to evaluate in what ways our module is different from that one.
First, I like to say , the video module is great, it offers a lot of possibilities and accept many formats.
The main difference is that we want to offer a module that is more mainstream than this one. We want to offer a plug-in that is very easy to install, to use and doesn’t have much 3rd party dependencies.
Our version not only support DivX file in AVI container but Also DivX Plus file (Matroska container).
We also offer the user to adjust all the available options specific to webplayer:
• Minimum version required to play the current media (example 2.0 is required to play mkv)
• Webplayer control type (or webplayer skin)
• Parameter to allow(or prevent) user of right clicking on the player(contextual menu)
• Multiple choice for the buffering mode of the player
• Enable(or disable) looping at the end of the playback
• Enable(or disable) auto playback
• Enable(or disable) the DivX ad Post plate at the end of the video
• Change the over lay message(and Fontsize) ex.: “Click Here to Start Playback”
If the user don’t change theses values, optimal default values will be used.
Unlike the video module, if FFMPEG is installed on the server, our module automatically generate a choice of 3 images thumbnails for the user to choose from.
We also want to make sure our module is easy to install/use so non experimented user can install it on their server, even if this is their first module. We never know, some user might even want to start using Drupal because this module enable them to publish their creation easily.
Here is our desired Flow for the installation.
Here is the flow for the current video module available from Drupal.org.
(If we target user that have minimal knowledge of the technology, they will have hard time to figure out what components are required or not in order of the module to work. Let say we use commonsense and we select(or try to select the followings: Video, URL Video, Upload Video, Video ffmpeg Helper, Video Image, Video Opt Metadata, Video Params)
Unfortunately, selection cannot be done because these components have dependencies on other modules. (For many non-experiences user this will be a show stopper), Let say we continue
Comment #24
langecornu commentedComment #25
avpadernoI am not saying that the application will be rejected, but it seems the case is the one reported in Apply for contributions CVS access.
Comment #26
langecornu commentedIt's not just because this module is simpler, But the fact that all features can be managed using this module such as:
• Minimum version required to play the current media (example 2.0 is required to play mkv)
• Webplayer control type (or webplayer skin)
• Parameter to allow(or prevent) user of right clicking on the player(contextual menu)
• Multiple choice for the buffering mode of the player
• Enable(or disable) looping at the end of the playback
• Enable(or disable) auto playback
• Enable(or disable) the DivX ad Post plate at the end of the video
• Change the over lay message(and Fontsize) ex.: “Click Here to Start Playback”
and also support the management and publishing of the DivX Plus File (.mkv)
As I mentioned before, the module will be offered for most used CMS System such as Drupal, Wordpress, Joomla etc.. and will offer all the same features for all of them and one of the key feature will be easy to install/use.
Thank you again :)
Comment #27
avpadernoIn your previous comment, you underlined the fact the users need to take more steps, in order to make the existing module working as they expect; this sounds like saying that the existing module is too complicated to be used from users, which is what Apply for contributions CVS access talks of.
Comment #28
avpadernoApart the code for defining new constants, the rest should be put in a Drupal hook (Drupal has a hook that can be used during initialization).
See the Drupal coding standards to understand how a module code should be written. In the coding standards there is a part about namespace respect.
Comment #29
langecornu commentedThank you for that, I am fixing some bugs now as I received some feedback from users that are testing the module, I will add this to my fixes :)
Comment #30
avpadernoThere have not been replies from the OP in the past 7 days. I am marking this report as .