[Sugar-devel] [IAEP] Activity version compatibility

[Wade Brainerd]

BTW, we should still answer the question of the activity.info field...
 Seems like there 3 options to me:
1) Deprecate host_version in the activity.info spec.  Activity developers
write code to test for presence non-BC APIs and provide fallbacks (or else
let activities fail to launch/work).

2) Keep host_version as an incrementing number, make activityfactory respect
it, and bump the Sugar number from 1 to 2 in 0.86.1 to reflect the toolbar
changes.

3) Deprecate host_version, introduce sugar_version which is set to the
oldest Sugar version number the activity is compatible with.

I'm fine with any of these, let me know and I'll provide the patch.

-Wade

On Tue, Sep 29, 2009 at 12:12 PM, Gary C Martin <gary at garycmartin.com>wrote:

> On 29 Sep 2009, at 14:00, Wade Brainerd wrote:
>
>  On Mon, Sep 28, 2009 at 8:15 PM, Gary C Martin <gary at garycmartin.com>
>> wrote:
>> I have a prototype patch which fixes the launch window and adds an error
>> message.  I'll try to get it posted soon.
>>
>> Cool :-)
>>
>> Ok, a prototype patch is posted at http://dev.sugarlabs.org/ticket/1447.
>>  When an activity fails to start, it immediately displays a "<Name> failed
>> to start." with a close button.
>>
>> If anyone can test it out I would greatly appreciate it.  Also if you have
>> a theory about the occasional segfault when clicking Close, or know how to
>> get a traceback when running jhbuild, let me know.
>>
>
> Fantastic, looks great, I'm hacking on new Labyrinth toolbars just now so,
> I will apply this and test it on all the tracebacks I get ;-)
>
> Regards,
> --Gary
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sugarlabs.org/archive/sugar-devel/attachments/20090930/afdb7c81/attachment.htm