[FX.php List] Anyone using XSLT anymore?

[DC]

Hi Gjermund,

I'm wondering what a template engine has to do with this at all? Why  
suggest using a templating system?

I'm all for smarty and I use it myself for its template system AND  
its caching mechanisms. But, the problem Bob describes is not one  
that would be helped by using a template system alone - a basic  
template system (without caching) is simply a way for developers to  
keep php code and HTML as separate as possible.

The problem has to do with the speed of FMP when faced with spitting  
out large strings from the database.

Since by all accounts you are an experienced PHP and FX developer, i  
would love to hear more detail about why do you say the proposed HTML  
file hybrid solution sounds "silly"? Is there some fatal flaw being  
overlooked?

dan

On Sep 20, 2006, at 1:40 PM, Gjermund Gusland Thorsen wrote:

> Hmm sounds like your client only needs one field pr layout.
>
> See if that improves speed, to me the solution sounds silly...
>
> There are template engines like smarty, or you could just make a
> couple of php/html templates yourself...
>
> ggt667
>
> On 9/20/06, Bob Patin <bob at patin.com> wrote:
>>
>> I'm using 8.5... but what I'm thinking is that I'll just add a  
>> field to the
>> layout that has the URL to the HTML file... shouldn't add any  
>> overhead, I
>> woudln't think, since all I'm returning from FileMaker is the URL.
>>
>> I may still return some of the HTML from the database; these  
>> reports are
>> made up of about 20 chunks of HTML, and when I return the chunks  
>> the speed
>> is just fine. The problem arises when I have to return all 20  
>> "chunks" in
>> one long report; I may just output the long report to static HTML  
>> and leave
>> the little chunks embedded in the database...
>>
>> At any rate, it's great to see a solution. I'd completely  
>> overlooked the
>> possibility of using a hybrid of static HTML and database... I use  
>> it all
>> the time for photos and such, but hadn't thought about it in this
>> context...
>>
>> Best,
>>
>> 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
>>
>>
>>
>>
>> On Sep 20, 2006, at 11:04 AM, DC wrote:
>> I just remembered that in order for this architectural change to  
>> work you
>> must be using a version of the WPE that lets you return the data  
>> from a
>> layout that is different from your search layout. otherwise there  
>> is no way
>> to stop the HTML field that you want to search from spewing itself  
>> into the
>> XML result. so, this scheme wouldn't work in FMP6.
>>
>> dan
>>
>>
>> _______________________________________________
>> FX.php_List mailing list
>> FX.php_List at mail.iviking.org
>> http://www.iviking.org/mailman/listinfo/fx.php_list
>>
>>
>>
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list