modules/video_upload/TODO.txt

$Id: TODO.txt,v 1.5.2.2 2008/12/31 22:05:06 jhedstrom Exp $

List of to-do items for the video_upload module, in no particular order.
@todo tags can also be found distributed througout the code.

* Completely abstract out the Zend Gdata library so that this module
  could use the Drupal Youtube API module. The reason for this is that
  the Zend library requires modification of the PHP include_path
  variable, which can be hard for shared-hosting sites.

* Abstract out the YouTube specificity, so that this logic could apply
  to other providers. This work has been started by moving most
  YouTube logic into the providers directory. There is still a lot
  left to do though.

* Get the Browser Upload method working with 6.x

* Make a 2 step form? Not sure if this is better. The advantages:
   - Collect all relevant info prior to submitting data to youtube
  The disadvantages:
   - it's a 2-step form, not sure how that would work with all CCK scenarios

* Allow for multiple YouTube accounts per site (or per field instance,
  etc).  The YouTube API limits uploads on accounts with more than
  1000 videos:

  http://code.google.com/apis/youtube/developers_guide_protocol.html#Uploading_Videos

* Handle the selection of which thumbnail to use: YouTube provides 3
  thumbnails, which the user should be able to select from.

* The description that is sent/synchronized on YouTube should be able
  to pull from fields other than node->body. This should be
  configurable.

* When configuring a field, any known vocabularies should be presented
  as options for YouTube keywords

* Extend token support
1	$Id: TODO.txt,v 1.5.2.2 2008/12/31 22:05:06 jhedstrom Exp $
2
3	List of to-do items for the video_upload module, in no particular order.
4	@todo tags can also be found distributed througout the code.
5
6	* Completely abstract out the Zend Gdata library so that this module
7	could use the Drupal Youtube API module. The reason for this is that
8	the Zend library requires modification of the PHP include_path
9	variable, which can be hard for shared-hosting sites.
10
11	* Abstract out the YouTube specificity, so that this logic could apply
12	to other providers. This work has been started by moving most
13	YouTube logic into the providers directory. There is still a lot
14	left to do though.
15
16	* Get the Browser Upload method working with 6.x
17
18	* Make a 2 step form? Not sure if this is better. The advantages:
19	- Collect all relevant info prior to submitting data to youtube
20	The disadvantages:
21	- it's a 2-step form, not sure how that would work with all CCK scenarios
22
23	* Allow for multiple YouTube accounts per site (or per field instance,
24	etc). The YouTube API limits uploads on accounts with more than
25	1000 videos:
26
27	http://code.google.com/apis/youtube/developers_guide_protocol.html#Uploading_Videos
28
29	* Handle the selection of which thumbnail to use: YouTube provides 3
30	thumbnails, which the user should be able to select from.
31
32	* The description that is sent/synchronized on YouTube should be able
33	to pull from fields other than node->body. This should be
34	configurable.
35
36	* When configuring a field, any known vocabularies should be presented
37	as options for YouTube keywords
38
39	* Extend token support