[etoys-notify] [JIRA] Updated: (SQ-126) Switching language removes Buddies flap

[Bert Freudenberg (JIRA)]

     [ http://tracker.squeakland.org/browse/SQ-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bert Freudenberg updated SQ-126:
--------------------------------

    Priority: Critical  (was: Optional)

Switching languages (as sometimes happens when entering another project) also destroys all user-created shared flaps. Raising priority.

> Switching language removes Buddies flap
> ---------------------------------------
>
>                 Key: SQ-126
>                 URL: http://tracker.squeakland.org/browse/SQ-126
>             Project: squeakland
>          Issue Type: Bug
>          Components: etoys
>            Reporter: team
>            Priority: Critical
>             Fix For: etoys 2011
>
>
> FromTRAC Ticket #7747 (bert, aug 2008)
> While shared, a "buddies" flap is shown. When changing the language, it disappears.
> Seems to be caused by 1508flapsOnLanguageChg-sw:
>     * If sugarNavigator is true, put up the sugar flaps.
>     * If sugarNavigator is false, then put up either
>           o developer's flaps, i.e. Tools, Widgets, etc., if eToyFriendly is false
>           o 'classic' etoy flaps (a la Squeakland) if eToyFriendly is true. 
>     * If user has destroyed existing flaps, the flaps menu offers all three alternatives for fresh flap installation. 
> But we need to preserve the "buddies" flap because removing it breaks sharing. IMHO the code should not remove any non-system flaps.
> Unfortunately, flaps use the translated name for identification. So we still need to treat the buddies flap specially, and when switching the language rename it to the new translated name.
> In general it would be much wiser to use a translation-independent tag to identify flaps in code ...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.squeakland.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira