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

Age	Commit message (Collapse)	Author
2010-04-16	Only return the members element to the rest client if the item is an album. ↵	Tim Almdal
	This makes it consistent to the rest client that collections will have a members element.
2010-04-04	REST changes: Allow PUT and POST requests to modify members, not	Bharat Mediratta
	just entity. TESTS ARE NOT UPDATED YET. - Fix item_rest::get() to maintain the proper sort order, which requires duplicating some Item_Model code. - Elide "weight" from the REST version of item - Adjust the weight of members according to the order they're returned from the client. You can't add or remove members here, you can only reorder them. - Changed the wire protocol to handle more complex values. Now "entity" and "members" are JSON encoded. The Gallery3 helper does this correctly. - Changed the wire protocol for tag_item -- now it stores the tag and item urls in the entity, not as members. This is more consistent. - Added missing security for renaming and deleting tags. - Got rid of vestigial tag_rest::post(). We add/remove tags via the relationship.
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 ) ) )