Creating a Connection to an XML Feed
April 23rd, 2009
Comments
In this next screencast in the series, we present a overview on how to create a connection, to an XML Feed:
|
|
|
|
|
|
|
|
Archive
Posts Tagged ‘Connector’
Google Map from RSS Feed
April 5th, 2009
Comments
Here we present a screencast demonstrating the steps you would go through to create a Google Map from an RSS feed, as was described in the post “Fun With Google Maps“:
|
|
|
|
|
|
|
|
|
Categories: Screencasts Bluyah, Connection, Connector, Google, Google Maps, Map, RSS, RSS Feed, Screencasts, Tutorials, Video
Creating a Google Docs Connector
April 3rd, 2009
Comments
In the first of an ongoing series, we present a screencast describing how to create a Google Docs Connector:
|
|
|
|
|
|
|
|
|
Categories: Screencasts Bluyah, Connection, Connector, Google, Google Docs, Screencasts, Tutorials, Video
The Problem with XML
March 16th, 2009
Comments
We’ve been working laboriously on a new connector type for Bluyah: XML. On the surface, this seems like a very simple nut to crack - we’re already parsing RSS and ATOM feeds, both of which are XML-based. But the truth of the matter is, it’s becoming more complex the deeper we dig into it.
The problem is in the XML format itself. XML can be anything it’s author wants it to be. It’s self-describing, sure. But it’s not pre-defined. In other words, there is nothing within the structure or definition itself to tell you that in the following snippet, the ‘row’ element should be treated as the rows of data to be reported upon, with the sub-elements to be treated as ‘column’ data:
<report>
<head>
<title>Fremont Pizza Parlors</title>
<records_found>2</records>
<metadata>
<parlor length="32" source="name">Parlor</parlor>
<street length="64" source="street">Address</street>
<city length="64" source="city" />
<state length="2" source="st" />
<zip length="9" source="zip_code" />
<phone length="10" source="telephone" />
</metadata>
</head>
<data>
<row>
<parlor>Piecora's New York Pizza</parlor>
<street>1401 E Madison St</street>
<city>Seattle</city>
<state>WA</state>
<zip>98102</zip>
<phone>(206) 322-9411</phone>
</row>
<row>
<parlor>Pagliacci Pizza</parlor>
<street>426 Broadway E</street>
<city>Seattle</city>
<state>WA</state>
<zip>98102</zip>
<phone>(206) 726-1717</phone>
</row>
</data>
</report>
As you can see from the above sample, the data we want to loop over for reporting is contained within the ‘data’ element and that the ‘row’ elements are aptly named ‘row’. But what if they were named ‘places_i_like’? And what if they were parallel to the ‘head’ element? How could an application know this without human intervention?
Well … we think we have a way to ‘discover’ the likely candidates and will be introducing that feature in 1.0.2 (See the Product Roadmap for details on several upcoming features).
A minimal amount of human intervention will be required - but we believe we have a way to drastically reduce the technical hurdles - enough so that the tool will be easily understandably by non-technical users.
In addition, around release 1.1.0 we will be publishing the specifications for Bluyah’s Basic Reporting Syndication (”BRS”) format, which is based upon Bluyah’s own XML export format (see this xml export for an example). At that time, the Bluyah application will allow you to create Connectors to BRS formatted data sources as well.
Keep your eyes on this space for more details as they become available.
|
|
|
|
|
|
|
|
|
ver 0.4.6 live
March 2nd, 2009
Comments
Version 0.4.6 of the Bluyah application has been released. As we get ready for our official launch on March 6th, you’ll see these next few releases contain minor fixes to the existing services as we polish up the app. This release in particular contains several back-end fixes that will make your experience with Bluyah more enjoyable. They include:
- A more coherent approach to DNS management [Ticket #119]. The end result is that users should no longer experience lag when going from their sub-domain to www.bluyah.com (or back again). All primary and sub-domains are now running fully on EC2.
- Problems logging out in IE7 [Ticket #172]. We realize that one of the most-appealing features of Bluyah is its ability to help you get things done quickly. You log in, do what you need to do, then log out and get on with your other work. IE had other ideas about how you should be spending your time - so we’ve squashed it’s attempts at workload domination.
- Letting you know when something goes heinously wrong. [Ticket #69]. We don’t expect it to happen - but half of being prepared is expecting the unexpected. We’ve enhanced error messaging so if in the off-chance something goes wrong in a big way, you won’t be left staring at a blank screen, clutching your coffee mug and wondering what just happened.
- Google Docs Connector now enabled for hosted accounts. [Ticket #127]. If you use Google Apps for your business then this is what you’ve been waiting for. All of your spreadsheets at docs.yourdomain.com can now be exported through Bluyah into your favorite formats.
- Enhanced features for Professional and Enterprise accounts [Ticket #150]. Our senior level account subscribers now have much more control over export configuration - including the ability to turn off the Bluyah branding attached to all Maps, Charts and Marquees. Now why people would want to do this we have yet to figure out….
- Fixed an issue with pie charts where users were not able to properly set the row containing their chart data in the UI. [Ticket #166]
- Enhanced maintenance notifications and defined maintenance window. You will now see a ‘System Unavailable’ message when we’re performing maintenance on the system. Additionally, we’ve standardized our maintenance schedule. For the immediate future, all maintenance will be performed on Saturdays between 9:00 - 10:00 PM PST. W will post a calendar to this blog and to the website.
|
|
|
|
|
|
|
|
|