Hello,
I've developed a web application that has data stored on a remote SQL*Server database. I now want to create a mobile iOS app (native feel, but using Kendo) that will allow:
1. For the user to 'log-in' and be authenticated using a username/password stored in the SQL*Server app
2. Whilst connected to the internet/SQL*Server, download a list of data elements from the database from about 5 tables. This could be down by using a 'Refresh' or 'Update' button
3. Disconnect from the database (i.e. I can't assume that access to the database it possible) and then use the data from the database that is now locally stored. This data need to be available should the user close the apps and restart it
4. Execute a sequence of updates using the app and then post certain updates back to the database once the internet connection is re-established.
Is the above functionality possible with Kendo?
Thanks,
Nick
I've developed a web application that has data stored on a remote SQL*Server database. I now want to create a mobile iOS app (native feel, but using Kendo) that will allow:
1. For the user to 'log-in' and be authenticated using a username/password stored in the SQL*Server app
2. Whilst connected to the internet/SQL*Server, download a list of data elements from the database from about 5 tables. This could be down by using a 'Refresh' or 'Update' button
3. Disconnect from the database (i.e. I can't assume that access to the database it possible) and then use the data from the database that is now locally stored. This data need to be available should the user close the apps and restart it
4. Execute a sequence of updates using the app and then post certain updates back to the database once the internet connection is re-established.
Is the above functionality possible with Kendo?
Thanks,
Nick
2 Answers, 1 is accepted
0
Hello Nick,
These requirements are not currently supported in Kendo UI Mobile. I would suggest you to use the DataSource component which is part of the Kendo UI Framework. It fully supports CRUD (Create, Read, Update, Destroy) data operations and provides both local and server-side support for sorting, paging, filtering, grouping, and aggregates.
Regards,
Kiril Nikolov
Telerik
These requirements are not currently supported in Kendo UI Mobile. I would suggest you to use the DataSource component which is part of the Kendo UI Framework. It fully supports CRUD (Create, Read, Update, Destroy) data operations and provides both local and server-side support for sorting, paging, filtering, grouping, and aggregates.
Regards,
Kiril Nikolov
Telerik
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
0
Dean
Top achievements
Rank 1
Rank 1
answered on 08 Sep 2013, 11:47 PM
Hi Nick,
Actually, your list of requirements are the same as ours and we're in the final phases of testing our mobile app. We use the Kendo DataSource to connect to a local SQLite database on the phone so that the user can update the data without a connection to the internet. Our synchronization with the remote SQL Database on our server is done using jQuery's AJAX function.
So our app works like this:
1. We make an AJAX request to download data from our server (passing a username & password for security).
2. The response is a JavaScript array of records that we loop through and store in a local SQLite database.
3. Refresh all the Kendo DataSources which allows the user to continue interacting with the data locally.
The parts of our mobile app that connect to our server are coded by us using jQuery, they don't use Kendo. Kendo is used for the interface and connecting to the local SQLite database on the phone. Oh, and I should mention we're using Icenium, which comes with the SQLite plugin that we use.
I hope this helps.
Dean
Actually, your list of requirements are the same as ours and we're in the final phases of testing our mobile app. We use the Kendo DataSource to connect to a local SQLite database on the phone so that the user can update the data without a connection to the internet. Our synchronization with the remote SQL Database on our server is done using jQuery's AJAX function.
So our app works like this:
1. We make an AJAX request to download data from our server (passing a username & password for security).
2. The response is a JavaScript array of records that we loop through and store in a local SQLite database.
3. Refresh all the Kendo DataSources which allows the user to continue interacting with the data locally.
The parts of our mobile app that connect to our server are coded by us using jQuery, they don't use Kendo. Kendo is used for the interface and connecting to the local SQLite database on the phone. Oh, and I should mention we're using Icenium, which comes with the SQLite plugin that we use.
I hope this helps.
Dean