All index entries say where they point to. This information is all
you need to give good feedback when a student asks. This is the most
important area of improvement for now, and I would like this to be
done -- ideally in time for the fall semester. I don't see why it
shouldn't be doable -- Matthias
On Apr 17, 2009, at 4:13 PM, Eli Barzilay wrote:
On Apr 17, Matthias Felleisen wrote:
Why don't you start with these guidelines:
context = TL + tp(1) + ... + tp(n)
The first page must contain only:
(1) all query results that concern tp(i)
(2) all results concerning TL
(3) tp results appear BEFORE TL results
[(4) we might also wish to order results so that those for tp(j)
occur before tp(i) if j > i]
All other results appear on pages 2 and up.
I suspect you can scale these rules to #lang scheme/gui and friends.
I just wish we had scheme/redex.
I'm guessing that by "TL" and "TP" you mean "Teaching Language" and
"Teachpack". The index entries are *not* divided onto these -- this
thing is working from the plain index nothing more and nothing less.
I don't see any reason to add any kind of specialization for the
teaching languages and teachpacks -- since the same issues are
relevant in all other languages too.
It is the responsibility of teaching language to generate a query that
will narrow down the full index to the relevant index -- and this
should be done by a "context query". There are search operators that
make it possible to write a query that shows only entries from some
manual or that are provided from some module -- but in your suggested
organization you do hit the two big problems that I mentioned many
times now: you're describing a query that uses `or', and you're
describing a query that changes the order of results.
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli
Barzilay:
http://www.barzilay.org/ Maze is
Life!
_________________________________________________
For list-related administrative tasks:
http://list.cs.brown.edu/mailman/listinfo/plt-dev
