Create new components by (doh) clicking the appropriate button. Move components by click-dragging. Resize components by SHIFT-dragging. Highlight by selecting (That would be clicking, yes).
After creating a component you need to configure it by clicking "Configure". You then get a list of the properties that the component wants defined. For components that format external data sources, such as table or tree, you need to select *which* data source you want to read.
Which brings us to the subject of data sources. A data sources is an url and a "path" into the data generated by that url. If the data source is a JSON Dappit dapp, the path describes the place where to truncate the data and try to display it. At the moment the generic XML and Web Service data services are not functioning.
The table looks best if you choose a path in the data source chooser that is just above the information you want to use as table rows. If you use a dapp, this place is usually "Server Data.fields"
OK. here be dragons. :) It's at this point your eyes glaze over and you fall slowly to the ground waiting for the next ice age or garden party or anything, really, just to GAFIA. For those hardy souls still awake, the radio edit goes like this; A Datasink is what you get when you treat a Dappit Dapp or a Web Service as if it were a callable subroutine. Sort of. When you create a data sink, you create a list of input variables. Then when you create a form, you can choose which data sink to send the contents of the form. So the data sink acts kind of like the action=".." part of regular forms handling.
But then the thing you are calling might have some retun value, so creating a sink also creates a coresponding data source, which will contain the return value(s) if any from the data sink. That means that you can create a table which reads from the sink's data source. This will result in two visible on-screen components; 1) A form component with any number of fields in it, 2) A table component which will update itself with the result
of the data sink tied to the form when called with the for field values as arguments. Sound simple,doesn't it?
Containers can bre dropped in and between each other. Color can be choosen with the "color" button, oddly enough. Also, it almost works to delete containers with the button with the same name. Table and Tree needs a json datasource which uses 'cb' verbatim as a json callback function. The data source will then be read and presented as a tree. Click down the tree to choose which level will be used as source for the component.
Use the html component to insert raw html code.
Try the following dapps (http://www.dappit.com) as datasource url;
Back to Mashup Station