|
DB's Frontier Scripting Site |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| fmp macro |
|||
|
Hello. Welcome to the fmp Macro page for version 1.0b4.
1.0b4 Updated Tue, Feb 2, 1999 at 6:43:37 PM by [email protected] List of bugs fixed in 1.0b4. News Version 1.0b4 fixed an error with fmp.edit(), and has improved documentation on this site. Version 1.0b3 has improved error reporting, and now offers the ability to publish backwards or forwards from a given database with the new "fromEnd" boolean pref. What is it? Its an application of dynamic serving with Frontier's website framework that quickly creates a web interface for FMP databases, gathering the FMP data for you and putting it in the familar adrPageTable for you to use as you wish. Why would I want that? It automates the process of getting stuff out of Filemaker. Imagine that everything that you need from an external database is already in the adrPageTable, waiting for you to format, work with, or ignore...you name it. It either got there from your preset preferences, or was retrieved from searchArgs passed in the URL. Write your own macros with it. Write your own custom rendering scripts, you don't have to be stuck with my idea of what makes a table or piece of data look good. It also puts several macros at your disposal that automate functions like "get next X hits", "get X previous hits", "your search returned X hits" , etc. Because they are in macro form, you control the appearance of the page. Why would YOU want to do that? I put it together because I am always publishing databases for others, and have been through several modes of doing that, including my earlier set of .fcgi scripts for Filemaker, fmp. I knew fmp had some shortcomings, and then I was hit by the thunderbolt of Matt Neuberg's explanation of the .wsf process. It blew me away. I had been doing .fcgi scripting for several years in Frontier, and had always disliked the process of making my own html from scratch. I also made plenty of scripts that no one else could use, because they were so specific to my own applications. He finally made clear to me the power that Userland had put into our hands. If you just use little bits and pieces of data from external databases, this isn't what you want. If you want to represent a database on the web, this is a good way to do it. Email list archives, contact info, problem databases, searchable Help databases, all are good applications for fmpMacro and Filemaker. Using .wsf was really different for me, especially considering that I had only scratched the surface of Frontier's web publishing capabilities before this point. It was an incredible learning process, the stuff that I really enjoy about scripting with Frontier. More about how it works. You can see some functioning examples here, including a searchable archive of ScriptMeridian's mailing list.
|
|||
|
|||
