GitLab

The fix basically works by adding a hidden submit button at the very beginning of the form. Its "name" is the same as for whatever current action is being performed. Thus, when enter is pressed, the same value is passed through.

In javascript mode, this form element's name attribute is poked every time a new element is configured to be correct for that. There is also some special event handling for the search tab of the artefact chooser, so it does not trigger a form submit - just a 'click' event on the correct button.

* In the non javascript version, make sure that request variables are not passed through, which can result in the newly chosen form artefact chooser starting on the wrong page
* In the javascript version, close the old form when opening a new one.

Also, added a 'loading' spinner/message to be displayed while the configuration form is being retrieved.

Use the viewlib functions for building the column HTML. The data has been moved to viewlib.php also.

More progress on the views frontend. There are stubs for several actions, and javascript implementations of those actions.

With javascript, an AJAX request is made to retrieve the new blocktypes. Without javascript, a standard GET request changes which one is displayed. When javascript is on, the radio buttons are not sent back.

Currently contains a bunch of hardcoded data that needs translating into api calls, a javascript overlay file for the rich UI, a CSS file for laying out the UI page, a smarty template for the HTML, and a metric ton of work still to do.