[developers] [oe at ifi.uio.no: changes to on-line MT and parsing demo code]

[Stephan Oepen]

hi berthold,

> having discovered that the generation feature is now part of the LKB web
> demo, I would like to create an updated demo with the current version of
> GG. 
> 
> I'd be happy, if someone could give me a bit of information beforehand: 

  [...]

the message below, hopefully, should answer all your questions.  if you
roll suibable `gg.html' and `gg.js' files, i would be happy to include
those, an up-to-date copy of GG, and `--gg' support in the LOGON `www'
script for our next release (expected in the second half of august).

                                                        cheers  -  oe

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++ Universitetet i Oslo (IFI); Boks 1080 Blindern; 0316 Oslo; (+47) 2284 0125
+++     CSLI Stanford; Ventura Hall; Stanford, CA 94305; (+1 650) 723 0515
+++       --- oe at ifi.uio.no; oe at csli.stanford.edu; stephan at oepen.net ---
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


[--- start of forwarded message ---]

Date: Wed, 13 Feb 2008 18:25:07 +0100
From: Stephan Oepen <oe at ifi.uio.no>
To: developers at delph-in.net
Subject: changes to on-line MT and parsing demo code

hei!

there used to be separate code for on-line web demos of just parsing or
running the full MT pipeline.  i know at least berthold has created his
own variant of the ERG demo code, and i remember others were interested
in doing the same.

i have recently consolidated the code for on-line demos, pulling things
back together, adding functionality to the parsing demo, and making it
possible to customize for various grammars without code changes.  there
are two examples of this new setup here (temporarily for the SRG):

  http://erg.emmtee.net/
  http://srg.emmtee.net/

the downside of these changes is that the new on-line demo requires the
same inventory of tools as the full MT demo, hence is supported as part
of the LOGON tree only (which one might think of as a DELPH-IN distro).  
it requires about three gigabytes of available disk space, but i expect 
anyone wanting to run an on-line demo of their grammar (or MT pipeline)
should be able to find the necessary resources :-).

i would like to ask those of you with uncommited changes to the on-line
demo code (howdy, berthold and francis) to work with me on integrating
your changes into the main tree.  you can take a peak at the LOGON tree
(which we are about to announce publicly) as follows:

  svn co http://svn.emmtee.net/tags/topp topp
  cd topp
  LOGONROOT=`pwd` ./www --binary --erg --port 8888

the above should result in an on-line web demo at port 8888 of your web
server.  note, however, that many firewalls block access to user ports,
so at least for external access you may have to talk to the IT crowd; i
recommend wrapping a proxy web server around those demos, which is what
drives the `erg.emmtee.net' et al. addresses.

my current theory of customized demos, say for JACY, would be to:

  + add a command line option and startup code to the `www' script;
  + create two additional files for each grammar:

    lingo/lkb/src/tsdb/html/jacy.html
    lingo/lkb/src/tsdb/js/jacy.js

for grammars that are part of the LOGON tree anyway, i will be happy to
include those additions in SVN.  berthold and francis, please feel free
to email me your input (dan and montse, feel free to request changes to
what is there currently).

the former `www.system' and `lingo/lkb/src/www/' are thus deprecated; i
plan to remove them from the CVS head revision in the next few months.

                        i hope the above makes sense?  all best  -  oe

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++ Universitetet i Oslo (IFI); Boks 1080 Blindern; 0316 Oslo; (+47) 2284 0125
+++     CSLI Stanford; Ventura Hall; Stanford, CA 94305; (+1 650) 723 0515
+++       --- oe at ifi.uio.no; oe at csli.stanford.edu; stephan at oepen.net ---
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

[--- end of forwarded message ---]