[Sugar-devel] API policy

[Gonzalo Odiard]

Reworked the proposal to keep the method for background compatibility.

Gonzalo


On Wed, Jun 19, 2013 at 8:48 PM, Gonzalo Odiard <gonzalo at laptop.org> wrote:

> Good point, etoys use the object chooser.
> I don't know id dbus signature can do a parameter optative,
> or how do it backwards conpatible
>
> Gonzalo
>
>
> On Wed, Jun 19, 2013 at 8:28 PM, Daniel Narvaez <dwnarvaez at gmail.com>wrote:
>
>> What about non-python activities?
>>
>>
>> On Thursday, 20 June 2013, Gonzalo Odiard wrote:
>>
>>> In this case, the activities don't use the dbus API, but the object
>>> defined in sugar-toolkit-gtk3.
>>>
>>> Gonzalo
>>>
>>>
>>> On Wed, Jun 19, 2013 at 7:55 PM, Daniel Narvaez <dwnarvaez at gmail.com>wrote:
>>>
>>>> Hello,
>>>>
>>>> when reviewing patches I'm always unsure what to do about AP breaks,
>>>> both in python and in dbus interfaces. Do we have any kind of policy we
>>>> should follow?
>>>>
>>>> The last case I run into is adding a parameter to the ObjectChooser
>>>> dbus API. Is that a break we should make? Should we add a new method
>>>> instead?
>>>>
>>>> --
>>>> Daniel Narvaez
>>>>
>>>> _______________________________________________
>>>> Sugar-devel mailing list
>>>> Sugar-devel at lists.sugarlabs.org
>>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>>
>>>>
>>>
>>
>> --
>> Daniel Narvaez
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20130620/5b324b06/attachment.html>