Let’s talk about image size (again). But this time in the context of data capture. We have this wonderful image field that allows your users to attach image files to their form. This is great. but it’s also scary. You likely don’t want to use this for the 10MB images that came straight from their digital camera. Consider that these images will be base64-encoded and inserted with the rest of the form data — and stored in the PDF. You want to limit them to images that are reasonably sized.
Today’s sample has an image field with a validation script that checks the size of the loaded image. For an image field, field.rawValue will return the base64 value of the embedded image. The length of that string will tell you how big the image is. My validation script does a rough conversion — image size is roughly 3/4 the size of the base64 string. If that size is greater than your threshold you can choose to either reject the image (set the field to null) or simply mark the field as invalid.
There are a couple of other resources I should point you torward. First of all, Niall O’Donovan has posted a nice blog entry describing new features in Designer 10:
http://www.adobe.com/devnet/livecycle/articles/top-10-adep-designer-features.html. You might recognize Niall as a regular contributor on the Designer forums. He’ll be one of the experts you can meet at MAX next month where he will be doing a session on Designer.
Then, one of our own, Ragavendra, has a blog focused on the server side of forms and output:
http://blogs.adobe.com/foxes/ . In particular, you might find this entry interesting:
With the latest verson of ADEP, it is now possible to create bookmark references for your dynamic forms.
It’s been quiet here. I have been mostly heads-down preparing for MAX. I hope I’ll see many of you there. If not, the content I’m working on will eventually find its way to this blog.
But today the focus is on some things to get you further ahead with macros.
I’ve included a zip file with the following:
- updated lint check macro
- updated accessibility checker macro
- updated form report macro
- sample macro to use as a ‘starter’ for new macros
You can simply unzip this file under your Designer install directory and they should immediately work.
If you’re writing new macros, you should appreciate sample.js. It includes:
- A convenience method for emiting messages to Designer’s log panel
- A convenience method for recursively iterating over the contents of your form
- A ‘catch’ block that does a good job of reporting script errors in your macro.
Have a peek at the comments in the macro for more details.
In full disclosure, I admit that one of the reasons for updating these macros is that I found a couple issues where old macros didn’t work in the new version of Designer. But not to worry, there are workarounds available and the new versions of these macros work even better than the old ones.
I’d like to extend this to more of the XFA object model, but that’s a project for another day.