|Subject:||Re: Signature capture via Android and CWS OCX
|Date:||Wed, 16 Nov 2016 09:46:09 -0500
|From:||Jim Moseley <email@example.com>
Liz (and all),
After a little more research, I think I've figured out how to get the
graphic file up to the CWS OCX. I'll just base64 encode it, so it is
just plain text, and then add that as a field to the transaction. This
will greatly increase how much data is being sent, but shouldn't cause
any issues I can think of.
Using your idea, I think I can decode and store these graphic files in
some user-directed folder on the hard drive, maybe split out by year &
month so it doesn't become unmanageable.
The end result of this is to show a report of all signatures for a
client. How would I create a report to show these graphics, if they are
all stored 'outside the database'? Do I read these into a :PRIV:
table's memo/blob fields? Or is there a way to cause the report to
directly display a bunch of graphic files?
If anyone sees any gotchas in this, let me know.
On 11/15/2016 9:05 PM, Liz McGuire wrote:
> I have never done anything like this. If you are able to receive the
> file, I would save it to the OS in a file structure outside the web
> root, in a sub-directory linked to the account, and with a file name
> that is saved with the related transaction (e.g. the transaction Id
> could be the file name).
> For the rest, I have no idea whether you could do that (not even certain
> I comprehend it.
> On 15 Nov 2016 08:05, Jim Moseley wrote:
>> Greetings, all.
>> Has anyone used the Corel Web Server to handle signature-captured BMP or
>> SVG files?
>> I currently have an Android app that ties into the CWS OCX to update my
>> Paradox data directly. But, I don't know what to do with the BMP/SVG
>> files. I don't think I want to save them as Memo/BLOB fields in
>> Paradox, after seeing how easily that can get corrupted. But, if I save
>> them as individual files on the drive, this seems like it would quickly
>> become unmanageable.
>> Any thoughts?
>> Also, how should I setup the CWS OCX to even process these files? This
>> is a sample of my current transaction upload via a POST:
>> Would I just add a new field containing the encoded BMP/SVG contents,
>> and then split that off and 'save' it somehow?
>> Jim Moseley