Is paypal express checkout supported or not. While downloading the merchannt SDK samples I found this
"This Classic SDK is not actively supported and will be deprecated in the future. For full support on new integrations, please use the PayPal REST API SDK for .NET"
I need the express check out option. Which one should I use?
I am kind of confused. Can I use merchant SDK the classic one or go with the REST API?
The message about deprecation for the SDK is a bit misleading. PayPal have new REST APIs and also the Braintree v.zero SDKs, and these are the products that should be used for integrations going forward for the vast majority of merchants.
However, for enterprise merchants, and especially customers with specific product features that are not currently supported on the new platforms, Express Checkout is still the best solution, and it will continue to be for some time. So the deprecation message is intended to guide to the new APIs, rather than indicate a lack of support or functionality.
PaySharp.NET is an open source .NET SDK, and should meet your requirements, given that it is specifically designed to support Express Checkout. Here is an in-depth tutorial on the subject.
Related
I want to add a new payment method in BigCommerce for Digital River.
The API's don't allow.
I have seen the workaround mentioned in : Creating new payment method for Bigcommerce
But that's just a hack, and we need something build in, don't want to write the DR wrapped in whole.
I looked at the SDK : https://github.com/bigcommerce/checkout-sdk-js/tree/master/src/payment/strategies/digitalriver
where DR is added couple of weeks ago, is this something going to be supported sooner ?
You're right that this is not currently supported via apis in the docs. As creating a new payment integration is not as straight-forward as other integrations, such as shipping or tax for example, which use the rest apis in the BigCommerce dev docs.
This process requires a partnership with BigCommerce, in addition to being a large time & resource investment. I do have good news though -- BigCommerce is currently working with this provider to build this integration! :)
We are finishing up an Outlook add-in which was written using Angular 8 with typescript. I am doing my investigation into what it will take to write a gmail add-on. I've gone through the quickstart tutorial using Apps Script. I've also looked at the clasp tool.
Is it possible to create a Google add-on with the angular framework?
Thank you.
Unfortunately, it is not possible to build Gmail add-ons with Angular framework.
Gmail add-ons are distinct from "Editor Add-ons"(ie. add-ons built for Google Sheets, Google Docs or Google Forms) and are developed strictly with App Script using a widget-based model.
Furthermore, Gmail Add-on development does not grant developer's direct access to the DOM.
See restrictions of Gmail addons.
The short and simple answer is no.
Google Workspace Add-ons UI are created using the Cards framework. Besides Google Apps Script, nowadays it's possible to use programming languages like Java hosted in Google Cloud Run or other hosting infrastructures as long as they deliver JSON to build the add-on UI using the Cards framework.
Reference
https://developers.google.com/workspace/add-ons/guides/alternate-runtimes
You could try using the InboxSDK.
Typically you end up having to manipluate the DOM. This tool caters for most the key functions in an easy to use library.
Not so sure how you will use Angular but it is possible to build rich experiences based on this library.
I have used Dialogflow for developing the app for Google Assistant. I have created intents and entities in the Dialogflow web GUI and I'm using a webhook response for further conversation.
Now I want to build a chatbot that is part of an existing Android or iOS app and use the code I already wrote for Dialogflow as part of this. What do I need to be aware of when I do so? It looks like I can use the SDK for that platform or make calls to the Dialogflow REST API. Which is faster or are there any tradeoffs? Can I use the Dialogflow NLP without going over the network?
Note: Dialogflow API V1 is deprecated and will be shut down on October 23th, 2019.
That means that the official Javascript, native Android, native iOS and Cordova clients will stop working since they all use V1. There's no word if and when these clients will be upgraded to V2.
So the best bet right now is to use the REST APIs.
There are a few things to be aware of when moving from fulfillment that was built for Actions on Google to using this to also provide responses for other platforms. Actions on Google expects the responses to be formatted slightly differently, and if you're using AoG specific characteristics (such as a SimpleResponse object or a Card object), then it might not appear for other Dialogflow integrations. So you'll need to go over your webhook code to make sure what you send back works across platforms. Your logic and the Dialogflow UI builder should pretty much remain the same - it is just your backend that might need some work.
To make the call, as you say, you can either do the REST call yourself or use the SDK built by Dialogflow. While the SDK will be slightly faster, since it is using ProtoBuffs instead of REST, the difference will likely be fairly slight in most cases. If you're planning to stream audio, you will likely need to either use the SDK or your own ProtoBuff implementation because REST doesn't handle that as well. If you're just sending text, and are more comfortable with doing REST APIs, then this is a perfectly reasonable approach.
There is no "local Dialogflow" library. All calls have to go over the network. There are other libraries that do Speech-to-Text and NLP locally if that is what you need.
We're new to DocuSign and have discovered that there are two different C# wrappers for their REST API; GitHub DocuSign C# Client and NuGet DocuSign.Integration.Client.dll. Is one 'more supported' by DocuSign then the other? Is there a preference to one over the other and if so why?
Thank you,
John
DocuSign offers open source API clients that are auto-generated using Swagger. As of this writing Java, C#, Objective-C, PHP, and Node.js are currently supported, but I believe more are on the way.
But yes moving forward DocuSign encourages, recommends, and supports the Swagger-generated API clients and not the previous versions which are deprecated.
Here are the Swagger generated DocuSign Clients:
https://github.com/docusign/docusign-csharp-client
https://github.com/docusign/docusign-java-client
https://github.com/docusign/docusign-objc-client
I found no clues in the developer documentation, but equalify claims that it integrates into the desktop application. They don't offer a free version so I couldn't try it out.
Is it possible/supported to create extensions for the desktop client and is there some hidden documentation available?
I'd be interested in developing one, but so far I had no luck in finding any documentation.
It used to be possible using the Spotify Apps API. I think you can still manually sideload apps, but there is no App Store or similar. Moreover, support for old Spotify Apps is about to be dropped completely in the future.
So no, there's no way to extend Spotify as far as I know.