On 12/09/2008, Andy J. [email protected] wrote:
to put a
menu between your users and your engine. Think instead about what kind
beautiful GUI would display and animate your features the best.
I prefer to be able to choose when I want to think outside the box.
Well, you chose that when you chose Shoes.
Menus are a ubiquious part of GUIs; users know how to use them and what
to expect. If they want to save, they already know how to do that in
countless GUI applications across Windows and Mac (and I guess Linux
too). But not for a Ruby Shoes application. There is a good reason why
enus have been a part of GUIs for well over twenty years - they work
very well. I think this is a serious ommission from the toolkit, and it
surprises me that no one else on the web sees it that way.
And they are consistent hindrance in the user interaction for over
twenty years. They are one of the poorest UI parts in use today.
There are other ways how to present a “Save” feature to the user.
There are bazillions of applications out there that have a “Save”
button on every graphics enabled platform I have seen.
And there are many applications that do not require you to save
anything manually. They update your choices on the fly as you make
them. And if the application is intended for editing complex data it
should have undo history anyway, and you can automatically save that.
If you really feel like you absolutely need a menu there is about a
dozen toolkits you can choose from, just choose the tool that fits