It does not look like the core React Native APIs has anything listed for Address Book on iOS. This seems like a core thing you would need to do in an app.
Is this something that just needs to be built, or is there a particular reason there seems to be no info on this?
I have begun work on a Native Module that supports reading from a users contacts, once granted permission.
react-native-addressbook-ios
I just don't think it's been addressed yet, and there's not even anything in the Github issue tracker. The RN team do seem to have some things internally at Facebook that still haven't been made public, so we might see it from them in the future but the best way to find out would be to create a new issue to track any work on a Contacts API. I've done that for you here.
vjeux has already replied with his thoughts.
Related
i am quite new to Mobile App Development, Payment Gateway implementation and NativeScript itself. Now i shall integrate an IPG into a Mobile App build with NativeScript to allow the user to buy goods via the Application (it is already possible to do so via the Website). I do not have any information regarding supported payment methods yet.
Whenever coding something i do have the opportunites to either write it on my own or use an existing open-source API. I've decided to try an open-source API to make it work.
My Problem is that i don't really know where to start. I have been doing some research on "how nativescript works" and Payment Gateway itself. Basically any JavaScript code is going to work with NativeScript, so any open-source API for IPG working with JavaScript should do it for my Application, right? Since i did not find any open-source API's for NativeScript itself, i started looking for any JavaScript API. Sadly, all if found was an API of telecash (https://www.telecash.de/produkte-services/e-commerce/support-fuer-entwickler/downloads-handbuecher/) (watch out, thats a german side), whose documentation seems quite fine, but it did not seem open-source.
So my Question(s):
Can anyone tell me a little bit about any experience you might have with that topic (perhaps just a link or a tip)? Maybe there is even another thing that i should start with that i have forgotten? And i think i did not understand the difference (if there is one) between Payment Gateways itself and IPG. Maybe someone can help me out on that.
I can not post code here since i am still on the "research"-phase (have been for quite a long time), but I can not see any progress within it so I am counting on your help. Feel free to correct me if I did a mistake or understood something wrong I mentioned here. :-)
Best regards.
I'm trying to implement a OAuth2 appcelerator connector for Studio to connect to a wordpress (WP has installed plugins REST API, OAuth2 server). And appcelerator download this module https://github.com/JiriChara/titanium-oauth2-client, but it is a version of 2012 which certainly has flaws. Unfortunately I could not make them work together.
I want to ask the community (Since it is the first time I am developing this type of connection between an app and a website in wordpress), if they have any solution please.
Thank you very much
I think that since the oAuth protocol hasn't changed, you should still be able to use that library you linked to. I see that it hasn't been updated in a while - and maybe that's because there is nothing to update.
If you encounter specific problems using the library you can clone the source and try to fix (maybe even revive the project and push back to GIT).
Basically, oAuth is a set of HTTP calls - so you can write it on your own. But since a lot of the job was already made in that module I would try to get it working and push whatever fixes I can so others searching for the same thing can enjoy it as well.
Take a look at this repo. It is an Appcelerator Titanium widget that was written to work with Azure oAuth2 but it would only take slight modifications to make it work with other oAuth2 systems. I was successful doing this for a recent project.
https://github.com/grantges/co.grantges.azure.adal
The first is that they can update the code (include to require) . I also try to take this module, but does not work .
regards
Is there any way to access the appear.in API (Developer page) via python? I want to create a user with the API and with that credentials, I then want to create multiple rooms. I am assigning each rooms to separate persons hence I am storing the details in a database. Any help?
Developer at appear.in here. The short answer is no, we don't support that kind of functionality. We aim to be a very low-end API solution for those that need video and just that. If you need more advanced support, I recommend checking out http://simplewebrtc.com/. They offer more advanced features, but requires a bit more work.
Feel free to contact us at api#appear.in as well with your questions, that will get you answers much quicker :)
I know there are some packages like derby-auth, every-auth etc., that were written by the community/derby developers.
After a research I noticed that almost all the answers about the authentication mechanics in derby are pretty much a year old. Were there any changes? Is there a "derby" way to manage a simple username/password user authentication?
The official derby documentation says:
Access control
A basic access control mechanism is implemented, but it isn’t documented quite yet. An example is coming soon.
You can mix up your own authentication service, but the key point wold be - is there a way to properly secure you collections to prevent client side intrusion?
EDIT:
I can't find anywhere an example of a simple login and data lock! Is there a way to lock down collections and restrict some of the CRUD methods, like in MeteorJs? Right now, even with the derby-auth package, I am fully capable of mutating the model data trough the browser console, without being logged in.
Such a great framework, but this leak of documentation destroys it all..
AFAIK that is still work in progress: derby is still far from being production ready.
I'm working on a package called derby-passport, which is basically a fork of derby-auth, and I don't think any of these packages is actually an answer to you question. Not yet.
I will be developing a web application with Google App Engine that will use Facebook Connect as the only means of registering / logging in. The web app will be written in Python. I need to know their name, profile pic, how many friends the user has, as well as their age and also possibly location, relationship status, work info, etc. (although those are mostly optional besides name, pic, age and friend count).
There seem to be a number of libraries that can do the task. There is the official Facebook Javascript SDK, minifb, and pyfacebook to name a few.
How do you think I should go about this task? Which libraries should I use, and what are the pros / cons?
Also to be considered is how well documented the code is and how widely it is used. If you can provide links to relevant example code / documentation, that would be greatly appreciated.
Facebook python-sdk has an example application to use Facebook connect with Google App Engine. I guess, you are looking for the same.
This should be a comment for the answer which suggests using the Facebook python-sdk.
Note that at github it says
This SDK is deprecated. It does not support the new cookie format that
we rolled out as part of the OAuth Migration. In short, it doesn't
work.
I've had success with the facebook-sdk project, which I believe is a fork of Facebook's original (and now dead) python-sdk project noted above. However you may also wish to check out EngineAuth.
Why don't you check out this similar question asked by another StackOverflow user:
Simple Facebook Connect in Google App Engine (Python)
There are some links provided here that sound exactly like what you're looking for.
For all specified detail you need to go with respective permission from users and then you can extract all specific information you needed.
You can go by either Graph Api or Javascript Api:
But with javascript you need to use many ajax request through your application where graph api only need access_token once for particular instance and also independent of client action.
Graph API also helps you in preventing use of other framework like pyfacebook, minifb, etc.
Apart from pros and cons you can also look some example code for both javascript and graph api
Hope this information will be useful to you.