more brain > blog.html

Hi, just curious -- why did you choose to use constants to identify categories? This is precisely what Symbols help the Ruby world avoid. :)

Jay- Great question. I find constants rather ugly myself. The reason I didn't use symbols is because I believe they are most useful when the value of the symbol is the same as the name. If I make a category a symbol, such as :music, I would still have to map :music to the category id of 10, which is the numerical value that has to be sent to YouTube. I can't create the symbol :10 and it wouldn't make much sense. Constants are more generally used in the case where you need to map something to a specific numerical value. I may still change to symbols for readability though. They'll definitely make more sense if I could change the numerical value of a symbol and call to_i on it. Do you think symbols are better when they are meant to represent a different value from the symbol name? For the 0.9 version I'm envisioning having a catch all videos_by method, similar to ActiveRecord find, using symbols for named arguments, like, i.e:

videos_by(:category => :music, :tag => 'tiger honey pot')

videos_by(:user => 'matz')

Since this is a bugfix release, I didn't want to make any API changes.

I didn't know about it, it really makes using their service much easier. Thanks for information!

Well done bro! You're well on your way to living yyour life your way. Kudos! Much respect.

shane: I sent over a patch via email on Monday and a description of what I've changed. Did you receive this?

Daniel- Nope. Didn't receive it. Can you send it again? My email is in the About me page. Thanks!

shane: I re-forwarded the email! Not sure why you didn't get the first one, double-checked the email and everything looked good. Although, Gmail was acting funky that day.

Daniel- I got it this time. I'll take a look. Thanks for the contribution!

In my situation everything works great! I had some problems untill I found this blog. So thanks a lot!

Your gem is great. Thanks!

The only feature I was missing was the total number of available videos when you get the search results page by page. I extracted the value the following way:

def _parse_video_response(response)
  videos = response'video_list'
  @total = response'video_list'.to_i  #<<<<<<<
  videos = videos.is_a?(Array) ? videos.compact.map { |video| Video.new(video) } : nil        
end

Thanks, the gem is very nice. I added the following code in the library to retrieve the popular videos:

1. Returns a list of YouTube::Video objects
2. The time_range to list by (e.g. ‘day’, ‘week’, ‘month’, ‘all’) def popular_videos(time_range) response = videos_list_popular(:time_range => time_range) _parse_video_response(response) end

Just in case anybody needs it. As an example: videos = youtube.popular_videos(‘day’) videos.each { |video| print video.author }

Just wanted to say thank for this gem, it’s great, easy to use, works like a charm. We just implemented it at http://www.mtraks.com, under Artist pages you can now view relevant videos under the ‘videos’ tab.

One suggestion for the ‘videos_by_category_and_tag’ method. Would you (or maybe you already have) be able to have the video objects use the ‘embed_status’ attribute like the ‘video_details’ method uses? I would be really helpful to be able to request of bunch of videos then only embed the ones that are in fact embeddable. Right now I have to make a call to ‘videos_by_category_and_tag’ then a call to ‘video_details’ for each video. The YouTube API website says that ‘videos_by_category_and_tag’ does return the embed_status attribute.

Cool. thanks again!

Hi there, super fantastic plugin. But I have one issue—when including the YouTube gem into my Rails app, I get the following output when starting my server:

/usr/local/lib/ruby/gems/1.8/gems/xml-simple-1.0.11/lib/xmlsimple.rb:275: warning: already initialized constant KNOWN_OPTIONS /usr/local/lib/ruby/gems/1.8/gems/xml-simple-1.0.11/lib/xmlsimple.rb:280: warning: already initialized constant DEF_KEY_ATTRIBUTES /usr/local/lib/ruby/gems/1.8/gems/xml-simple-1.0.11/lib/xmlsimple.rb:281: warning: already initialized constant DEF_ROOT_NAME /usr/local/lib/ruby/gems/1.8/gems/xml-simple-1.0.11/lib/xmlsimple.rb:282: warning: already initialized constant DEF_CONTENT_KEY /usr/local/lib/ruby/gems/1.8/gems/xml-simple-1.0.11/lib/xmlsimple.rb:283: warning: already initialized constant DEF_XML_DECLARATION /usr/local/lib/ruby/gems/1.8/gems/xml-simple-1.0.11/lib/xmlsimple.rb:284: warning: already initialized constant DEF_ANONYMOUS_TAG /usr/local/lib/ruby/gems/1.8/gems/xml-simple-1.0.11/lib/xmlsimple.rb:285: warning: already initialized constant DEF_FORCE_ARRAY /usr/local/lib/ruby/gems/1.8/gems/xml-simple-1.0.11/lib/xmlsimple.rb:286: warning: already initialized constant DEF_INDENTATION /usr/local/lib/ruby/gems/1.8/gems/xml-simple-1.0.11/lib/xmlsimple.rb:287: warning: already initialized constant DEF_KEY_TO_SYMBOL

The xml-simple FAQ - http://xml-simple.rubyforge.org/ - indicates that the XmlSimple library is already included in Rails, but has a non-standard file name, such that other requires of the plugin will reload it, redefining all the constants. The FAQ suggests that if you’re going to use XmlSimple in a Rails app, you ought to only require the library if the XmlSimple const has not already been defined.

I know this isn’t a YouTube gem bug, but would you mind making this minor change so that those of us using Rails apps don’t see these warning messages over & over?

Many thanks,

Michael

This gem is great! I used it on my Alarm Clock/YouTube mashup with no problems. Thanks for your hard work.

AlarmTube

—Tim

He filledher lil kim porn with his fist into my straight face for. I guess lil kim exposed i found that she was real.

jenny mccarthy gallery

sonya walger nude

candice michelle nude

tara reid breast

megan fox fhm

lena headey nude