Silica guidelines vs long lists and a lot of options
 

As this was a bit OT in a different thread starting new one.

In my opinion Silica guidelines are ok for a few choices, maybe my thumb is too short, but I see no way to properly implement pulley menu in apps that have a lot of options or a few very often used ones. QT Creator in Silica? GIMP? Transmission? There's just no way, or you will have to hide all the options under 4-5 accessible in the pulley menu. See IRC app for example, totally unsilica (at least fails guidelines, in my opinion it is Silica++), yet works absurdly well. Not only you get quick access to most often used options instead of pulleying down menu to select msg or channel and only then selecting from a long list, but you also get a quick glance-like feature by changing colour, so you instantly know who msged you after the vibra. Maybe I'm a bit too in love with the app, but I believe Silica needs an update. It works great for apps where you have 'settings/about/refresh' and nothing else, but lacks for many others. Thoughts?

Re: Silica guidelines vs long lists and a lot of options
 

Rules are there to be broken, aren't they? :)
If you can achieve a better user-experience in your app by breaking one or two of the guideline rules, then why not?
But in general having a long list of options in a pulley menu does not give a good user experience (counter-example: directory path breadcrumbs in the pulley menu in Cargo Dock).
IMHO it always depends on the use-case if applying the rules strictly makes sense, or not.