A cool feature of the Smart Space SDK is the ability to create a set of global Smart Space variables that can be used by any gadget. These are essentially name value pairs that are called LocalProperties in Smart Space.
I came across an article in Hemispheres Magazine (UAL publication) about this time last year. The article was about cycling, and last February I was just getting back into cycling after a long break from it, so I was intrigued. Aside from getting back into cycling I was also buried in everything Smart Space attempting to build and launch this new product. I was shocked how much this article related what I was doing in software to what Shimano was planning to do for cycling.
When talking to people about Smart Space I hear this question come up all the time. I have found that most people have very different views on this topic so take what I have to offer as merely another opinion. In my earlier post I talked about the definition of a gadget and stated the following:
In my last post, I talked about how the messaging capabilities contained within the Smart Space product can be leveraged in non-traditional ways. One of the best ways is by using the Smart Space Java API.
One of the cool things about using Smart Space is that you immediately become a part of the community of Smart Space users. You get this for free because the Smart Space client has built in messaging capabilities.
This opens up a wealth of opportunities for one to communicate with other Smart Space users in both traditional and non-traditional ways.
Whenever I start a new development endeavor I almost always look to sample code to get started, and it is even better if it is a simple sample. So with that I will attempt to give you my version of a ‘Hello World’ sample for Smart Space gadgets. Changing things up a bit I will make this a notepad sample as this is pretty common in the Gadget/Widget world.
Smart Space is a radical departure from the traditional BI/EPM application. For years the BI/EPM market has been focused on providing more and more features. These features are added to backend services bringing us to the ‘system’ we have today. However most of these features are simply added to existing user interfaces. Over time these interfaces, though packed with features, have become difficult to use, underperforming and nearly impossible to customize.
I hear these terms a lot now a days when talking about software, and just a year or so ago I would of thought a widget was a generic term for a product and a gadget was some new electronic device. Not anymore, these terms have quickly taken on new meaning and have a place in the world of delivering information. The bad thing about these terms is that everyone uses them a little different and there are already variations on the terms.