3 ms·

Did you happen to look at http://willowsystems.github.io/jSignature/ http://willowsystems.github.io/jSignature/ ? I'm wondering what oppositions you had to the

by vonseel 13y ago

Did you happen to look at http://willowsystems.github.io/jSignature/ http://willowsystems.github.io/jSignature/ ? I'm wondering what oppositions you had to their plugin, if so. I looked at Thomas Bradley's plugin, tested it in a client app, but ended up going with jSignature as the base64 such could be posted as form data, converted as necessary, and placed in a LaTeX template that was converted to PDF. Note that my client was aware this was not a valid "e-signature", but they wanted a simple solution that appeared valid and large contracts would require paper signatures anyways.

oijaf888 13y ago
Why wouldn't that be a valid e-signature? Previous comments have said that a valid e-signature is (essentially) anything adopted by the person with intent to sign the record.
- vonseel 13y ago
  It's been several months so I may be wrong, or perhaps I am thinking of a different regulation, but I was under the impression electronically signed documents required an audit trail, and that the signature could not be modified post creation of the document.
ricardobeat 13y ago
That also seems to use linear interpolation, giving signatures the 'wiggly' digital look.
ezl 13y ago
I did look at it. It was my second choice and I would have used that if I didn't used Thomas Bradley's. I emailed Thomas Bradley when I was exploring options and he responded within an hour. Also, that repository was active (TB was responding to bug reports and there had been commits on the day that I looked) and had more followers and forks. Since I'm a mediocre hacker, I generally optimize for paths where I can get the most support if I think I might need it. Thomas's is also very well documented with specific code examples and demos for the basic use cases. I considered a lot of different options, including signature as a service (https://www.signature.io/ https://www.signature.io/ -- these guys have a beautiful implementation), integration with other companies (hellosign and signnow are my favorites, docusign/echosign), but TB's was just the best fit for my needs at the time.

by vonseel 13y ago

oijaf888 13y ago

Why wouldn't that be a valid e-signature? Previous comments have said that a valid e-signature is (essentially) anything adopted by the person with intent to sign the record.

vonseel 13y ago
It's been several months so I may be wrong, or perhaps I am thinking of a different regulation, but I was under the impression electronically signed documents required an audit trail, and that the signature could not be modified post creation of the document.

ricardobeat 13y ago

That also seems to use linear interpolation, giving signatures the 'wiggly' digital look.

ezl 13y ago

I did look at it. It was my second choice and I would have used that if I didn't used Thomas Bradley's. I emailed Thomas Bradley when I was exploring options and he responded within an hour. Also, that repository was active (TB was responding to bug reports and there had been commits on the day that I looked) and had more followers and forks. Since I'm a mediocre hacker, I generally optimize for paths where I can get the most support if I think I might need it. Thomas's is also very well documented with specific code examples and demos for the basic use cases. I considered a lot of different options, including signature as a service (https://www.signature.io/ https://www.signature.io/ -- these guys have a beautiful implementation), integration with other companies (hellosign and signnow are my favorites, docusign/echosign), but TB's was just the best fit for my needs at the time.