<div>
<span style="font-size: 15px;">Hi all -</span>
</div><div><span style="font-size: 15px;"><br></span></div><div><span style="font-size: 15px;">I think I lean in the direction of more carrot, less stick, for a release or two.</span></div><div><span style="font-size: 15px;"><br></span></div><div><span style="font-size: 15px;">One reason is that, as Limi and Jared have mentioned, it will give add-on authors time to migrate. Another is that I suspect many people have add-on UI lurking in the add-on bar at the bottom of their screens, mostly out of sight and mind, and moving them into a toolbar at the top will make updating to Australis feel _more_ cluttered rather than less, which is not the update experience we want people to have. Yes, they can customize them to other parts of the UI, but they should feel like customization is a necessary and burdensome step.</span></div>
<div><div><br></div><div><span style="font-size: 15px;">If we're keeping the add-on bar, should we be including it in the customization mode?</span></div><div><span style="font-size: 15px;"><br></span></div><div><span style="font-size: 15px;">Madhava</span></div><div><br></div><div>-- </div><div>Madhava Enros</div><div>Firefox User Experience</div><div>mozilla.org/firefox</div><div><br></div></div>
<p style="color: #A0A0A8;">On Tuesday, May 14, 2013 at 3:29 PM, Alex Limi wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>+1 for not making this a requirement for Australis. Active add-on developers will probably want the added visibility and "nativeness" of being in the main toolbar, so this will hopefully resolve itself over time.</div><div><br></div><div>(Note that I speak for myself, not on behalf of the UX team on this :) </div><div><br></div><div>— Alex Limi · Product Design Strategy, Mozilla · <a href="http://twitter.com/limi">http://twitter.com/limi</a> · <a href="http://limi.net">http://limi.net</a></div><div><br></div><div><br></div><div><br></div><div>On Tuesday, May 14, 2013 at 11:55, Jared Wein wrote:</div><div><br></div><blockquote type="cite"><div><div>Maybe it makes sense to just leave the add-on bar untouched.</div><div> </div><div>We have a carrot or a stick here that we can use. The carrot here is the new API that puts the button in the navbar, the stick is removing the addon bar. If add-on developers like the new API, they can update their addon to move their content from the add-on bar to the nav-bar. It's not going to get everyone to move away from the add-on bar, but supporting the add-on bar isn't the biggest of our problems.</div><div> </div><div>Given the time schedule that we'd like to have for Australis (and the API change leadtime promised by the Add-on SDK), it probably makes more sense to leave the add-on bar untouched and keep pushing forward on new APIs for add-on developers to use that will let them put standard buttons in the nav-bar toolbar.</div><div> </div><div>- Jared</div><div> </div><div>----- Original Message -----</div><blockquote type="cite"><div><div>From: "Brunoais" <brunoaiss@gmail.com (<a href="mailto:brunoaiss@gmail.com">mailto:brunoaiss@gmail.com</a>)></div><div>To: firefox-dev@mozilla.org (<a href="mailto:firefox-dev@mozilla.org">mailto:firefox-dev@mozilla.org</a>)</div><div>Sent: Tuesday, May 14, 2013 5:01:26 AM</div><div>Subject: Re: Remove the add-on bar</div><div> </div><div>Can we put the addon bar back down if we want to by customizing the</div><div>UI</div><div>using the "customize..." menu option?</div><div>On 13-05-2013 21:11, ZER0 wrote:</div><blockquote type="cite"><div><div>4. Most of us wants to get rid of add-on bar.</div><div> </div><div>Hope I made all the premise clear for anyone that wasn't aware of</div><div>previous discussions.</div><div> </div><div>That said, if we want to remove the add-on bar we need a place were</div><div>put</div><div>the SDK Widget in Australis, because we don't have time to do the</div><div>deprecation process properly, so we – jetpack – need a period of</div><div>time</div><div>where both new UI Components and Widget coexist; but nav-bar is not</div><div>a</div><div>suitable place according to UX – and personally I agreed.</div><div> </div><div>My proposal is move the add-on bar to the top, above the content,</div><div>making</div><div>the add-on bar like any other toolbar in Australis Mockup. I made a</div><div>simple mockup for that, based on the ones made by Stephen:</div><div> </div><div><<a href="http://people.mozilla.com/~mferretti/files/addons-in-toolbar/addon-bar-mockup.png">http://people.mozilla.com/~mferretti/files/addons-in-toolbar/addon-bar-mockup.png</a>></div><div> </div><div>As you can see, there is a button with a generic add-on icon</div><div>pressed, in</div><div>the nav-bar, exactly like any other add-on that can creates a</div><div>toolbar</div><div>(see the mockup by shorlander).</div><div> </div><div>Have a solution like that should be consistent with the Australis</div><div>UI,</div><div>and in my opinion will also help the migration process of the SDK</div><div>Widget</div><div>to our new UI components: developers will start to wonder "Why I</div><div>have to</div><div>be in a generic toolbar with an anonymous button, when my add-on</div><div>can</div><div>have its own toolbar?"</div><div> </div><div>Hope that this approach will makes everyone happy, if you have</div><div>questions, doubts, concerns, other solutions or I missed /</div><div>misunderstood</div><div>something, please let me know!</div><div> </div><div>Cheers,</div><div> </div><div>Matteo</div><div>_______________________________________________</div><div>firefox-dev mailing list</div><div>firefox-dev@mozilla.org (<a href="mailto:firefox-dev@mozilla.org">mailto:firefox-dev@mozilla.org</a>)</div><div><a href="https://mail.mozilla.org/listinfo/firefox-dev">https://mail.mozilla.org/listinfo/firefox-dev</a></div></div></blockquote><div> </div><div> </div><div> </div><div>_______________________________________________</div><div>firefox-dev mailing list</div><div>firefox-dev@mozilla.org (<a href="mailto:firefox-dev@mozilla.org">mailto:firefox-dev@mozilla.org</a>)</div><div><a href="https://mail.mozilla.org/listinfo/firefox-dev">https://mail.mozilla.org/listinfo/firefox-dev</a></div></div></blockquote><div> </div><div> </div><div>_______________________________________________</div><div>firefox-dev mailing list</div><div>firefox-dev@mozilla.org (<a href="mailto:firefox-dev@mozilla.org">mailto:firefox-dev@mozilla.org</a>)</div><div><a href="https://mail.mozilla.org/listinfo/firefox-dev">https://mail.mozilla.org/listinfo/firefox-dev</a></div></div></blockquote><div><br></div><div><br></div><div><br></div><div>_______________________________________________</div><div>firefox-dev mailing list</div><div><a href="mailto:firefox-dev@mozilla.org">firefox-dev@mozilla.org</a></div><div><a href="https://mail.mozilla.org/listinfo/firefox-dev">https://mail.mozilla.org/listinfo/firefox-dev</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>