ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

JSON or XML - Ajax and the Graphing Calculator - part 2 in a series

Updated on June 25, 2011

The same graph as my last Hub

I used a different, and more flexible, technique to draw it, though; strange how getting back to where you started can feel like progress.
I used a different, and more flexible, technique to draw it, though; strange how getting back to where you started can feel like progress.

Picking a data representation

In this Hub, I am continuing my exploration of Using AJAX to obtain data for my graphing calculator to plot. My previous Hub on data input gave the background for why I want to do this.

The file that my code will fetch to plot needs to be in a well defined format. Otherwise, it will be almost impossible for the code to discern the meaning of the data. A pretty much infinite number of different representations are possible, but two stand out. XML has a tag structure that is easily processed via jQuery. JSON is a syntactic representation of javascript objects that could be evaluated by the javascript engine directly. Strictly speaking, JSON doesn't include javascript code, just data declarations, but you might need a browser plugin or javascript library to enforce that restriction. I am also not convinced that data is necessarily harmless. So, I prefer to write my own code to ensure that the data I am getting is what I expected. For this reason, I will use XML and parse it with jQuery.

var mypath = {
	path : [ [-1, 1], [0, 0], [1, 1]]
};

....
eval( data );

JSON does have the advantage of compactness, and parsing is done for you. The JSON representation of my data would look like this. Once I received it, I could just have javascript evaluate it, or I could use a parser that is specialized to JSON. The latter would prevent any inadvertent execution of javascript that is in the data.

The same data as my previous Hub

<?xml version="1.0" encoding="utf-8"?>
<path>
<point>
<x>-1</x>
<y>1</y>
</point>
<point>
<x>0</x>
<y>0</y>
</point>
<point>
<x>1</x>
<y>1</y>
</point>
</path>

However, as I said, I chose to represent my data with XML. The first tag is necessary to convince some Web servers and Web browsers to treat my file as an xml file. Properly, I should use a standard document format or define a formal schema, but that is a lot of work which I won't get much practical benefit from. So, I didn't bother.

I used a "path" tag to encapsulate a list of points on the path. Each point encapsulates an "x" and "y" element. In the future, I could add additional dimensions to the point, and some descriptive information to explain what each element is.

For now, I am just trying to get something simple up and running, though. I don't want to get bogged down in too much elaboration early in a project.

The fuction for fetching a list of points

function getPath( url, coord ){
	var xpts = new Array();
	var ypts = new Array();
	var yi = 0;
	var xi = 0;
	$.get( url,
		"",
		function ( data ) {
			$( data ).find( "point" ).each( function () {
				$(this).find( "x" ).each( function () {
					xpts[xi++] = $( this ).text();
				});
				$(this).find( "y" ).each( function () {
					ypts[yi++] = $( this ).text();
				});
			});
			jgplot( coord, xpts, ypts );
	});
}

The function to the right uses jQuery to fetch and parse the XML file. get is one of a family of AJAX functions that jQuery offers. It like the others, calls a function once the data has been fetched. That function is where I translate the XML into a couple javascript arrays, and call the plotting function I developed in my previous Hub.

The HTML to call my new function

<tr><td><img id="start_plot" src="jgplot.jpg" 
onClick="javascript:getPath('/path1.xml', unitsquare);"
 /></td><td>&nbsp;</td></tr>

Now, I just need to alter the javascript related to the onClick event of my "Plot" button to cause jgGetPath to execute and graph my points from data stored on my local Web server.

The resulting graph is the illustration at the top of this Hub. Basically, I've done some work to get back where I started; a pretty common approach in programming. In my next Hub on this topic, I will use this stepping stone to do something more exciting, though.

Comments

    0 of 8192 characters used
    Post Comment

    • oldhorse profile imageAUTHOR

      oldhorse 

      7 years ago

      Testing to see if I can post a comment.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://hubpages.com/privacy-policy#gdpr

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)