File:  [LON-CAPA] / loncom / TODO
Revision 1.44: download - view: text, annotated - select for diffs
Thu Mar 1 19:42:47 2001 UTC (23 years, 3 months ago) by albertel
Branches: MAIN
CVS tags: HEAD
- finished some XML stuff

    1: + add functionality
    2: & change functionality
    3: * bug
    4: ! January
    5: c Continual
    6: 
    7: G=Gerd
    8: A=Alex
    9: S=Scott
   10: B=Ben
   11: H=Harsha
   12: Y=Guy
   13: N=Hon-Kie
   14: I=Issac
   15: 
   16: XMLPARSE
   17:     + support text_TAG functionality (Y/A)
   18:    !* needs to fixup missing end tags in source (Y/A)
   19:     + style file recursion (Y/A)
   20:     + add <options> tag (A)
   21:     + counters and output formats for counters (A/Y)   
   22:     + support <tag /> or see if new HTLM::TokeParser does <tag/>
   23:     + deregister()
   24:     + register need to take care of overloading, and deregister needs to unload
   25: 
   26: CAPARESPONSE.C
   27:    !+ pass back the reason (Y)
   28: 
   29: RUN.pm
   30:     & ->share() a var rather than pass a parameter? Maybe set 
   31:       a global in the safe enviroment using ->root()?
   32: 
   33: HOMEWORK
   34:     + need to support /OR (Y)
   35:    !+ create <stringresponse> <formularesponse>(Y)
   36:    !+ <hintpart> ?done? (Y)
   37:    !+ <optionresponse> (Y)
   38:    !+ <rbresponse> <oresponse> need to restore last submitted response (Y)
   39:     + <rbresponse> <oresponse> hints need to work (Y)
   40:     & <rbresponse> <oresponse> are ugly (Y)
   41:     & all response types need to be verified about what they do after the answer date (Y)
   42:     + view problem as specific student (Y)
   43: 
   44: /ADM/GRADES
   45:     + modify status of a problem (Y)
   46:     + search for students (Y)
   47:     & find domain of student (Y)
   48:     + handle ambiguous case (Y)
   49: 
   50: NUMERICALRESPONSE
   51:    !* doesn't throw error when #response > #answer (Y)
   52:    !* bad message when #response < #answer (Y)
   53: 
   54: GOODIES
   55:     * bookmarks don't work correctly (B)
   56:     * indexer does not always work (N)
   57:     + messaging (G)
   58:     + chatroom, etc
   59: 
   60: TEX/TTH/TTM
   61:     * Address bugs in tth/ttm (second half January, A,Y,G)
   62: 
   63: BUILD
   64:     * need to roll together anaconda reconfiguration interface (S)
   65:     * need to write a "run-time" teflon script to tighten down (S)
   66:       file ownerships on non-development LON-CAPA machines (S)
   67:     * need to debug anaconda installation interface (S)
   68:     * need to debug anaconda upgrade interface (S)
   69: 
   70: GERD STUFF
   71:     + lecture online converter does all types (G/Y)
   72:     + lond can add UNIX user and change UNIX password (G/S)
   73:     & lond produces no history files for nohist_ namespaces
   74:    !* make spreadsheet calculation less resource intensive (G)
   75:     * tmpget seems to only work up to a few hundred kilobytes (G)
   76:     + pageflip up and down work
   77:     + feedback, mailing and announcement mechanism finished
   78:     + londropadd does XML
   79:     +?TAs can open and close assignments
   80: 
   81: RAT
   82:     + RAT can set resource parameters (G)
   83:     * RAT error line 1413 "insert resource into link" for recon link (G)
   84:     * focus on RAT when in /priv space (G)
   85: 
   86: PUBLISHER
   87:     + publishes material other than HTML, XML and problems (G)
   88:     * handles "publish directory" more gracefully (G)
   89: 
   90: VERIFICATION OF CONTENT
   91:     c have TA's do homework (G)
   92:     c verify internal page links  (G)
   93:     c verify applets (G)
   94:     c do homeworks from home/computer labs (G)
   95:     c be always at least two weeks ahead in homework

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>
500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at root@localhost to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.