- 02 Dec, 2007 9 commits
-
-
Nigel McNie authored
-
Nigel McNie authored
-
Nigel McNie authored
Remove acceptance of path parameter, not needed any more. Shorten the defining of the TITLE constant.
-
Nigel McNie authored
In particular, finally, the name of the user is linked to their profile page, which should surely help discovery of their profiles, given it's the main way that people see one another's content.
-
Nigel McNie authored
Removed the buggy old way of generating an artefact hierarchy path and replaced with something most likely slower but at least it's correct for now. Premature optimisation is the root of all evil, as they say. Flagged it with a comment for review later however. Added a page title, and other misc. cleanup.
-
Nigel McNie authored
-
Nigel McNie authored
-
Nigel McNie authored
It does basically do what the old one did. I do want to poke it into having the feedback not need javascript though.
-
Nigel McNie authored
-
- 30 Nov, 2007 1 commit
-
-
Nigel McNie authored
-
- 28 Nov, 2007 3 commits
-
-
Nigel McNie authored
Namely: the string saying how many results there are, and the string that says there are no artefacts to choose from.
-
Nigel McNie authored
I was actually looking to fix a bug about it displaying the currently logged in user in search results, but there's a change on the forums branch that will allow this, and I don't want conflicts.
-
Nigel McNie authored
Now the items are layed out in a grid to the right of the searcher, which saves some vertical space and has more fluidity to the layout. Also, the calendar elements have from/to text, which is a small violation of the language text freeze but makes the purpose of the calendar items for each element much clearer. I'd like to add more text to this page as an explanation, though that would be a larger violation.
-
- 27 Nov, 2007 2 commits
-
-
Nigel McNie authored
-
Nigel McNie authored
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.
-
- 14 Nov, 2007 2 commits
-
-
Francois Marier authored
-
Penny Leach authored
Changed all requires. Also removed not used json/renderartefact.php
-
- 07 Nov, 2007 1 commit
-
-
Nigel McNie authored
Use the key 'javascript' instead of 'js' everywhere, for consistency with the vast majority of stuff we already have doing things this way (render_self)
-
- 04 Nov, 2007 1 commit
-
-
Nigel McNie authored
-
- 29 Oct, 2007 2 commits
-
-
Nigel McNie authored
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.
-
Nigel McNie authored
* 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.
-
- 27 Oct, 2007 1 commit
-
-
Nigel McNie authored
Call the new artefactchooser_element method to establish the data required to render the pagination. This means less data has to be passed to the script. Also format the json_reply call a bit better.
-
- 26 Oct, 2007 1 commit
-
-
Nigel McNie authored
Tell the template if the user viewing the view can also edit it, so a link can be displayed allowing them to do that.
-
- 23 Oct, 2007 5 commits
-
-
Nigel McNie authored
-
Nigel McNie authored
The page was being first hit using the 'id' parameter, pieforms was building the form based on this. But the hidden element in the form was called 'viewid'. When the page was being hit again after form submission, the form was built again assuming 'viewid' held the view ID, which it did not anymore. Thus the form was built with and ID of 0, and the submit handler behaved appropriately - by creating a new view. The small bug was that the 'save' button said 'new' when you were saving an existing view.
-
Nigel McNie authored
Now uses the centralised method of building the artefact chooser content, and uses extradata to make sure the correct page of results is being generated.
-
Nigel McNie authored
Added the artefactchooser pieform element, smarty templates and javascript file. Really rough first drafts.
-
Nigel McNie authored
-
- 17 Oct, 2007 1 commit
-
-
Nigel McNie authored
-
- 16 Oct, 2007 11 commits
-
-
Nigel McNie authored
-
Nigel McNie authored
-
Nigel McNie authored
Hook in the layout views css for the 'view view' page so it doesn't look like a pile of steaming wreckage
-
Nigel McNie authored
Show a message when redirecting back to the view edit page if no layouts are available for the view. Made sure this happens with five columns as well as one column
-
Nigel McNie authored
-
Nigel McNie authored
-
Nigel McNie authored
-
Nigel McNie authored
-
Nigel McNie authored
-
Penny Leach authored
view/view.php reworked - all the blocktype and view class changes done in order to support non editable views
-
Penny Leach authored
-