Graphometric Signature Android library - signature

Are there any libraries about Graphometric Signature for Android platform? I found only Olivetti toolkit, but I would use a free library for my Android App.

you can try Namirial S.p.A. solution.
http://www.graphosign.com/
http://www.firmagrafometrica.it/
You can use the Namirial solution with Windows, Android & iOs.
They also provide an sdk for the all platform.
For more information you can send an email to: info#graphosign.com

I've got the same task last year. The one which looked best is http://www.signotec.com/internet/page.php?naviID=900000026&site=900000025&typ=2&s_sprache=en but it's not free at all.
Some others:
http://www.xyzmo.com/en/products/Pages/digital-signature-ipad-android.aspx
http://www.androidpit.de/de/android/market/apps/app/com.xyzmo.signature/SIGNificant-E-Unterschrift
http://www.binarysolutions.biz/2010/12/signature-capture-for-android.html
http://www.supersignature.com/default.aspx
http://www.gocanvas.com/content/blog/post/create-your-own-android-mobile-app-with-signature-capture-in-5-minutes
https://play.google.com/store/apps/details?id=AB.AN&feature=search_result#?t=W251bGwsMSwyLDEsIkFCLkFOIl0
https://play.google.com/store/apps/details?id=com.rockalldesign.signaturesaver&feature=also_installed

Related

macOS cannot verify the developer of "clang"

I updated to macos-catalina and I am trying to crosscompile c++ code for android using android-ndk-r18b
macOS cannot verify the developer of “clang". Are you sure you want to open it?
It asks me for all different executables/compilers (e.g arm-linux-androideabi-ranlib). I got around this by got around it by going to Security & Privacy and allowing all executables that show up there. Is there a more generic way to authorize everything within the android ndk?
Open `System Preferences/Security & Privacy/Developer Tools.
Allow Terminal app to run software locally that does not meet system's security policy
This was essentially answered in the comments by Dan Albert, but to add an actual answer, as per android ndk issue 1060:
For macOS, the SDK manager is the most reliable method of acquiring the NDK for most use cases and should be preferred until something else changes. That is not viable for all users, but if it is an option for you that's your best option.
In other words, if you install/reinstall an NDK using SDK manager, you should end up with a version that gatekeeper will be happy about, e.g.:
android/Sdk/tools/bin/sdkmanager --install "ndk;18.1.5063045"
The best way is to update the ndk to R21. if your Macos version is catalina.
"No Mac NDK before NDK r21 was signed or notarized."
Download and install the Mac App Bundle version of the NDK available since r21 from this page.

Visioglobe map and Metaio AR with Xamarin

I want to use these tools with Xamarin
Visioglobe 3d maps
Metaio SDK for Augmented reality
they are working well with native android and iOS apps.
And I would like to know if we can use these tools with Xamarin, Does xamarin support them?
And how to integrate a Xamarin app with them.
[DISCLAIMER] I'm an engineer at Visioglobe.
You've probably moved on already, but I'll reply anyway in case someone else is interested.
To this date, there is no indication, either way, that Visioglobe's VisioMove SDK will work with the Xamarin platform.
If you have already chosen Visioglobe for your application's map, then I would suggest strongly to use the traditional IDE's to reduce any risk of potential conflicts.

Xamarin licensing issue (can I use specific component)

I saw this SO question asking for a PDF viewer for MonoTouch, which is just what I need. First I tried the Xamarin code sample suggested by poupou, but this needs a lot of extra work to use. So I decided to try the mTouch-PDFViewer suggested by Alex.
So I went to the download page and on to the GitHub for this component and cloned the repository. The problem is that the Visual Studio solution opens with a message saying I need a different license for Xamarin than I have. I only have a Xamarin Indie license and am therefore not able to build this library.
Is there a way around this? If I copied all the code into the Xamarin Studio, would it work then or can't I use this component at all due to licensing problems? Will it work in the app as long as I get hold of the dll file or do I need the more expensive license?
I have sent an email to the support email address for the mTouch-PDFViewer asking if the dll is available somewhere, but I was wondering in general if the licensing limits the use of dlls or just the ability to compile the code.
Indie license does not have Visual Studio support. An Indie license requires you to use Xamarin Studio on a Mac. There should not be any restrictions on using specific components.
Also, for basic PDF viewing, iOS has excellent built in support, which you might try before using a 3rd party component.

AsyncBridge.portable for Xamarin.ios

I created application with mvvmcross and I want to target WPF, andoid and ios.
I used task and async/await in my core PCL library.
It works with WPF and Android because I use Microsoft.Bcl.Async and AsyncBridge.Portable from Daniel Plaisted.
My problem is with ios version because Daniel not implemented AsyncBridge.Portable for ios.
I would like to know if someone maked it or if someone know where I can find source code of AsyncBridge.Portable of Daniel ?
If Daniel, you sees this post, can you explained me how can I make ios version ? :)
Thank you
You can find the source code here. From that, you may be able to just adapt the Android code to work on iOS.
However, official Xamarin PCL support is coming soon (-ish), and that may change how you need to do this (or make it so you don't need to do it at all).

Running J2me apps on Android phones

Is it possible to run J2ME apps on Android phones? If so, what is the installation procedure?
Otherwise, is it possible to convert .jad files to .apk? In this case, what is the procedure.
(I have already tested the procedure offered by netmite but it doesn't seem to work.)
Using this site http://www.netmite.com/android/srv/2.0/getapk.php you can convert your J2ME application in to Android Application. You need to just supply your .Jad & .Jar file in it and it will generate Android's executable file .apk for you.
However in it doesn't able to convert all the feature of Java ME to Android, but basics can be easily converted.
You can try phoneME, netmite j2me app runner, jblend, jbed like jeme emulators in android. For now, phoneME is the best. you can get various version of phoneME here http://davy.preuveneers.be/phoneme
You also need OI file manager to select files in phoneME.
A complete guide can be found here http://w3epic.com/run-java-apps-j2me-on-android-devices-guide/ for rest of other emulators (if you want to try).
#dennis
I got it, thanks.
MicroEmu open source project hasn't been mentioned yet, and here it goes: https://code.google.com/p/microemu/
I searched for a good JavaME emulator for Android for a long time, and finally found one. This here is what you need:
http://davy.preuveneers.be/phoneme/
No doubt the best there is for Android.
Added 15th January 2016:
Reply from the author of phoneME, Davy Preuveneers, in regards to the Android 5.0+ issue commented by Álvaro Gutiérrez:
Hi,
I am testing on a Samsung Galaxy S4 running Android 5.0.1, and the
"phoneME Advanced - Foundation Profile + MIDP FullHD Resolution" build
seems to run just fine on this device.
Also, following this thread
Position Independent Executables and Android Lollipop,
I ran:
$ readelf -l libcvm.so | grep -i "file type"
and it reports:
Elf file type is DYN (Shared object file)
So according to the website this is OK.
However, for the CDC and Foundation profiles (console like
applications), there is indeed an issue where you get this error:
"Error: only position independent executables (PIE) are supported"
However, for those 2 profile I call a native executables and redirect
the native stdout/stderr streams to Android, whereas for the MIDP dual
stack I load a library and create a complicated wrapper to get things going.
I can recompile with -fPIE and -pie options but will then end up with
binaries that are no longer backwards compatible with devices running
Android 4.0 and below. That is why I added some additional builds to my
website for Android 5+ devices:
http://davy.preuveneers.be/phoneme/?q=node/10
Best regards,
Davy

Resources