Now that fmSpark is functionally complete, it's missing something. Specifically, it's missing sample data. We can't simply dump in a list made-up names and addresses and create random data; fmSpark needs data that looks good, by which I mean templates that demonstrate how good your email (and letters and labels) can look using fmSpark.
We've been getting some great questions about fmSpark's features. fmSpark was developed to solve the following problems with merging in FileMaker Pro.
- you want to store your email or letter templates in a database and not in layouts
- you want a send templates
As we get closer to pushing fmSpark out the door there are a few issues remaining to be finished off. Having been in this business for more years than I care to admit, I am nevertheless surprised when beta testers find bugs that were missed during development. No matter how much time you spend with the product, refining and tweaking and bug stomping, there will nonetheless be a few that slip out the door. I'm happy to say that all known bugs have now been squashed and fmSpark will be released shortly.
We've crossed a huge milestone this past week. fmSpark 1.0 is officially in private BETA and I thought I'd step back a little and get you all caught up on the development effort.
First, a huge thanks to the those who have been using version 0.9 in production work, and also to John Sindelar at SeedCode for the tremendous positive prodding a long the way.