I trying to make a Web Service application which will run when the program is on the background too and i will fetch my data from tree different URLs from my server. I read almost all of this and also this tutorials and even i watched CS193p Core Data Lectures too but still i cant get started with coding. This is my first Iphone(ipad) application, i use NSJSONSerialization for parsing. Can anyone please explain a little
How many ManagedObjectContext s i need to declare?
How to save data which come from different classes to the same entity?
(The mos important) From where to get started with coding..
I think this is a kind of not wanted questioning but i really need help. Thanks in advance
I would suggest taking one of the core data sample apps from the ADC site and looking at how it's structured. You may even be able to adapt the code to your application. CoreRecipes is a great sample to learn from.
https://developer.apple.com/library/ios/#samplecode/iPhoneCoreDataRecipes/Introduction/Intro.html
Related
I am taking a hand in development for the first time and trying to teach myself some things, and chose to start with ASP and Visual Studio. I have a rather simple question to ask... I generally search and search and search... but I don't know what the proper term/phrase is for what I'm searching for.
Assumptions: Visual Studio 2013 (not express), asp.net mvc5 with bootstrap(3.1.1) is what I'll be using.
Two part question: what is the phrase/term to use when searching for an answer to part two? data grid? data fill? something else?
The second part of my question is what are the most commonly used methods of creating and filling a table with data from an existing database? Do people almost always just have to hand code everything or are there great tools out there?
So far I only found...igniteUI and I haven't actually read the website to see what it's about yet. I want to be able to design something... maybe using bootstrap or boilerplate.. and then create tables and fill them with tables. I've only ever made static sites. Anything that has some kind of GUI that lets me build these tables and and direct certain data types to specific table columns and rows would be a major plus, as I could compare what I just did with the code that was created... and then I could learn to make cleaned up handcoded versions myself. this is how I learned web design, I figured I could learn SOME parts of development the same way.
As I said above, the reason I am asking this question is because I do not know what any of the proper term(s) for what I'm describing and wasn't sure where to start.
Welcome to SO.. kind of a loaded question and somewhat opinionated, but I have 2 spare cents I can offer.
In the end, it depends what data you are trying to present, and what you want that user to do with that data. With HTML, anyone can create a simple table and present some data (aka TR and TD tags). What's this good for? Showing tabular data. What's this not good for? Anything interactive...
OK, so then what do we use instead? Again.. depends what you're trying to allow the user to use, AND if you have any existing resources in place. For example, jqGrid is your front runner in late bound, jquery enabled sortable\editable data presentation. ExtJS is also a popular scripting library, and they have some tools as well.
But that's late bound, javascript enabled stuff.. what about things that are already bundled into ASP.NET? Well, you have the gridview and listview at your disposal. Both are nice because they allow some quick and easy ways to connect to structured data, and if you're using some of the more popular data stores, such as SQL server, you even get drag\droppable connections (aka, less coding). Telerik has been in the game a long time, and for some cash, you can get some pretty advanced tools.
Again, all opinionated stuff. ASP.NET has some very nice things out of box, but nothing is perfect.. all of the items mentioned above I have used at one time or another, and they've been a great foundation for starting my applications. But at the end of the day, I always had to take what was given to me and add\edit functionality to get what I ultimately needed.
Hope this helps...
This question already has answers here:
Working with data in iOS Apps (What to choose? NSData, CoreData, sqlite, PList, NSUserDefaults)
(2 answers)
Closed 9 years ago.
Really straightforward description of my app; it is a simple app that display for the consumer questions and the user must answer the question I attempted to store the questions on a simple txt file and luckily I got a positive consequences,However I thought perhaps I should come with another way to store my data and I been very curious about using Core Data since it might be better for my app and for me as well since I'll gain more skills and information on iOS programming. To be honest I'm new to the iOS world and never used Core Data before.Yesterday I started studying the library that Apple provides to the public and what I found out that I can't access or add data on my NSManagedObjectcontext unless adding some lines of code such as the insert method and fetching the data. correct me please if what I mentioned earlier was wrong and lastly my question is should I use core data technology on my app? I'll be pleased to get more tips,info and great sources from you world.
As a beginner, you'll probably have an easier time with plists than with Core Data (which has some learning curve, and you'll need to write, and understand, some code to make it work).
With plists, you can save an NSArray or an NSDictionary as a file (and read that file when needed). You can also create a plist with some data and include it into your app (e.g. if you have a set of questions you want to include). Check out this tutorial.
Of course, once you need to implement data storage in a real, production app, you need to understand the tradeoffs between all the different persistence mechanisms that iOS provides.
Core Data can be made more approachable by using a tool such asmogenerator which will help abstract from a lot of the more in-depth stuff. Good stuff for wanting to do things 'right' and to progress your knowledge, but maybe the best way to do this is to keep it simple, get it working and move to something more in-depth if you start hitting walls?
Looks like they are trying to close this so hope this helps
I am making an iPhone application and Website simultaneously and I want a shared database between the two. I know about some of the options although none of them seem to work perfectly. Like Core Data which will be very nice on the iPhone side, although I havent found a way to access the same information in something other than Obj-c. SQLite is another option, I might not be right, but it supposedly does not work well for servers and being accessed simultaneously from different places. Or I could do XML which seems easy on both sides but it seems like thats the slowest option and will have a huge drag on performance if im going to be reading it from a server all the time.
Any help would be appreciated, and if you know of any other solutions I will be glad to give them a try.
Thanks in advance,
Jordan
Have you thought of using a MySQL backend on your server, and then providing your mobile application with an API?
This takes the hassle out of data synchronisation and also provides you with a good level of sustainability and scalability.
I hope this helps.
Josh.
I was put in charge of learning this and well I have read and tried to understand it all. I am lost in how to get it started and optimized. I need to achieve a window at startup that is menu based and takes you to different components. I think I have the photo galleries sorted out just now sure how to link to the startup window.
examples
I used this tutorial when I was trying to learn - http://miamicoder.com/2011/writing-a-sencha-touch-mvc-application/
The learning curve is quite steep but once you understand it it's a really good bit of kit to know your way around.
If you don't already understand the MVC (Model View Controller) architecture then it's going to be a bit tricky but the tutorial explains it all pretty well.
My advice would be start following the tutorial. Stick to it, get it working and THEN adapt it.
Good luck.
With Sencha Touch 2, the team have created a bunch of guides which hopefully help ease the pain when trying to learn the framework.
I suggest you first take a look at the Getting Started Guide, and then move onto the Building your first App Guide. These both should give you a kick start on where to start.
After that, I would definitely recommend you take a look at the code of their various examples, and then try modifying it. When I was first learning the framework (and JavaScript in general) I found that taking existing code and modifying it was definitely the easiest way of learning. Obviously this varies from person-to-person, but it is always a good step.
Much of their documentation have previews and examples which you can actually edit the code inline, which I have found very useful in the past. You can view an example of this here.
The Touch Forums are very active. Almost all topics get responded to within hours, and I have never seen a post which was never responded to.
I am a final year computer undergrad student looking for a unique (or semi-unique) application for audio fingerprinting, for my finally year project. My original idea was to have a program to figure out what song a user was humming, thru the use of audio fingerprint. But I did a search, and found out somebody had already implemented it (perfectly I might add). Any suggestions on how I can tweak it (it doesnt have to be TOTALLY new) or derive some thing along similar field will be VERY MUCH appreciated.
P.S. Thank you in advance.
(P.P.S. I don’t have to do a full implementation, just the core part or an essential part of my choosing)
Last.fm has an amazing API and song fingerprinting script. Maybe you could extend their app to do something different?