yes, absolutely right.
You can´t for example write a UTF8 ics calendar file for iCal without using a Plugin or XML.
Great post Doug. Part of the need to take web interface and methods seriously series...
<<snip>>Do you agree that the Export Field Contents function having the ability to control export to UTF-8, complete with determining the appropriate line endings and BOMs would be a useful feature for FileMaker Pro in these days of the Internet?<<snip>>
YES YES YES ... and, oh, by the way, YES!
I long ago abandoned the native Export in favor of writing my own files via Troi File. Yes, this is a plug-in, but these days (for for years now) I find that every application I create needs at least one plug-in to handle some shortcoming or another. So I quit fighting for "all native" a long time ago. (I need to upload containers from a web site, I need to talk to a WSDL, I need to extract data from a PDF, I need to push data to Outlook or Address Book contacts or pull data from QuickBooks, I need context-senstitive pop-up menus to eliminate extra steps for the users ... the list goes on and one.)
If I were to lobby FileMaker for more "native" functionality, I would ask for functions that allow creating, reading, writing,renaming, copying, and moving non-database files. In other words, I would love to have built-in the functionality that Troi File (and a half dozen other excellentplug-ins) provide to interact with other real-world objects (files). That way, no matter how the web (and the world) evolve, we could always create interface files in the format needed.
Just my $.02 ... ;-)