Difference between revisions of "XB PointStream/custom parsers"

From CDOT Wiki
Jump to: navigation, search
(Parser Interface)
Line 1: Line 1:
 +
===Parser Interface===
 +
 +
==Intro==
 +
Currently XBPS only supports reading .ASC file types. If you require the library to render other files, you will need to write a custom parser and register it with the library. This should not be difficult, there are only a few things your parser must implement.
 +
  
===Parser Interface===
+
==Example==
 +
Here is an example which you can use to help understand the process: [link here]
  
Currently XBPS only supports reading .ASC file types. If you require the library to render other files, you will need to write a custom parser as register it with the library. This should not be difficult, there are only a few things your parser must implement.
 
  
We have already created a demonstration of this. You can find it [http://# here].
+
==Parser Skeleton==
  
Here is a skeleton of a parser you could take and implement:
+
The following bit of code is a skeleton which you can use as an aid to help you write your own parser.
  
 
<pre>
 
<pre>

Revision as of 18:58, 14 February 2011

Parser Interface

Intro

Currently XBPS only supports reading .ASC file types. If you require the library to render other files, you will need to write a custom parser and register it with the library. This should not be difficult, there are only a few things your parser must implement.


Example

Here is an example which you can use to help understand the process: [link here]


Parser Skeleton

The following bit of code is a skeleton which you can use as an aid to help you write your own parser.

var Your_Parser_Name = (function() {
  /**
  XBPS will create an instance of your parser and pass in an object with three
  named properties:
  
  start - must occur exactly once. Has one argument, the parser itself
  end   - must occur exactly once. Has one argument, the parser itself

  Everytime your parser calls the parse function, it must send in an object with
  named arrays. In the following example, vertexArray is a Float32Array which contain
  the vertices which have already been read and parsed.

  var attributes = {};
  attributes["ps_Vertex"] = vertexArray;
  attributes["ps_Color"] = colorsArray;
 
  parse - may occur one or many times. Has two arguments, the parser itself and a
  
   Your parser is responsible for calling these functions at the appropriate times.
  */
  function Your_Parser_Name(config) {
   
    /*Returns the version of this parser.*/
    this.__defineGetter__("version", function(){
      return /*!!*/;
    });
   
    /*Get the number of parsed points so far.*/
    this.__defineGetter__("numParsedPoints", function(){
      return /*!!*/;
    });
   
    /*Get the total number of points in the point cloud.*/
    this.__defineGetter__("numTotalPoints", function(){
      return /*!!*/;
    });
   
    /*Returns the progress of downloading the point cloud between zero and one.*/
    this.__defineGetter__("progress", function(){
      return /*!!*/;
    });
   
    /*Returns the file size of the resource in bytes.*/
    this.__defineGetter__("fileSize", function(){
      return /*!!*/;
    });
   
    /**
      @param path Path to the resource
    */
    this.load = function(path){
      /*!!*/
    };
  }
  return Your_Parser_Name;
}());


/*
  The following example demonstrates how XBPS might use
  a particular parser.
*/

var parser;

function startCallback(parser){
  // started
}

function parseCallback(parser, attributes){
  parser.version;
  parser.numParsedPoints;
  parser.numTotalPoints;
  parser.progress;
  parser.fileSize;
}

function finishCallback(parser){
  // finished
}

// create a hypothetical parser and set the callbacks
parser = new Your_Parser_Name({ start: startCallback,
                                parse: parseCallback,
                                end: finishCallback});
// load some resource
parser.load("pointcloud.xyz");