Update : This post is now formated correctly.
Wow, it is quite impressing that Miguel proposed to use the ribbon in MonoDevelop in his last post. When I started the project, I looked for ways to test my ribbon. One of my idea was also to redesign MonoDevelop, but I started with a tiny sample because it was much simpler 
Redesigning MonoDevelop remained one of my secret target, but it never happened due to lack of time or caffeine…
Below is the content of ribbons I imaginated 2-3 months ago:
Solution
+Version Control
++Checkout
+Solution
++Build
++Rebuild
++Clean
+Project
++Build
++Rebuild
++Clean
Testing
+Execution
++Run
++Debug
Test Units
+Coverage
++Test class
++Test project
++Test solution
+Mono
++Compability check
Release
+Documentation
++Generate
+Deploying
++Deploy
++Deploy to
++Configure targets
+Version Control
++Commit
++Build patch
I did also thought of some contextual ribbons:
Source code
+File
++New
++Open
++Save
+Printing
++Print
++Print Preview
+Editing
++Undo
++Redo
++Copy
++Paste
++Cut
+Search
++Search
++Previous
++Next
++Replace
++Go to Line
++Go to Matching Bracket
+Bookmarks
++Toggle
++Previous
++Next
++Clear all
Namespace
+Refactoring
++Rename
Class
+Refactoring
++Rename
++Change namespace
Method
+Refactoring
++Rename
++Move up
++Move down
Field
+Refactoring
++Rename
++Encapsulate
I am sure that this is not optimal, but I think it is not too bad. The problem is that plugins would also have to use the ribbon. Consequently, there is a lot of code to update.
