Geoff Bowers wrote:
> Yeah.. we're always debating whether certain lists should be LI or
DD/DT based.

I've tried to find some form of best practice via the web standards
group (to no avail) but seriously I think the DL method (as per Mollio)
is the best implementation for result lists; it allows for an arbitrary
number of DT/DD entities - it also fits in very nicely with the extended
metadata information via your displaysearchresult.cfm template
technique.

Cheers

David

-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
On Behalf Of Geoff Bowers
Sent: Friday, 19 May 2006 5:38 PM
To: [email protected]
Subject: [farcry-dev] Re: Using Friendly URLs in Search results


David Whiterod wrote:
> Are your displaysearchresult.cfm templates doing a getData operation 
> on each returned object to get the extended metadata (author etc)? 
> Does this have performance implications (In 3.0.1 does fourq instance 
> cache up running?)

Yeah there is a getdata() per result.. so displaying 10 results will
result in 10 additional lookups for the page.. but its not that much of
a performance hog.

3.1 will have the objectbroker technology in place which should be ideal
for quashing these sorts of db-lookup hungry activities.

>> We're using UL/LI rather than DL/DT/DD with H3 for the title.
> 
> I saw the DL/DT/DD combo in Mollio - I think this is a really good use

> of those tags.

Yeah.. we're always debating whether certain lists should be LI or DD/DT
based.

-- geoff
http://www.daemon.com.au/
--
Message protected by MailGuard: e-mail anti-virus, anti-spam and content
filtering.
http://www.mailguard.com.au/mg





--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"farcry-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/farcry-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to