I'm not that good in understanding apple documentation, but is it "Safe" to use this: http://www.touch-code-magazine.com/tutorial-building-advanced-rss-reader/
In a Xcode project, or will apple reject the app because it is customized?
I understand this might be a stupid question, but since Im not sure of the rules, I thought I ask first.
Also, what is the best way to release it?
Thank you in advance!
All the best,
Andy
Absolutely safe to use. I use GData in my project and Apple never rejected it.
You can use without any problem. And you can also use NSXLMParser.
Related
I am trying to find the reason why LSCopyItemInfoForURL is depreciated. I tried to read the apple developer page but i couldn't find the reason. I am new to mac. Can any expert give the reason behind it?
Ask this question on Apple Developper forum. Only there you can find some who has an answer. But I am not sure Apple talks about deprecation. It’s their choice. Usually, that means that there is a new way to do the same thing and it has been considered that the new way should be ´The Way ´
I thought navigation-experimental was the latest one and I saw some posts which says it is deprecated in V0.43. So which navigation component to use in IOS, If I want to start today ?
Update:
There is no right answer to this question. But personally I prefer react-native-router-flux. But there are too many ones which makes difficult to choose.
You can also check reactnavigation. I hav not tried it yet personally but it seems promising.
Have a look at this one - https://github.com/wix/react-native-navigation.
It has good API and is well maintained.
I haven't used it myself though. The one I use is https://github.com/aksonov/react-native-router-flux
I think the best way to get started is on Exponent. Ex-navigation is great for beginners.
I want learn how to develope floating notifications.
I need any API or Library?, Somebody knows?
Thanks.
Have you tried looking at bootstrap's notifications? You an build your own if you;re keen to do it. Otherwise, you can try NotifyJS. It is simple to understand and easy to use.
I'm trying to update my app (iSocialNet) to use the latest version of MGTwitterEngine without success. I've successfully got iSocialNet to work using Ben Gottlieb's Twitter+OAuth, but there are issues that come with it.
What I would like to do is make my own 'TwitterEngine' but I'm not sure where to start. Can anyone please point me in the right direction? I must warn you that my knowledge of ObjC is minimal, but I'm getting there. Any help is appreciated.
The problem with Twitter+OAuth is that I can't get native retweets to show in the timeline, there's no retweet feature in the MGTE supplied, I can't get all users that a person follows and that's just what I've encountered so far. This is why i need to either update MGTE which comes with OAuth or i need to implement my own engine. I know that OAuth is tricky, but there's a library that MGTE uses that I would use. It's the actuall speaking to twitter that I don't understand.
Many thanks in advance
You could try to parse the timeline directly off twitter, I have same problem and I think it may solve the retweet problem as well as parse the follower list off twitter too ;)
I'd recommend you to explain your problems with Ben Gottlieb's Twitter+OAuth here better than implementing a new OAuth engine, that's absolutely not trivial and with little Objective-C knowledgement it could be disappointing for you! We can help each other here and by reusing code.
I need to design a simple plugin system in Objective C. I would like some advice about how to go about this. Thanks!
Cocoa is your girlfriend: http://www.cimgf.com/2008/09/17/cocoa-tutorial-adding-plugins-to-a-cocoa-application/
Awesome tutorial.
There is always going to the Source. Here is the ADC reference to Plug-ins
There are dozens of ways you could do this, so you might need to elaborate a little on what exactly you're trying to achieve. As a starting point, I'd recommend you look into Cocoa delegates which are usually a great way to integrate new code into an existing framework.