Flex/Flash Components for soapgate Q!

The Flex/Flash Components for soapgate Q! is a set of specific wrapper classes to consume the web service operations provided by soapgate Q! for Domino.

The collection of soapgate Q! web service operations are mirrored and extended in the Flex/Flash Components to reflect the specific differences of the Flex/Flash environment compared to the Lotus Notes Domino (and other environments for that matter) and to further simplify the coding for Flex/Flash developers accessing a Domino backend.

As Flex/Flash functions strictly asynchronous, a web service call requires at least two listener (or callback) functions that kick in once a web service result is available or failure occurred respectively. Listener functions are a bit tricky, not only from a memory management point of view, but also because of the asynchronous communication when calling a web service operation:

One cannot simply call the same web service operation twice (e.g. dbcolumn() on different databases/views) from the same web service object, having the same listener functions. At least not unless a mechanism is implemented to control which listener (callback) event is triggered by which web service operation call and hence to ensure that the respective result set is allocated/assigned correctly. 

Another problem the components solve is that of data conversion. For instance the operation dbcolumnX() returns multiple columns of a Notes view in form of a serialized array. As we know the number of columns requested and the number of array elements returned, it is relatively simple to convert the serialised array back to a two dimensional array (row/columns). But then again, there are two ways of deserialising the array: by row (required for a data grid presentation) or by column (required for e.g. dropdown lists). To make this story short, it is nice to have this conversion out of the box, making data binding to the web service operation's result-set a peace of cake.

By wrapping the web service operations inside a class each object instance of the class has its own bindable result properties and listener functions. Of course it also provides properties to assign custom listeners where required.

This class is a top level web service connector class for SoapGateQ! It mirrors the web service operations provided by soapgate Q!, manages the Domino authentication process and contains a session keep alive feature.

This is a wrapper class for all of the web service functions provided by soapgate Q! The wrapper functions take care of return value conversion where required (e.g. data serialization), error handling and custom listener functions for web service result and fault events.

This class provides workflow functionality for handling Flex/Flash (MXML) form components in a similar way a Domino developer would work with Notes forms (desktop client).

Most significantly it provides the same form events and listener or callback functions, such as QueryOpenDocument, PostOpenDocument, QuerySaveDocument, etc. 

This class integrates with the dominoDBUtilities class and calls its respective web service operations to read, save and send Notes documents.

This class provides workflow functionality for handling Flex/Flash data grids in a similar way a Domino developer would work with Notes views and folders (desktop client).

By default this class uses special soapgate Q! operations to read the design of a Notes view and to create from the received design information dynamically a Flex/Flash advanced data grid that mimics the Notes view. The result is a Flex/Flash data grid that works almost identical to the requested Notes view. This includes categorized columns, response document hierarchies, colors, fonts, icons, etc. It also provides paging functionality.

This class integrates with the dominoDBUtilities class and calls its respective web service operations to read Notes views. It also integrates with the dominoFormUtilities class to read, save and send the Notes document listed in the Flex data grid.

This class provides supporting functions to utilize the dialog components (MXML) coming with the Flex/Flash components, such as the Login and Names Dialog.