Vvidget Server ► Overview ► Design
Vvidget Server can be used in a desktop application, static HTML, or in a web app server configuration. The designs for each are diagrammed below.
Desktop Application
The system you use while programming with Vvidget Server is diagrammed in the following figure.
The Graph Views in your application sends input to the Peer Visual Server which returns a resulting graph image. The graph layouts (fonts, grid widths, colors and annotation, etc.) are maintained in template directories. You can use the default layouts in which case you do not have to be concerned about templates. However, sooner or later you will probably want to add your own graphics to the graphs in which case you will need to add a templates directory to your application's Resource folder.
You use the graph view's input string constructor to form key value pairs as input to the server. Once all those entries are formed you display your graph view and the communication starts. For example, to form a "data_value" key and value pair use this code:
VP_Input_String_Constructor *inputStringConstructor;
NSString * dataString;
inputStringConstructor = [myGraphView get_VP_input_string_constructor];
dataString = [myTextView string];
[input_string_constructor VP_append_key:"data_values" string_value:data_string];
The key value pairs are described in the Dictionary section.
Static HTML
By using static Peer Visual HTML you can provide charts of your data without having to store the chart images. You can also provide PDF forms for print without further conversion. In addition, you can provide forms processing to permit access to your information.
The static html design is diagrammed below. The request to the graphing server comes directly from the web browser after it reads your HTML file in the normal way.
Web Application Server
By utilizing a web application server you can automate the construction of the peer visual URL. In this way you can construct URLs dynamically based on query state information. The Peer Visual server can also be programmed (optional) to respond to custom application service URLs.
