[Xapian-tickets] [Xapian] #235: store the sort specification in the option map instead of separate variables

[Xapian]

#235: store the sort specification in the option map instead of separate
variables
---------------------------+------------------------------------------------
 Reporter:  tv+xapian.org  |        Owner:  olly     
     Type:  enhancement    |       Status:  assigned 
 Priority:  normal         |    Milestone:  1.1.1    
Component:  Omega          |      Version:  SVN trunk
 Severity:  minor          |   Resolution:           
 Keywords:                 |    Blockedby:           
 Platform:  All            |     Blocking:           
---------------------------+------------------------------------------------

Comment(by olly):

 I've just been looking at applying this.

 I hadn't thought about this before, but this is a bit problematic if we
 expect these to be usefully modifiable from the template (which I assume
 is the point), the interaction between CGI variables and
 {{{$set{OPT,VALUE} }}} isn't very helpful, and I'm not sure how to avoid
 this.  If they aren't modifiable, it might be better to add new
 !OmegaScript commands as that's
 how similar cases are currently handled.  Or we could add read-only
 options perhaps.

 Are the patches for the Debian list search available anywhere?  I couldn't
 see a link on the Debian list search page.

 I can see that providing more control here would be nice, but a concrete
 example would help me think about this.

-- 
Ticket URL: <http://trac.xapian.org/ticket/235#comment:7>
Xapian <http://xapian.org/>
Xapian