tag:blogger.com,1999:blog-58832847584321539192008-06-10T10:35:20.392-05:00Ryan Gahlhttp://www.blogger.com/profile/07296413923778231728noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-5883284758432153919.post-63487559113246946442008-05-08T10:04:00.009-05:002008-05-08T17:07:05.756-05:00

Darwin noted that it was not the strongest species to survive, but the most adaptable. This proves true in nature as it does in the software arena. Software, for the most part, becomes isolated on a single client after an invasive installation process. Having the application solely based on a single system leads to many inherent issues with data that is collaborative in nature, such as a

Matthttp://www.blogger.com/profile/00527875141925548098noreply@blogger.comtag:blogger.com,1999:blog-5883284758432153919.post-28415879924754936112007-09-06T23:19:00.001-05:002007-09-07T17:45:25.644-05:00

When demonstrating our widget platform (WebWidgetry(tm) and MashupStudio(tm)), one of the first things most people ask me is, "what do you guys view as the definition of 'widget'?" In another post of mine (Widgets are Applications without Boundaries), I offer a couple of very quick and dirty rules to answer that question. Here I will dive (however briefly) into one of those qualifiers while

Ryan Gahlhttp://www.blogger.com/profile/07296413923778231728noreply@blogger.comtag:blogger.com,1999:blog-5883284758432153919.post-29313775546616327012007-07-11T10:29:00.001-05:002007-07-13T17:25:53.214-05:00

There is a line between what is a widget and what is not a widget. That line, however, is not drawn in the sand - that is, it depends on who you ask. Some people will say that a widget is a little piece of code that you can embed in your website and nothing more (a novelty at best), or that can be virally propagated, or is a read-only view into some combination of interesting data. To me (and my

Ryan Gahlhttp://www.blogger.com/profile/07296413923778231728noreply@blogger.com