| Age | Commit message (Collapse) | Author |
|
metavariables as well
|
|
|
|
we are not in silent mode. This was changed incidentally on the way.
|
|
stack overflow for large search spaces
|
|
|
|
|
|
|
|
otherwise we force the exhaustive tree generation to be strict
|
|
command in the shell
|
|
|
|
generated from the parser
|
|
work unless JavaScript is enabled
|
|
dependent types
|
|
|
|
same monad in PGF.Forest.getAbsTrees
|
|
|
|
|
|
solutions found
|
|
functions now return both the generated tree and its linearization
|
|
|
|
|
|
in the types
|
|
types
|
|
|
|
|
|
|
|
|
|
after each solution
|
|
in the abstract syntax
|
|
|
|
|
|
|
|
|
|
|
|
|
|
broken. It will be fixed with the next patch
|
|
pressing enter in between
It mostly works now, but some minor issues still need to be fixed.
|
|
|
|
|
|
Added a meta tag to specify that the file is in UTF-8. This makes the browser
(at least Firefox) assume that the JavaScript files are also in UTF-8, it seems.
Moved the call to start_minibar() from the <body onload="..."> to the end of
the file. The onload action is not executed until all images in the document
has been loaded, while javascipt at the end of the file is executed as soon
as the HTML file has been loaded. (Calling start_minibar() from the head of
the document would be too soon, since it refers to elements in the body,
which hasn't been loaded yet.)
|
|
When pfg-server servers a static file in HTTP mode, it is output as is, so
specifying charset="iso-8859-1" could be wrong.
Note: the a charset can be specified with a meta tag in HTML files,
e.g. for files in UTF-8:
<meta http-equiv="Content-type" content="text/html;charset=UTF-8">
|
|
|
|
Still not quite stable.
|
|
|
|
supported in GF
|
|
|
|
enter if it matches one of the possible completions exactly
The current word is also accepted if there is only one remaining possible
completion.
|
|
|
|
|
|
It is needed for the userLanguage field in the grammar info from pgf-server
|