gallery3.git - A clone of the Gallery3 code for testing and development.

Age	Commit message (Collapse)	Author
2008-11-18	First iteration of REST controller refactoring. RESTful controllers that ↵	Jozef Selesi
	refer to collections should now have plural names and there should be only one controller per resource. Updated existing classes that implement REST_Controller. The routing now works like this: GET /controller -> controller::_index() POST /controller -> controller::_create() GET /controller/id -> controller::_show() PUT /controller/id -> controller::_update() DELETE /controller/id -> controller::_delete() GET /form/edit/controller/resource_id -> controller::_form() GET /form/add/controller/data -> controller::_form()
2008-11-17	Add output formats to our REST controllers. Add support for JSON and	Bharat Mediratta
	XML to the comment controllers as a proof of concept. It's not fully baked; we should examine ways to create helpers to make this process easier.
2008-11-16	Handle _method in either GET or POST	Bharat Mediratta

2008-11-16	Drop the call to render() and just use the View's __toString method to	Bharat Mediratta
	print it out.
2008-11-16	Several large changes:	Bharat Mediratta
	1) Changed the way that we get forms. Now, if you want to get a form for a REST resource you prefix /form to the resource id. So: /form/photo/1 : returns a form for editing photo id 1 /form/comments/1 : returns a form for adding a comment to photo id 1 /form/comment/1 : returns a form for editing comment id 1 2) Changed the comment module to have two controllers: comment: deals with a single comment resource comments: deal with collections of comments attached to an item Related stuff: - Moved the comments js into the theme - Reworked Comment_Helper for clarity - Moved form generation code down into Comment_Helper - Cleaned up routes (eliminating new comment ones added in recent rev) - Added form() function to all REST controllers - Changed comment module to use a block instead of an arbitrary helper call from the theme - Comment controller only returns HTML currently, but returns a 201 Created status code when a new comment is added, which the Ajax code can catch and act upon. - Got rid of a lot of extra views in comment module
2008-11-15	Revise the user login code.	Bharat Mediratta
	* Remove user registration link and popup from the theme; this shouldn't be done in a popup. Use ajaxform to simplify the way that we load the login popup. * Create form.html.php, this is a template for Forge based forms. * Move user validation rules into User_Model and let forms populate the rules into their forms as useful. * Undo r18688's changes regarding the REST code. We should never accept a null resource, this breaks the REST abstraction. * Change login and user controllers to use Forge which lets us delete login.html.php and user.html.php since those now are generated by the theme-owned form template
2008-11-14	Allow the HTTP get method to be called without an id to create any empty ↵	Tim Almdal
	template.
2008-11-14	Use the shortform to load the resource.	Tim Almdal

2008-11-11	Change the PUT/DELETE tunneling param from __action to _method	Bharat Mediratta
	to be like Rails.
2008-11-11	Change REST API to use non-routable functions: _get(), _post(),	Bharat Mediratta
	_put(), _delete(). This should make it more obvious that these are not your typical routes, simplifies overall routing by removing a rule and removes the possibility of accidentally leaking information if we route to one of them by accident.
2008-11-11	Add phpdocs to explain how to use REST_Controller	Bharat Mediratta

2008-11-11	Create REST_Controller abstract base class for all REST based resource	Bharat Mediratta
	controllers. Any controller that wants to act RESTful can extend this class and implement get/post/put/delete. Tweak default routes to disallow direct access to the REST controller and direct access to any REST methods.