~vtuson/scope-aggregator/film : changes

~vtuson/scope-aggregator/film » Changes from revision 42

From Revision 42 to 23

Rev	Summary	Authors	Date
42	remove location data as a requirement remove location data as a requirement	Victor Palau	9 years ago
41	no source msg no source msg	Victor Palau	9 years ago
40	moved logic to a json flag moved logic to a json flag	Victor Palau	9 years ago
39	basic sources working basic sources working	Victor Palau	9 years ago
38	added filters for cinema added filters for cinema	Victor Palau	9 years ago
37	added store added store	Victor Palau	9 years ago
36	movie aggregator 0.1 movie aggregator 0.1	Victor Palau	9 years ago
35	modify child scopes json to match modify child scopes json to match	Kyle Nitzsche	9 years ago
34	arrrg! copied wrong files in. this one fixes the aforementio... arrrg! copied wrong files in. this one fixes the aforementioned bug	Kyle Nitzsche	9 years ago
33	actually fix the category ordering bug that happened when se... actually fix the category ordering bug that happened when setting a child category (previous fix did not fix it)	Kyle Nitzsche	9 years ago
32	added to src/query.cpp //TODO: support using child_category ... added to src/query.cpp //TODO: support using child_category AND using a different category for not_logged_in results	Kyle Nitzsche	9 years ago
31	correct regression in category ordering in which the buffer ... correct regression in category ordering in which the buffer var was incorrectly set to false AND the first bool was not set to false in the right place	Kyle Nitzsche	9 years ago
30	Added the capabililty to specify common renderer templates ... Added the capabililty to specify common renderer templates in child_scopes.json, and then to declare for any child scope that if the cateogry id in the result is X, use the common template whose id is Y. A main purpose of this is to allow using a common category/layout for such things as presenting login buttons when the child scope provides a result through which the user logs in through online accounts. One thing that makes this a little complex is that each child scope uses particular category ids for such a case. Therefore, this implementation allows any child scope (in the json) to declare the equivalent of this: if the results category id is X, use common template R. Caution: a child scope in an aggregator should only ever have a single category, so use this feature should be used with care. Here's how it works. child_scopes.json now supports a new top level object called "common-templates". This includes a list of objects, each of which is a common template with two fields: id and template, like so: { "common_templates": [ { "id" : "not_logged_in", "template": { "schema-version": 1, "template": { "category-layout": "grid", "card-size": "large", "card-background": "color:///#5E2750" }, "components": { "title": "title", "subtitle": "subtitle" } } } ], "child_scopes": [...] For each child scope, you can connect the incoming result to any such common template by adding a "result_category_id_to_common_template" array of objects, each of which must contain the two keys shown below "child_scopes": [ { "scope": { "id": "com.canonical.scopes.fbphotos_fbphotos", "category_title": "FB Photos", [...] "result_category_id_to_common_template": [ { "result_category_id": "fbphotos_login", "common_template": "not_logged_in" } ] } }, * result_category_id declares the category id of the incoming result. * common_template declares the id of the template declared in this file in the "common_templates" list.	Kyle Nitzsche	9 years ago
29	* Added support for declaratively (from child_scopes.json) c... * Added support for declaratively (from child_scopes.json) changing result attributes. That is, specified incoming child result attribute values are obtained and inserted into specified aggregator result attributes for the particular child scope. For example, suppose the child scope has this json: "swap_result_attributes": [ { "incoming_result_key": "mascot", "new_result_key": "art" }, { "incoming_result_key": "art_", "new_result_key": "mascot" } ], What happens is: * The aggregrator scope result attribute named "art" is given the value of the incoming (from the child scope result) attribute whose key is "mascot" * The aggregator scope result attribute named "mascot" is given the value of the incoming result attribute named "art_"	Kyle Nitzsche	9 years ago
28	move make_child_scopes() into utils since it is no longer co... move make_child_scopes() into utils since it is no longer code a developer should need to modify	Kyle Nitzsche	9 years ago
27	translation works using the po/JSONS file in the usual mecha... translation works using the po/JSONS file in the usual mechanism I created earlier. simply run the scripts in po and your po files are up to date including msgids originating from json values whose key starts with '_'.	Kyle Nitzsche	9 years ago
26	Have converted this to declarative model. Now you declare yo... Have converted this to declarative model. Now you declare your child scopes in data/child_scopes.jon. Still need to provide declarative override for result handling though. And, implement a means to translate child scope category titles.	Kyle Nitzsche	9 years ago
25	update license text in .h and .ccp files update license text in .h and .ccp files	Kyle Nitzsche	9 years ago
24	remove couple white lines remove couple white lines	Kyle Nitzsche	9 years ago
23	* move Query::handle_enabled_child_scopes() into utils.cpp b... * move Query::handle_enabled_child_scopes() into utils.cpp because it is not expected that devs will need to modify it when creating agg scopes. * move most hints/OOBE code into utils.cpp also because devs are not expected to need to modify this. What's now left in query.cpp is pretty tightly focused on just what devs need to modify to create an agg scope	Kyle Nitzsche	9 years ago

Older »