<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<tt>Well back years ago I wrote one output that used the HTML format
and the only way to make it sensible was to create the HTML
document the way I wanted it and reverse engineer to the filepro
code. Filepro would add tags when it should not and did not have
any complex options for some tags. That was a pain in the behind.<br>
<br>
Then I found XSL and XML. XSL allows you to create a proper HTML
document with logic to insert the data from an XML document. In
my brain it worked very much like filepro, when you create an
output page and put in field numbers. It made a nice looking
page, since you had full access to CSS and XSL and all the stuff
for HTML pages. Then all filepro had to do was generate the XML
file and you run a program that combines the XML with the XSL
stylesheet. I have found this easy to do.<br>
<br>
On the PDF stuff, I have not had an opportunity to use filePro's
output to PDF and more often I have had to develop ways to convert
between PCL, TIF, PDF etc. Taking documents apart and rebuilding
them. This is well outside the capabilities of filepro and I am
not sure I will need the filepro to PDF tools any time soon.<br>
<br>
Nancy </tt><br>
<br>
<div class="moz-cite-prefix">On 8/17/2020 2:59 PM, Jose Lerebours
via Filepro-list wrote:<br>
</div>
<blockquote type="cite"
cite="mid:93da32c2-5c17-f27e-812a-f0b8f1d7c83f@gmail.com">Just
wondering how often and how many of you push HTML/PDF documents
out
<br>
of your filePro application.
<br>
<br>
Do you use filePro native syntax to produce HTML? How complex are
your
<br>
HTML documents?
<br>
<br>
For what I have noticed, PDFs are very much in the tank since
filePro has provided
<br>
native drivers (or so it seems) to print PDF documents. I wonder
if the community
<br>
in general is OK with its limitations (please share what these are
in your case, if you
<br>
wish) have driven you to utilizing other means to produce your PDF
documents as well.
<br>
<br>
I once wrote a PHP script to parse filePro screen and produce the
HTML form matching
<br>
the screen. It took a couple of hours but I was trying to show a
friend of mine how simple
<br>
it would be to replace his screen scraper and simply show exactly
what he has, replicate
<br>
every screen and write the code to query through his filePro
files.
<br>
<br>
We ended up developing the entire thing in SQL because of
scaleability cost and a few other
<br>
reasons he came up with ... don't ask me, I was just writing the
code. ;-)
<br>
<br>
Regards,
<br>
<br>
<br>
<br>
_______________________________________________
<br>
Filepro-list mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Filepro-list@lists.celestial.com">Filepro-list@lists.celestial.com</a>
<br>
Subscribe/Unsubscribe/Subscription Changes
<br>
<a class="moz-txt-link-freetext" href="http://mailman.celestial.com/mailman/listinfo/filepro-list">http://mailman.celestial.com/mailman/listinfo/filepro-list</a>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Nancy Palmquist MOS & filePro Training Available
Virtual Software Systems Web Based Training and Consulting
PHONE: (412) 835-9417 Web site: <a class="moz-txt-link-freetext" href="http://www.vss3.com">http://www.vss3.com</a>
</pre>
</body>
</html>