iSeller Commerce
iSeller POS Retail
iSeller POS F&B
iSeller POS Express
Crosslight
WebUI
ClientUI
What's New
Download Trial
Web Solution
Mobile Solution
Enterprise Solution
Custom Development
Blog
Community
Latest Development Blogs
ForumPostTopic
Browse By Tag
Hello Thomas,
Thanks for raising this question.
We are aware of the upcoming Xamarin's plan regarding unification of iOS and Mac OS API and support for 64 bit along the way. We will fully support the new unified iOS API by the time it is available, around early/mid January.
Since Crosslight lets you program most UI logic in the shared/core layer, the upgrades to the upcoming Xamarin unified API will be very seamless and straightforward. We expect very minimal effort for the upgrade process. That's made possible because Crosslight developers don't deal with the platform API directly. Most Crosslight's platform API are designed as thin layer mainly to provide binding capabilities and encapsulate view specific behaviors.
We hope you find this a good news. We will post more information as we have more updates regarding to unified API support.
Hello Fabian,
May I know why you need the Timer class from Xamarin.Forms assembly? The PCL and System.Tasks already includes full support for threading and timer. It's not necessary to use Xamarin.Forms just to use the Timer class.
Note that if you have installed Microsoft BCL extension (which is done by default if you created a new business project using Crosslight Project Wizard), you can access the tasks-related class from TaskEx in System.Threading.Tasks namespace. For the Timer class, it should be available in System.Threading namespace.
Hope this helps.
Hello Ryan,
The view-specific properties such as appearance aren't common to be implemented as bindable properties. That's because each platform has their own type and API which differ with other platforms. In Crosslight, we designed the bindable properties to cover most user interaction logic that can be well separated from the view.
The good news is that Crosslight also allows you to create your own bindable properties, so you can create binding for certain properties not supported in Crosslight. This can be easily done through binding adapter, a mechanism that Crosslight itself uses internally for the built-in MVVM-aware components.
You can see an example of binding adapter in our Crosslight - Syncfusion chart binding sample which is a bit quite advanced. We are planning to publish a simpler sample with walkthrough later this week. At the meantime, you can try to learn from the chart binding sample to grasp the concept.
Thanks for your continuous support and feedback.
No worries, we will escalate your issues to our development team and address these few glitches shortly. We will keep you informed.
Just to clarify, the vertical alignment issue supposed to occur in iPad 7.1 only, correct? Per our testing using the latest build, the vertical alignment looks good in iPhone, for both 7.1 and 8.1.
For your reference, the backlog for this issue is filed on CROS-635.
Dear Pedro,
Binding data to UICollectionView can be done similarly to UITableView. If you can get your data to show in a table view, then you can present it with a collection view without any additional code changes. This is how we designed Crosslight to be. One shared UI logic, multiple different presentation.
We demonstrate this capability in our highly popular Inventory sample which you can download from our Git server here. If you run the sample in iPhone, the data is presented in a table view. Try to run the sample in iPad simulator, notice how the presentation changed to a collection view without code changes.
In the simplest implementation, you will simply need to create a view controller that derive from our UICollectionViewController, then configure the settings as needed. For more information about Crosslight's collection view, see iOS Collection View.
Crosslight supports "custom cell template" which allows you to create your own cell with any number of information you want to present. This feature is supported in both iOS and Android.
In essence, once you defined the view components in the designer, remember to pair each name with the target member through itemBindingDescription.AddBinding method. We have published a tutorial for iOS which you can learn more in Create Custom Cell Template for iOS UITableView.
To see this feature in action, please check out our comprehensive Data Samples here. Once you get it running in simulator, head to the Custom Template sample.
We apologize for the delay in getting you back. We typically respond within 24 hours for our product support. However, since we had a major product launch last week, there were a short delay in responding our community posts.
Your posts and questions should be well taken now. We appreciate your feedback and look forward to assist you soon.
Thanks!
Thanks for your questions Fredy.
Here are some answers to your questions.
What about performance...?
Crosslight is designed with best-in-class binding architecture that allows blazing-fast performance. We also shipped custom components that have been optimized for the best performance, for instances, Crosslight's table view for iOS and Android are built for the fastest scrolling performance, even when coupled with asynchronous images loading. We have stress-tested our components with hundreds to thousands of data without performance bottleneck, thanks to our advanced UI virtualization implementation.What about designer (is there one designer for all platforms...?, is it usabled..?
Crosslight has a flagship feature called Form Builder. It's not a designer, although you can easily create a rich form just with some attribute-based metadata. For more complex views, you will need to use the designer from each platform. That's because the user experience for each platform is different, and we believe that successfulapps should implement an authentic, platform-optimized user experience.
What about open bug's..?
So far, we're pleased to say that Crosslight is the fastest growing product in the industry, with release iteration on monthly basis. Our team has deliver 5 consecutive release in the past 5 months, including dozens of major features and enhancements. You can check out our release history here.
Dear Ryan,
Hiding a button can be easily done in ViewModel through data binding. You don't need a service to do that. Since service is singleton, the best practice for service is typically used for non UI related tasks. To learn more about MVVM and data binding in Crosslight, please refer to the article here.
Crosslight comes with several pre-built bindable properties to help developers accomplish common tasks easily. Specifically for your case, you can bind the IsVisible property against the property in your ViewModel and the button. This allows you to set the property to true/false in ViewModel, which consequently reflects the visibilityof the bound view. You can find out the complete bindable properties in our class API reference here.
To learn more how MVVM and data binding works, I highly suggest you to check our comprehensive MVVM samples from our Git server here There are some examples showing IsVisible property, as well as many others such as opacity, text,value, and more.
or
Choose this if you're already a member of Intersoft Community Forum. You can link your OpenID account to your existing Intersoft Social ID.
Choose this if you don't have an Intersoft account yet. Your authenticated OpenID will be automatically linked to your new Intersoft account.
Enter your Wordpress Blogname