Hello Thomas,

Thank you for confirming that the alignment issue only occur in iPad 7.1.
I Will keep this thread updated with any news I heard from the dev team regarding CROS-635.

Update: December 9, 2014 10:35 PM

A nightly-build of Crosslight 3 (build 152) is now available to be downloaded. Please obtain the hotfix in here. This is a nightly-build update that fixes Post button getting truncated and vertical alignment issues from MessageInputSamples project in iOS 7.1 (CROS-635).

For your information, I have evaluated the nightly build on MessageInputSamples project using iPhone and iPad simulator (running iOS 7.1 and iOS 8.1) and found that the reported problems are no longer persist. Please let us hear your feedback regarding the nightly build.

The reason for not adding the dll in the demo project is to reduce the downloaded file size and to allow developers to test/run the sample project using the most recent version of Crosslight.

All Crosslight samples are now available online and can be downloaded from Intersoft Git server. Click the Download button such as shown in the following screenshot to start downloading the entire repo in a single zip file.

For quick setup, it is recommended that you extracted the zip file to the samples folder in the Crosslight installation. The samples folder is located in:

• Mac – /Library/Application Support/Intersoft Solutions/Crosslight 2/samples
• Windows – [Program Files]\Intersoft Solutions\Crosslight\Crosslight 2\samples

For more detail information, please check this article.

Apologize for the delay in sending this.

I created a simple project of UXGridView (bind to WCF RIA services using MVVM pattern) and implement data filtering using UXDataFilter control.

How do I simply use the itemsource for UXGridView as my source for filtering?

I assume that you want to bind an identical data source to UXDataFilter and your UXGridView. UXDataFilter supports both client and server data operation. When you set the QueryOperation to Client, UXDataFilter will process the data paging operation in the client against the given data source.
For more detail, please run the attached sample project, and open "Customers" page.

Hope this help.

What are the differences between Crosslight Form Builder and Xamarin Form?

Crosslight Form Builder is designed for developers to easily create rich data form targeting multiple platforms with a set of simple attribute-based metadata. Crosslight Form Builder is built with MVVM design pattern for the best separation of concern where the data input is provided in the model and ViewModel, which are then bound to the View in loosely-coupled manner. This means that Form Builder is not designed to unify the heterogenous views across different platforms which will cause a lot of issues and limitations.

Xamarin Form, in the contrary, is built with Unified View pattern which mixes UI definition, logics and input together. Since it unifies the views across all platforms, it can only provide features that conform to the lowest denominators of all platforms. This means that developers cannot leverage the unique UI features available in a particular platform. Compared to Crosslight, Xamarin Form falls short of architectural design and feels like an incomplete solution. It's a quick solution only for small projects and targeting novice developers who don't concern much on architectural aspects such as maintainability, extensibility, and scalability in the long run.

Unlike Xamarin Form, Crosslight Form Builder is only a subset of feature available in Crosslight. There are much more features that Crosslight has to offer, including a comprehensive solution for building enterprise-class mobile apps for iOS, Android, Windows Phone and Windows 8. It includes not only powerful frameworks, but also tons of gorgeous UI components, data access components, and best tooling support. Find out more about Crosslight's latest features at Crosslight Release Summary.

Hope this help.

In accessing REST service you often transfer data from client to the REST service or the other way around. The common way to do it is to serialize the data into JSON format or XML format which already handled by Crosslight RestClient. However the serialization process is more dynamic based on application's requirements, there are many ways to handle serialization and the possibility to have new format in the future. To handle these scenarios, Crosslight RestClient allows you can create your own Serializer and Deserializer that comply with the target REST service.

For deserialization, Crosslight RestClient will create the object based on the specified type, read the specified input string, and attempt to merge all property values available in the input string to the actual object. Properties not available in the actual object will be ignored.

string baseUrl = "http://localhost:27040/api/";
 
// create the Rest Client
IRestClient client = new RestClient(baseUrl);
 
// create and execute RestRequest to access GET api/values.
IRestRequest request = new RestRequest("values", HttpMethod.GET);
IRestResponse response = await client.ExecuteAsync<complexdata>(request);

Notice that the ExecuteAsync method has the target deserialization type.

IRestResponse response = await client.ExecuteAsync<complexdata>(request);

It will deserialize the HTTP response content to ComplexData object and you can get the deserialized object from the response.Data property.

For more detail information, please check the Crosslight documentation on Understanding REST Client Data Serialization Process topic.

WebAPI-enabled Inventory Tracker sample (Link to Git: http://git.intersoftpt.com/projects/CROS/repos/samples/browse/MyInventory_WebApi.) is recommended for you. One of its features highlight is: Efficient use of the RestClient Class and QueryDescriptor Class to demonstrate web data retrieval.

Hope this helps.