[FX.php List] Anyone using XSLT anymore?

Gjermund Gusland Thorsen ggt667 at gmail.com
Wed Sep 20 12:06:15 MDT 2006


I believe the biggest proble is that your are using Word as a
generator for HTML... Please try to download NVU( free WYSIWYG HTML
editor ) and make the same page in Word and NVU check the difference
in size.

ggt

On 9/20/06, Bob Patin <bob at patin.com> wrote:
>
>
>
>
>
> Hmm sounds like your client only needs one field pr layout.
>
> No, that won't work. The data needs to be separated by 18-20 different
> topics, which are sometimes pulled up separately. The 18-20 topics also need
> to be displayed at once as well.
>
>
>
>
>
>
> See if that improves speed, to me the solution sounds silly...
>
> I tried that; the problem is that when I tried to pull up all 20 pieces of
> the report, the speed was too slow. The HTML sometimes stretches into 3-5
> pages of HTML, containing several tables and a couple of photos.
>
> I tried everything; I separated the different topics into separate layouts,
> which I use when they do a query for a single topic within the whole report.
> This works great; the speed problem occurs when they do a full report, and
> unfortunately this is the most-used report on their site.
>
> I don't find the solution silly at all. It's the same way that I always deal
> with photos in FileMaker; I store the photos externally and reference them
> with a calculated URL field. The problem in this case isn't the number of
> HTML files, it's the problem of maintaining a set of a half-million HTML
> files, all of which have to updated several times each year. In this case,
> my client will never see the HTML files; he'll run a single script on the
> database that'll import his data from his local copy, then run the script
> that'll generate the static HTML files. Speed will be excellent, I'll be
> able to cache his site, it'll all be a thing of beauty.
>
> The whole problem is that the data comes from Word documents, and there's no
> way around this. We long ago realized that the easiest thing was to convert
> the Word docs to HTML (which Word does itself), run these thru a parser that
> I wrote in Visual Basic, and then serve them up. I'll re-write the VB parser
> so that it now will generate a tab-delimited file, which we'll pull into
> FileMaker; then FileMaker will make the HTML files while it generates a URL
> for each file so that it can include them in PHP pages.
>
> Bob Patin
> Longterm Solutions
> bob at longtermsolutions.com
> 615-333-6858
> http://www.longtermsolutions.com
>
>   CONTACT US VIA INSTANT MESSAGING:
>      AIM or iChat: longterm1954
>      Yahoo: longterm_solutions
>      MSN: tech at longtermsolutions.com
>      ICQ: 159333060
>
>
>
>
>
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
>
>
>


More information about the FX.php_List mailing list