| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
gf -server now includes the comment field from the grammar in the
response to /cloud requests with command=ls-t and ext=.json
|
|
The editor doesn't show delete buttons on grammars published by other
users, but it was too picky when deciding which grammars you own. Now
it should be possible to delete grammars from the device/browser
you published it from, even if you don't have a private copy of it any more.
On a related note, there seems to be problem with the way unique grammars
names are created and maintained, causing published grammars to be duplicated
in some cases. This needs to be overhauled.
|
|
This was a problem in Safari (an other similar browsers I presume), but
not in Firefox: hovering over the grammar comment (shown below the grammar
name when you edit a grammar) didn't reveal the button to edit it, thus
preventing you from adding a comment. It was till possible by selecting the
"Enable editing on touch devices." at the bottom of the screen, but most
people probably didn't notice that it is possible to add a comment.
|
|
There is also a menu so you can choose to sort the list by name or by age
|
|
gfse/editor.js had its own list with 34 languages, while js/langcode.js
only had 30 languages. The missing languages have been added to
js/langcode.js and all apps now use that list.
|
|
|
|
|
|
Minibar needs js/langcode.js now, so need to include it in gfse/index.html
and syntax-exitor/editor.html too.
|
|
|
|
|
|
|
|
(Also fixed a broken link in gf-web-api-examples.html)
|
|
|
|
|
|
+ The syntax editor is now accessible from the Simple Translaton Tool.
+ The minibar now automatically provides access to the syntax editor (provided
the necessary JavaScript files and style sheets have been loaded).
+ Preparations for making the syntax editor accessible from the grammar editor.
|
|
Also move the functions title and attr from editor/editor.js to js/support.js.
Also mention recent changes in minibar/about.html.
|
|
|
|
To make definitions that span multiple lines more readable in guided mode,
preserve line breaks and indentation when lin and oper definitions are
displayed and edited in guided mode.
Bug fix: moving the cursor by clicking and selecting text by dragging did
not work in textareas and input fields, because those mouse event were
intercepted by the sort-by-drag-and-drop handler.
|
|
|
|
|
|
apps
Aarne says the Chinese resource grammar is complete, but not yet completely
correct.
|
|
Also fixed two small problems with public grammars.
|
|
|
|
This helps avoiding problems if an inherited grammar is renamed, or if there
is more than one grammar with the same name.
|
|
Avoid showing a blank page if there is an unexpected problem with the grammars
in localStorage.
|
|
|
|
the row view
Functional programming is easier than imperative programming!
|
|
|
|
When adding a new function, you can enter a linearization for one language
and then copy it to the other languages with one button click.
|
|
|
|
|
|
views
|
|
Accessed by clicking on a function in the Abstract column in the matrix view.
|
|
+ You can click on a column header to switch to column view (i.e. the
corresponding abstract/concrete syntax tab).
+ The categories and functions in the abstract syntax can be edited directly
in the matrix view.
|
|
|
|
missing
|
|
|
|
+ Added "Symbolic" to the list of resource modules that can be opened.
+ Clicking on the name of an opened resource module now displays the list
operations it provides. (Implemented using show_operations in the GF shell.)
+ Added a GF version info link to the cloud service start page.
|
|
|
|
|
|
Move the gfse-specific list of sortable tags and class names from sort.js
to editor.js.
|
|
|
|
* Update Setup.hs to build Japanese by default.
* News item about Japanese on the home page.
* Add Japanese to the supported RGL imports in the grammar editor (gfse).
|
|
The grammar extension is now done with a regular HTML form, so you can use the
TAB key to move between the fields and press ENTER to submit the extension when
you are done.
TODO: more immediate error feedback
|
|
It works OK now, but it could be better, e.g. the number of mouse clicks
required to enter an extension could to be reduced...
|
|
There are still some user interface wrinkles to iron out.
|
|
|
|
localStorage
|
