I am working on IBM Worklight. I have developed an application using JSON Store.I have some questions related to JSON Store.
1.Does JSON Store possess size limit?
2.JSON Store stores data in file right? If I want to see the data that is in JSON Store, how can I see that on my device?
3.Does the memory of the device has any impact on the JSON Store storage?
4.While creating a project ...I found option like create --> new Worklight JSON Store. What is the actual use of it? I am not able to create a new JSON Store with that option.
1.Does JSON Store possess size limit?
Available space on the device. More details in the documentation.
2.JSON Store stores data in file right? If I want to see the data that is in JSON Store, how can I see that on my device?
Yes. More details in the documentation. For example, on Android the database file is stored here: /data/data/com.[app-name]/databases/wljsonstore/jsonstore.sqlite
3.Does the memory of the device has any impact on the JSON Store storage?
JSONStore uses some amount of memory to work, like any software application. There's an section on performance in the documentation.
4.While creating a project ...I found option like create --> new Worklight JSON Store. What is the actual use of it? I am not able to create a new JSON Store with that option.
There's a blog post here that uses the wizard. Keep in mind the blog post is very dated, it's meant for Worklight 5.0.5. Some methods used in the blog post have been deprecated and improved since, but still made backwards compatible. What I actually recommend is basing your JSONStore code on the new 6.0 sample code here. There's a section in the documentation here that explains adapter integration and the wizard.
Related
i implemented a chat app in swift using firebase real time db, there user can send images, emojis and Text.Now i have a requirement of export chat or get the conversation's backup with media and text as per whatsApp.help me to solving it out.
While Firebase offers a backup for the Realtime Database, this doesn't fit your needs here, since you'll want a per-user export of the data.
Since this is specific to your application, you will have to code it yourself, just like the good folks at WhatsApp have probably done. It should be a matter of iterating over all data sources for the user, getting the data through the relevant API (that you're already using to display that data), and then writing to a local file). You can do this either client-side in your Swift code, or server-side on a server you already may have, or using Cloud Functions.
If you're looking for some inspiration for the latter, there is a sample repository that shows how to clean up a user's data, based on a set of wipe-out rules. You'll need to significantly modify this example though, so I'm not convinced this will be less work than rolling your own from scratch.
I want to develop an app, which will store information (text) locally on the phone.
I'm new to iOS development and wanted to find out if there's any internal DB system that is recommended to use to store data or if there's some other solution like AsyncStorage used in conjunction with React Native...
Sorry if the question is a bit general, but I could not make it more specific due to the lack of information I have.
You can use Realm for React Native to store data.
It's easy to start ORM database which can be used on Android/iOS.
As the title says, I'm looking for a string to be input in an IOS app and stored in a way that it would be accessible from a web browser.
Both editable and readable from web and the app.
From initial googling, I've come across Dropbox Datastore API but it is being deprecated.
What would be a good alternative for this?
Your intentions are quite scant. However, I assume you want a little more than just reading and writing a string. Inferring a bit more context, you should look at Apple's CloudKit.
It has API for iOS, OS X, and apparently now javascript. See this link for more details.
You need some code running on a server and a database to save the string, with an API to access this string from a client.
FireBase is probably the simplest drop in solution since it gives you a very basic example and a web based UI for testing (plus it updates in realtime)
I'm rather new to IOS but i managed to get my app to display a list of blog posts from RSS feeds. I would like to give my users the ability to save the blog posts for reading later when they might not have an internet connection.
I will do this through a setting in the settings bundle. I do not however know what the best way is to store blog posts within my app. I am already using core data, would this be a good option for it?
If you are already using a persistence option then use it for everything, don't mix and match.
If you are already using Core Data then yes it makes sense to keep using it throughout the application for consistency and maintainability.
I'm designing a new app for iPad for a small company. This app will use Core Data to store a local database and a database of products and prices. The last database needs to be always up to date since the prices can change.
This company, has a Excel file to keep this database of prices. So they don't have a SQL db to which I can interact from my app.
One option could be to export the Excel file in CVS and put that file in their server (accessible by internet). Then my app should parse the file.
I don't like very much this idea, though.
Do you have any suggestion?
I had a very similar problem to you. I recently got into a project where the client wanted to import information from an Excel file into an app. I know a lot of people say, just transform it into a CSV and parse it that way, but I really didn't want the client to go through yet another step and introduce a different file format - as simple as that may be.
I also really don't like having the information in the cloud, especially Google. Privacy is something that's important to most companies and I'd doubt they'd approve of you using Google to parse the info.
In order to parse the file, I created QZXLSReader. It's a drag-and-drop solution so it's a lot easier to use. I don't think it's as feature complete, but it worked for me.
It's basically a library that can open XLS files and parse them into Obj-C classes. Once you have the classes, it's very easy to send them to Core Data or a dictionary or what have you.
I hope it helps!
Here are a couple of options for you:
Use Google Doc as the intermediary. When the pricing Excel is updated by someone, simply upload the updated Excel to Google Docs. From your iPad app, you can read the latest data via the Goole API. If the company is up for it, they can move to Google Doc altogether and just modify the online Google Spreadsheet directly.
Use services like StackMob as the intermediary. You will have to write a tool to sync the pricing Excel with SrackMob but you can easily access the data via StackMob's iOS SDK.