Closed (fixed)
Project:
Ooyala
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
8 Nov 2010 at 22:33 UTC
Updated:
27 Dec 2010 at 04:40 UTC
Jump to comment: Most recent file
Comments
Comment #1
quicksketchThis looks like great functionality to add to the Ooyala project. The code looks pretty good, (certainly good enough for an initial commit), but I think it'd make sense to make an "Ooyala" package section on the modules page if we're going to start bundling multiple modules in the Ooyala project. Especially considering potential future enhancements that will likely be in separate modules too, like the "Ooyala channels" module we may eventually put together for creating channels.
Comment #2
eojthebraveFYI, I haven't actually tested this against ooyala.module in CVS yet. This was written against my mega-hacked version of the module since I couldn't wait for all the patches that this required to go in. Those patches are all in now, and this should work no problem. I would like to test it with ooyala.module from CVS before it gets committed though just as a sanity check.
I should be able to do so in the next day or two.
Comment #3
sirkitree commentedOk, I can certainly see the benefits of that. Marking as needs work then.
Comment #4
quicksketchI've made a few minor revisions to the code including:
- Missing semi-colons in the JS file.
- Changing the package name.
- Moving the README.txt information into the Ooyala module README.txt, so that way people have a single location for reading about the bundled modules.
I tested all the code and functionality and it works fantastic. Great work guys!