Both Canon and Nikon have options for uploading photos to different locations via WiFi. Not sure if that could fit into your workflow? On the FileMaker end, you could have something simple like a script in a loop (or an OnTimer) checking the target location for new files every so often.
TWAIN capture is available by a few plugins, like MonkeyBread.
Then you'd just need to find a TWAIN capable digital camera. A lot of photobooths (purikura) use these types of cameras and the same process.
There's a page I found that lists Canon cameras that support TWAIN. It's a bit dated but you get the idea.
Thanks Mike, exactly what I was looking for.
I was a bit too enthusiastic in my previous reply...
Last Twain driver update is from Nov 2013 and when I search Canon for twain-compatible camera's I get only links to the Canon museum, not a good sign. I would be hesitant to build something around software that may be phased out.
Nikon has camera control software from computer, but not sure if this will also allow direct dispatch of the images
Canon has a connect station, but same issue; not sure if this will work.
Before spending a lot of money on a wrong camera, I would like to know if anyone has a set-up like this working.
I made plugins for Xojo some time ago for Nikon and Canon devices.
Both offer an SDK to control them and do a lot of things.
While we could of course write a plugin for FileMaker, the process itself is quite complex (lots of steps), so it may be easier to either write a helper app in Xojo (or C++) and import to FileMaker or at least to a folder.
Or script an app doing that already.
Another way may be to add OS dependent image capture APIs into a FM Plugin to do this.
And I support a solution with multiple WiFi connected cameras and no plug ins.
I simply use Import Records with the Folder option to import images from the folder to which the cameras upload their images. If there's only one camera in use, this is much simpler to set up. I happen to use a windows command line to delete the images from the folder after import, but other methods are also possible.
Good suggestion Phil,
I remember I made something similar using the BEplugin when grabbing files from a machine; run a quick check on file names and file count, which runs in a loop for 60 secs until a new file was detected, then process the new file or bail out of the loop and inform the user.
So for user navigates to the record for which the image is intended, starts the script, takes picture which is immediately processed. As for UX, this is close to a barcode reader set up.
thanks for the feedback, and yes, I noticed from the TWAIN steps in your plugin that this is indeed not a simple interaction.