Signed-off-by: Francois Marier <francois@catalyst.net.nz>

The 'default' theme is to come back shortly.

Strips down the default theme to a very bare minimum, to allow better theming.

The next commits will move this theme to 'raw', and commit a new default theme that looks mostly like the old one.

More work on profile views and three new blocktypes (myfriends/mygroups/myviews) to emulate current profile page TODO: - write wall blocktype - change install default profile view hook to add blocks - upgrade path (xmldb & migration) - blocktype and category and singleblockperview implementation

    - TESTING

* A more neutral colour scheme, appropriate for a default installation
* Forms are layed out with the title beside the inputs
* The profile page is in tabs
* Layout is cleaner and clearer
* Still will be some bugs, especially in IE!

changing view layout to be a two step process for users with editing columns on view/blocks turned off

changing the 'change view layout' link on view/blocks.php to 'change my view layout', and removing the confusing image

adding confirm dialog to cancel with new view, and cancelling now deletes the partially created view

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.

Add a spinner to the loading message, since I seem to be staring at the loading screen more often...

Renamed the 'view' parameter for view/view.php to be 'id'. 'view' will continue to work for a while.

view/blocks.php uses id, and id is used for other objects in the system, so it doesn't make much sense for this one to remain this way.

* 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.

Make sure that 'new' is passed around in some other places where it is needed, so the wizard works. Also fixed a couple of broken redirects for the non javascript version