Re: Caps and Options update

[Guillaume Emont <gemont igalia com>]

On 05/04/2011 15:19, Juan A. Suárez Romero wrote:
> On Tue, 2011-04-05 at 14:35 +0200, Guillaume Emont wrote:
>> Here is how I see the next steps, with the aim of integration into
>> trunk:
>>  0. Fix issues you guys might raise on the latest version
>>  1. Remove pagination and flags from caps.
>>  2. (optional) make _set_value() and _get_value() private for both
>> options and caps.
>>  3. Modify code in metadata source and media source to use use caps
>> and
>> options.
>>  4. Modify at least one plugin to make sure the model works
>>  5. Modify all plugins to handle the new model
>>  6. Test everything
>>  7. (optional) merge all changes, as from this point on, we should
>> normally not need to break API/ABI to add filtering and sorting
>> support
>>  8. and 9. Add filtering and sorting support, not sure what order
>> makes
>> more sense. Filtering would probably be faster to implement since Juan
>> has already spent quite some time studying the issue.
>>
>> Any comments on that? (especially the optional steps). Does that look
>> like a sensible way of doing that?
>>
> 
> 
> Yes, I would do 8 & 9 as soon as possible. In fact, I would do it before
> 3. Because those two options are the one that definitely will tell us
> how good is our caps/options, and any issue to fix.

Well, the reason I was proposing 3., is that merging options in trunk
early can help us, beyond testing on our own, to ensure that we didn't
break anything. For the same reason, when we have filtering, I think we
should try to have it merged before doing sorting.