Archive for November 2008
I know, I know, 7.04 is old now, but I still haven’t upgraded my laptop.
I tried the standard
$ sudo gem install sproutcore
but I had issues with nokogiri:
Install required dependency nokogiri? [Yn] Y
Select which gem to install for your platform (i486-linux)
1. nokogiri 1.0.6 (ruby)
2. nokogiri 1.0.6 (x86-mswin32-60)
3. nokogiri 1.0.5 (x86-mswin32-60)
4. nokogiri 1.0.5 (ruby)
5. Skip this gem
6. Cancel installation
Building native extensions. This could take a while...
ERROR: While executing gem ... (Gem::Installer::ExtensionBuildError)
ERROR: Failed to build gem native extension.
rake RUBYARCHDIR=/var/lib/gems/1.8/gems/nokogiri-1.0.6/lib RUBYLIBDIR=/var/lib/gems/1.8/gems/nokogiri-1.0.6/lib extension
Don't know how to build task 'extension'
I found some references to using `upgrade –system’ to upgrade the gem software components, but this didn’t work for me. Instead the following worked:
$ sudo gem update --system
This upgraded my gem installation, but it still needed this patch in order to run.
After all this the Sproutcore installation went smoothly.
I just got back yesterday from a trip out to Silicon Valley. Most of the trip was geared towards seeing some family and relaxing, but I checked around on meetup.com to see what kind of tech events I could crash during my trip. Well, it turns out that there was a meet up of the Sproutcore Founder’s Club during the time I’d be out there.
I first heard about Sproutcore after running into Mike Subelsky of OtherInbox at TwinTechII in DC, who sang its praises. Armed with an invite code from Mike, I checked out OtherInbox when I got back home after TwinTech. I must say, I was very curious to dig into Sproutcore a little after seeing what Mike and his team at OtherInbox had put together.
However, I didn’t end up having time to do much besides just installing Sproutcore (which is amazingly simple, and should bode well for its adoption), so I was excited to be able to get a good introduction from Charles Jolley, the Sproutcore man himself. Charles is an excellent speaker, and I really got a great feel for the direction that he is trying to take with the framework. If Charles gives this talk at a few big conferences I think that Sproutcore could really get a lot of mindshare.
I don’t have more time to go into things too deeply here, but I expect to be writing more on this soon.
I recently downloaded the Microsoft Oslo SDK in order to check out where MS is heading in the world of domain specific languages. Before I really even dug into the M compiler or any of the other actual bits of the Oslo technology, I saw something in the installation called Intellipad. I fired it up and was presented with a simple editor like notepad, but looking like it was actually from this decade rather than stuck in the early nineties.
The main differences from notepad seem to be that the open documents were in `buffers’ ala Emacs, and you could split the view up horizontally or vertically. I never really use the split functionality in any of the other editors that I have, so this wasn’t really that interesting to me. The question I still had in my mind was, why on earth would Microsoft ship a simple text editor in an SDK that is purportedly for developing domain specific languages? Fortunately there is a small document in the SDK installation that gives you an overview. It turns out that the reason for its apparent simplicity is that it is intended to be easily extensible. Imagine that, a MS tool that is designed to be hackable.
I haven’t tried to extend it yet, but it looks like there are several ways to get it done. You can write a module using any .net language and plug it in, or you can actually script it in python. I’ll be sure to post something once I’ve gotten a chance to do some hacking on this.