Add profiles to wrench menu

ui/base/models/simple_menu_model.cc

Index: ui/base/models/simple_menu_model.cc
diff --git a/ui/base/models/simple_menu_model.cc b/ui/base/models/simple_menu_model.cc
index 57f6ec3e736ce04d06a0a35047a3d8e278916c0e..6301a11b2d41109378dc49fb379420e96d80c507 100644
--- a/ui/base/models/simple_menu_model.cc
+++ b/ui/base/models/simple_menu_model.cc
@@ -180,6 +180,10 @@ void SimpleMenuModel::Clear() {
   items_.clear();
 }
 
+void SimpleMenuModel::RemoveItemAt(int index) {

[sail, 2011/06/10 06:57:31]

This change isn't ready yet but I'm stuck on this part.
I need to be able to change the menu as the user adds and removes profiles.
I tried changing the menu model but this ends up crashing in the UI code. It
looks like the UI code doesn't realize that the model has changed and it starts
to dereference stale pointers.

Is there a good way to do this? Thanks!

[Nico, 2011/06/10 14:34:23]

Several SimpleMenuModel clients create a new ui menu from the model every time
the menu is displayed. That sounds like a simple way to make this work. Which
platform are you seeing this problem on?

[sail, 2011/06/10 14:52:59]

I'm seeing this on mac.
So do I change wrench menu controller to build a new menu each time? This will
mean that I have to move the edit and zoom buttons into a separate nib. Is that
ok?

[sky, 2011/06/10 16:24:14]

The windows side does this. Of course you would have to take care not to modify
the model while the menu is showing, otherwise bad things would happen. 

[Robert Sesek, 2011/06/10 16:46:26]

In general, MenuModel is immutable after creation. There are no delegate
notifications for when the Model changes and all the clients (at least on Mac)
do not expect for the model to mutate.

I may be mis-remembering, so take this with a grain of salt, but I think moving
views between menu items did not work in the past. So, you would need to move
the objects into a new xib and re-load it each time.

Unfortunately, the current architecture of the WMC doesn't really expect this.
If you need me to help at all with this, let me know.

The other option, which I think would be all-around preferable, would be to make
a MutableMenuModel which would broadcast change notifications to its delegate.
This has been something that I've been meaning to do for a while but haven't had
the time to pick up. Then the model wouldn't have to be rebuilt each time and
items could be added/inserted/mutated at will.

+  items_.erase(items_.begin() + FlipIndex(index));
+}
+
 int SimpleMenuModel::GetIndexOfCommandId(int command_id) {
   std::vector<Item>::iterator itr;
   for (itr = items_.begin(); itr != items_.end(); itr++) {