Bugzilla

I'm not sure if this is technically doable, but maybe it's something worth exploring.

**Rebuild our toolbar in order to have only dynamic implementation**
Currently, we have a dedicated toolbar for each tab. This is kinda necessary because each tab has different toolbarbuttons and different needs.

This approach falls short once we start needing to implement the same button on each toolbar. The most obvious example is the main app menu button, which we need to initialize multiple times for each toolbar location.

It also turns tedious when new buttons are implemented that need to be available in every toolbar or when new tabs are implemented (new address book missing the app menu button).

**Proposal**
We should have only one toolbar button, which is included in all those tabs that need it.
We should then find a decent mechanism that allows us to:
- Have all the available `<toolbarbutton>`s defined in one single file.
- Independently define a `defaultset` of toolbarbuttons available per tab.
- Independently define a set of all customizable toolbarbuttons available per tab.

What do you guys think?

I'm not sure if this is technically doable, but maybe it's something worth exploring.

**Rebuild our toolbar in order to have only dynamic implementation**
Currently, we have a dedicated toolbar for each tab. This is kinda necessary because each tab has different toolbarbuttons and different needs.

This approach falls short once we start needing to implement the same button on each toolbar. The most obvious example is the main app menu button, which we need to initialize multiple times for each toolbar location.

It also turns tedious when new buttons are implemented that need to be available in every toolbar or when new tabs are implemented (new address book missing the app menu button).

**Proposal**
We should have only one toolbar.
We should then find a decent mechanism that allows us to:
- Have all the available `<toolbarbutton>`s defined in one single file.
- Independently define a `defaultset` of toolbarbuttons available per tab.
- Independently define a set of all customizable toolbarbuttons available per tab.

What do you guys think?

I'm not sure if this is technically doable, but maybe it's something worth exploring.

**Rebuild our toolbar in order to have only one dynamic implementation**
Currently, we have a dedicated toolbar for each tab. This is kinda necessary because each tab has different toolbarbuttons and different needs.

This approach falls short once we start needing to implement the same button on each toolbar. The most obvious example is the main app menu button, which we need to initialize multiple times for each toolbar location.

It also turns tedious when new buttons are implemented that need to be available in every toolbar or when new tabs are implemented (new address book missing the app menu button).

**Proposal**
We should have only one toolbar.
We should then find a decent mechanism that allows us to:
- Have all the available `<toolbarbutton>`s defined in one single file.
- Independently define a `defaultset` of toolbarbuttons available per tab.
- Independently define a set of all customizable toolbarbuttons available per tab.

What do you guys think?