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

Age	Commit message (Collapse)	Author
2010-03-13	Changes to the example client to test updating the members of an album.	Tim Almdal

2010-03-13	Changes to support updating the child elements within an album. In this ↵	Tim Almdal
	change the urls of the children are sent up asan array of post fields children[0].... children[n]. If an existing child is not included it is deleted. Including a url to an child in another album will move the child. Changing the order of the children will respect the order of the children, if the sort column is 'weight'
2010-03-03	Update the copyright to 2010. It's only 3 months into the year :-)	Bharat Mediratta

2010-02-12	Revert "1) Add a depth parameter to retrieving an item thru the rest api"	Bharat Mediratta
	This reverts commit 3439671bcfb99c1884285e4b4e53295f044e688f.
2010-02-12	1) Add a depth parameter to retrieving an item thru the rest api	Tim Almdal
	2) Standardize the structure of members so that client programs can consistently parse the return information. 3) Added a summary parameter so that client programs can easily determine if the information returned is summary (item type, item title) or the full meal deal
2010-01-30	Use Item_Model::as_restful_array() to simplify tests.	Bharat Mediratta

2010-01-30	Remap parent_id and album_cover_item_id to and from RESTful urls.	Bharat Mediratta

2010-01-27	Convert back to using ORM::factory(..., $id) instead of calling where().	Bharat Mediratta

2010-01-27	Change "resource" to "entity" in REST responses. They're all	Bharat Mediratta
	resources, but we differentiate resources as collections and entities.
2010-01-22	Return the url of the newly created item from post().	Bharat Mediratta
	Don't try to access ORM::$changed -- it's protected.
2010-01-22	Reshape the rest code to be more consistent with regards to	Bharat Mediratta
	relationships. Now when you view a resource, it has 4 top level elements: url: the url of this resource resource: array of key value pairs describing the resource members: array of urls to members of this collection relationships: array of array of members. Relationships are a special type of collection that links two different resources together. To remove a relationship, just DELETE its url. To create a relationship, POST to its collection. Individual modules can add their own relationships to any resource via a callback mechanism. Example: Array( [url] => http://g3.com/rest/item/1 [resource] => Array ( [id] => 1 [album_cover_item_id] => 4 [captured] => [created] => 1264056417 [description] => [height] => ... ) [members] => Array( [0] => http://g3.com/rest/item/2 [1] => http://g3.com/rest/item/3 [2] => http://g3.com/rest/item/4 [3] => http://g3.com/rest/item/5 ... ) [relationships] => Array( [tags] => Array ( [0] => http://g3.com/rest/tag_item/2,1 [1] => http://g3.com/rest/tag_item/23,1 ) ) )