Actually, you can dispense with the HTML stuff. The 'data:' protocol doesn't
need it. It's intended for smaller snippets!!
"data:text/html," & GetAsCSS(yourFieldName)
The GetAsCSS function, while not perfect, should push out
"html-like-css-somewhat" code and include fonts, bolding, other field-type
formatting.
As I said, not perfect. But try it an see if that works for you.
--
Beverly Voth Tier3 Data & Web Services Group, LLC
606-258-7399 http://www.tier3web.com/xml.htm
Web Design & Hosting * Apple: CAN, ACN & ADC
Certified FileMaker 7 & 9 Developer * FileMaker Business Alliance
Coldfusion, Witango, PHP, MS SQL, MySQL, FMP, XML/XSLT, CSS
Over 15 years experience integrating databases and the internet!
On 7/31/09 2:33 PM, "Miki Eff" <[email protected]> wrote in whole or in
part:
> Hi Brad,
>
> Yes, you can make the webviewer display html data that's generated on the
> fly by filemaker. You can even you a Let statement to define all the fields
> that are referenced in your html, with all the filemaker tools. All you need
> in the webviewer calculation window is valid html.
>
> "data:text/html,<html>
> <head>
> </head>
> <body>YOUR FIELD STUFF
> </body>
> </html>"
>
> With CSS and a good sense on XML generation with your data, the
> possibilities are large. Of course there are many FM developers that don't
> see the sense of the work involved in HTML when Filemaker provides adequate
> tools.
>
> Hope this is helpful.
>
>
> On Fri, Jul 31, 2009 at 7:23 PM, Brad Lowry <[email protected]> wrote:
>
>> Hi All again,
>>
>> Since I got such a great response from my last WishList I am going to post
>> another.
>>
>> Again, I hope that this is possible and that I am just ignorant of how to
>> use the WebViewer or ignorant of an Elegant Workaround or even an inelegant
>> Kludge.
>>
>> WishList: be able to point a WebViewer window to the content of a field and
>> have its content render as html.
>>
>> I think it would be useful even if I just wanted to use HTML's tools to
>> display a bunch of data as HTML formatted text (1. Which values and the
>> manner in which I display the data is more able to be dynamically altered
>> without any Layout changes. 2. It allows separation of Code and Display at a
>> "middle tier" between the data and the layout.)
>>
>> Further, it could get really fancy.
>>
>> I could have a Web Form built within a text field by script. I can build it
>> so that many, many data fields autopopulated. I can have certain values as
>> html hidden fields (business rules say include that data in the form, but
>> you don't want the end user to know it (SS#, TaxID, Chart Number, Diagnosis
>> Code). And I can limit selections in drop-downs based on User Access
>> Privileges. Then have the Submit button send it off to any B-to-B vendor, or
>> service, or billing entity or... Another great advantage is that I can save
>> the html of that submitted form in its entirity to a table of Submitted
>> Forms as a logging mechanism.
>>
>> As it is now the only Kludge I can think to use is the very FM6-ish: Write
>> the file to the desktop (or other local folder) and launch it with your
>> browser.
>>
>> (Indeed, I did just this in FM6 with great effect. Some sites have gotten
>> sophisticated and won't accept a form submission from an "outside source",
>> but when I contacted the web guy at the target site and explained my purpose
>> [and that my client was a really good customer of theirs] we agreed on
>> another Hidden value I could pass in the form that would expire every three
>> months that would allow an exception to that block.)
>>
>> Of course, while FileMaker is at it, they should add the ability to open a
>> local (non-served) html file. However, this is only as an obvious
>> enhancement between only served files and field content -- if I could render
>> field content I can't think of a good use of opening local files.
>>
>> Just my two cents...
>>
>> Thanks for any replies.
>> --
>> Sincerely,
>> Brad
>>
