mobile | mac | business | development blog
Finally the video stream of Steve Jobs iPhone 4 & iOS 4 keynote at the WWDC 2010 is online now. So tune in to watch his performance.
Again, it’s keynote time: The sold out Worldwide Developer Conference 2010 – WWDC10 – is about to begin. At 10:00 PST Steve Jobs will be on stage. Developers, fans and all others who are interested in Apple’s business development will be hypnotized of Apple CEO Steve Jobs. Millions of people are sitting at their computers, iPhones, iPads or other mobile devices and want to know instantly what Steve is presenting today.
It’s really fascinating how Steve plays with the masses … so it does not surprise too much, that the big German news magazine Spiegel Online refers to the event as an “Californian worship”. That’s not how I would describe it … but it shows how hard it is to understand and describe that keynote phenomenon. Just thnik about the “viewing rates” or reach of a presentation of Olli-Pekka Kallasvuo (Nokia CEO), Jim Balsillie (Research In Motion co CEO) or even Eric Schmidt (Google CEO).
What will present us today … nobody really knows. But there is a lot of rumor out there: The iPhone HD or 4G? A sneak preview of the next Mac OS X version? New Mac hardware? … the first photos from the Moscone West Center suggest that it’s all about apps … maybe a Mac AppStore
Some weeks ago, a developer wrote a provocative email to Steve, whether he will counter Apples competitors like Google/Android. Steve’s short reply was “You won’t be disappointed!”.
So the expectations are high … and for all of us, who are not able to attend the Steve Jobs show at the Moscone West Center in San Francisco live: Here are some of the most important live coverage blogs for the WWDC keynote 2010:
As soon as the video of the keynote is available as a Quicktime stream … you’ll get an update
Yesterday, Steve Jobs presented the next iPhone OS generation to the developer community as well as to the interested public. Now, iPhone developers have access to experiment with iPhone OS 4 SDK and can optimize their apps for the new operating system. This summer, Apple will roll out the new OS to iPhone- and iPod-touch-users. This fall iPhone OS 4 will also be available for the iPad.
It’s quite obvious, why Apple is revealing the next version of their mobile OS now: The app developers need to implement the new features – like multitasking – to their apps … only if they do so, the iPhone OS 4 will be a success. But, calm down, Steve Ballmer: It will be a success
This is a quick overview over the 7 tentpole features, Steve Jobs and Scott Forstall (Senior Vice President iPhone Software) presented at the event (Quicktime-Video-on-Demand of the event):
Again, Apple achieved to integrate a bundle of innovations into the next iPhone generation … very good news for the growing number of iPhone-developers. Other players in the mobile industry, like Google’s AdMob, have to expect heavy seas ahead. This leads me to one of these wonderful Bob Dylan songs: “The times they are a changing …”
Happy Valentine’s day 2010!
Last year, 30 German iPhone developers joint their forces and reduced their app prices to the max to make you smile on Valentine’s day … this year everything is bigger: Now more than 80 apps are reduced to the max to please our customers.
CompareMe shopping utility is also available for $0.99. So check out AppsForSale.de maybeyou’ll find a real bargain. Only on 14.02.2010!
I had a lot of trouble with some rubygem warnings after upgrading to Ruby 1.9.1 and Rails 3.0 on Mac OS x Snow Leopard. They always occurred when I started the server within the project with the command
At first, when running on bundler 0.9.3, I had two types of errors. The first NoMethodError populated the terminal with hundreds lines of code, like …
WARNING: # NoMethodError: undefined method ` ' for nil:NilClass # -*- encoding: utf-8 -*- ... WARNING: Invalid .gemspec format in \ '.rvm/gems/ruby-1.9.1-p378/specifications/spec.gemspec'
The bundler-team around Carlhuda fixed that issue within bundler 0.9.4. So that problem will not occur any more.
The other problem was quite persistent. When starting the server via
or doing a test via
within the rails-3-project resulted in a bunch of warnings:
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems.rb:14: \ warning: already initialized constant VERSION /usr/local/lib/ruby/site_ruby/1.9.1/rubygems.rb:14: \ warning: already initialized constant RubyGemsVersion /usr/local/lib/ruby/site_ruby/1.9.1/rubygems.rb:194: \ warning: already initialized constant MUTEX /usr/local/lib/ruby/site_ruby/1.9.1/rubygems.rb:196: \ warning: already initialized constant RubyGemsPackageVersion /usr/local/lib/ruby/site_ruby/1.9.1/rubygems.rb:202: \ warning: already initialized constant WIN_PATTERNS /usr/local/lib/ruby/site_ruby/1.9.1/rubygems.rb:1079:\ warning: already initialized constant MARSHAL_SPEC_DIR /usr/local/lib/ruby/site_ruby/1.9.1/rubygems.rb:1084: \ warning: already initialized constant YAML_SPEC_DIR /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/version.rb:72: \ warning: already initialized constant VERSION_PATTERN /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/requirement.rb:20: \ warning: already initialized constant OPS /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/requirement.rb:30: \ warning: already initialized constant OP_RE /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/version.rb:246: \ warning: already initialized constant Requirement /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:18: \ warning: already initialized constant TYPES /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/platform.rb:171: \ warning: already initialized constant RUBY /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/platform.rb:177: \ warning: already initialized constant CURRENT /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:39: \ warning: already initialized constant NONEXISTENT_SPECIFICATION_VERSION /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:50: \ warning: already initialized constant CURRENT_SPECIFICATION_VERSION /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:56: \ warning: already initialized constant SPECIFICATION_VERSION_HISTORY /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:72: \ warning: already initialized constant MARSHAL_FIELDS /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:75: \ warning: already initialized constant TODAY /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/source_index.rb:593: \ warning: already initialized constant Cache /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/config_file.rb:14: \ warning: already initialized constant DEFAULT_BACKTRACE /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/config_file.rb:15: \ warning: already initialized constant DEFAULT_BENCHMARK /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/config_file.rb:16: \ warning: already initialized constant DEFAULT_BULK_THRESHOLD /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/config_file.rb:17: \ warning: already initialized constant DEFAULT_VERBOSITY /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/config_file.rb:18: \ warning: already initialized constant DEFAULT_UPDATE_SOURCES /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/config_file.rb:24: \ warning: already initialized constant OPERATING_SYSTEM_DEFAULTS /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/config_file.rb:30: \ warning: already initialized constant PLATFORM_DEFAULTS /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/config_file.rb:53: \ warning: already initialized constant SYSTEM_WIDE_CONFIG_FILE
Jeremy Kemper from the Rails core team pointed out that this is not a Rails problem, but a RubyGems issue. Ruby 1.9 ships with an outdated RubyGems … like 1.9.1p378 ships with RubyGems 1.3.1. I did update RubyGems to Version 1.3.5 by
sudo gem update --system
but this resulted in some duplicated rubygem files, which cause the error.
So how can the problem be solved? Deleting and reinstalling Ruby 1.9.1 does not have any effect … but the solution is quite simple:
1. Be sure that you do NOT install RubyGems 1.3.5 separately after the installation of Ruby 1.9.1 – this would result in a double installation. So have that in mind when following the excellent instructions to installing Ruby, RubyGems, and Rails on Snow Leopard of Dan Benjamin.
2. If you already installed Ruby 1.9.1, updated to RubyGems 1.3.5 and bundler 0.9.4 and also installed Rails 3.0, the only thing you have to do is:
sudo gem uninstall rubygems-update
That’s it. No errors any more!
1. You may start with Dan Benjamin’s recipe and modify it so you download, make and install the ruby-1.9.1-p378.tar.gz but NOT the rubygems-1.3.5.tgz.
2. Then update RubyGems with the command
sudo gem update --system
3. Ensure that the rake and the sqlite3-ruby gems are installed, too.
4. Now install the needed gems and rails –pre as described in the Rails 3.0 beta release notes
5. After the successful installation of Rails 3.0 beta, you now have to do the vitally important step:
sudo gem uninstall rubygems-update
6. Finally check, if any gem needs an update before diving into Rails 3.0 by
sudo gem update
Hope this helps … and saves some time. Thx Andy for the hint