Adventures with Chumby
Listing 1. Sample profile.xml File
<profile> <widget_instances> <widget_instance id="1"> <widget> <name>Breads</name> <description>Various bread recipes.</description> <version>1.0</version> <mode time="180" mode="timeout"/> <access sendable="false" deleteable="false" access="private" virtualable="false"/> <user username="myusername"/> <thumbnail href="file:////mnt/usb/breads.jpg" contenttype="image/jpeg"/> <movie href="file:////mnt/usb/breads.swf" contenttype="application/x-shockwave-flash"/> </widget> </widget_instance> <widget_instance id="2"> <widget> <name>Cookies</name> <description>Various cookie recipes.</description> <version>1.0</version> <mode time="180" mode="timeout"/> <access sendable="false" deleteable="false" access="private" virtualable="false"/> <user username="myusername"/> <thumbnail href="file:////mnt/usb/cookies.jpg" contenttype="image/jpeg"/> <movie href="file:////mnt/usb/cookies.swf" contenttype="application/x-shockwave-flash"/> </widget> </widget_instance> </widget_instances> </profile>
I haven't been able to get all the things I wanted to get onto the Chumby onto it. However, after actually using the Chumby for a couple weeks, I'm not so sure they were good ideas to begin with.
The main reason for this is that my intended recipe search, shopping list creator and meal planning widgets all would require extensive text input, and that is where the Chumby is not ideal. The Chumby is mainly an output device, suited to displaying various bits of information. Input is best limited to simple interactions, such as tapping on buttons and sliding your finger around the screen.
The Chumby can handle text input, and some widgets require it. The control panel, for example, has a simple on-screen keyboard where you enter in your wireless settings during the Chumby's initial setup. Also, in the music interface, there is another on-screen keyboard where you enter in the location of the music stream to which you want to connect. But, supporting text input where required and doing a lot of text input are two very different things.
After entering text in just those two above-mentioned places, I could see it was not something I would want to do on a regular basis with the Chumby, because although it works, it's slow. The problem is that when using the Chumby, the natural thing to do is to use your fingers, and most widgets—if they have buttons at all—keep them large and few in number. For effective text input, you need a lot of small buttons, and on the Chumby's screen, lots of small buttons practically requires you to use a stylus—not something I want to have to use with the Chumby.
I toyed around with using an RSS widget to display recipe data from sites that offer it, such as Taste-of-Home's Recipe of the Day, but as you can see from the screenshot, my testing did not go so well.
The Chumby is an amazing device. It can be adapted to fit in with almost any room in the house and can display any sort of data that can be displayed within the confines of the Flash file format.
New widgets come out all the time, and the basic software is under constant improvement. Check out chumby.com and browse the available widgets; there's something for everyone.
The Chumby is also very hackable. The underlying operating system is embedded Linux, and all the source code (apart from a few licensed bits that they aren't allowed to disclose) and complete hardware schematics are available on the Chumby Web site. The developers really seem to get the idea of making a device hackable, with their only warning being a gentle reminder that if you take your Chumby apart, it will void the warranty. Beyond that, they actively encourage you to turn the Chumby into anything you please and are eager to help you in any way they can through their Web site, forums and wiki.
In these days of locked-down, don't-you-dare-look-behind-the-curtain-or-we'll-sue gadgets, having one that you can mod to your heart's content, with full schematics and source code—and the original developers—to guide you, is a nice feeling.
|Designing Electronics with Linux||May 22, 2013|
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
- Designing Electronics with Linux
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Dynamic DNS—an Object Lesson in Problem Solving
- New Products
- Using Salt Stack and Vagrant for Drupal Development
- Validate an E-Mail Address with PHP, the Right Way
- Build a Skype Server for Your Home Phone System
- A Topic for Discussion - Open Source Feature-Richness?
- Tech Tip: Really Simple HTTP Server with Python
- Why Python?
- Not free anymore
2 hours 7 min ago
5 hours 55 min ago
- Reply to comment | Linux Journal
6 hours 3 min ago
- Understanding the Linux Kernel
8 hours 17 min ago
10 hours 47 min ago
- Kernel Problem
20 hours 50 min ago
- BASH script to log IPs on public web server
1 day 1 hour ago
1 day 4 hours ago
- Reply to comment | Linux Journal
1 day 5 hours ago
- All the articles you talked
1 day 7 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?