Image Plane Developer Documentation
An ideal implementation of Image Plane will most likely utilize a number of sophisticated web development techniques and use any number of client and server side scripts. The bare minimum implementation should use an embed or object tag (although embed tags are deprecated in HTML 4.0) to add the Image Plane application to the page. See the example of a well formed embed tag below. A better implementation would use a script to dynamically add the input variables to the get string.
- <div id="imagePlaneDiv" style="width:100% height:600px">
The application is designed to be flexible and fit into any framework. If you wish to enable the user to edit images as they are uploaded you will need to create a more sophisticated page interface. For example, let's say we have a page thats part of a CMS with a form to add a new product to a web store. You can enable the user to upload and edit a new image for the product before they submit the new product form
To do this, add an iframe to the product form. Inside this iframe use a file field to select an image for the new product. When the user selects a file, the form of the iframe submits and uploads the new image to the server. After the upload is complete the iframe changes to display a thumbnail of the new image and adds an "edit image" link that will open the Image Plane application to edit the now server-side image. The user can then edit the image using Image Plane before saving it back to a temporary directory. The user repeats this process for any other image files before finally submitting the original form for the new product. This submit script that checks the temporary directory for Image Plane's file output to see if a file was uploaded by the user and stores the new image with the product information to a database.
A few other important notes:
- Image Plane is programmed in ActionScript 3.0, thus it requires Flash Player 9 or later to run.
- Because it can stretch to fill any space, opening Image Plane in a new browser or modal window by itself allows it to maximize its potential.
- Image Plane is generally setup to save each image instance output under the same filename. To prevent these instances from overwriting each other you should save each instance output to a unique temporary location. You can control this using the IPinstance nodes of the parameters.xml file.