![]() ![]() ![]() Your mission with such a control is to make something that satisfies the art direction requirements (I will not open the can of worms questioning how sane an art director wanting a custom select is), but at the same time is discoverable using the standard operating system idioms. Or your boss does not get UX and lives in the art-directorial LSD fuckfest of the late nineties, and absolutely requires a custom control. Imagine you are all giggly and want to make a custom select element - a menu. Every custom select implementation is bound to be reinventing the wheel, in a bad way. ![]() There is a load of stuff humanity has put into menu implementations for the past 40 years. What I hate is a substantial reduction in useful behavior compared to a native control. Most of the apps I use daily (Flame, Smoke, Syntheyes, Nuke) do not use the native UI controls at all. I hate this kind of thing not because it doesn’t look like a native control - this is in fact secondary. After having a poke here and there, I was surprised to find that the custom controls epidemic was not over for some people.Īll popup menus on the system (all select elements) were implemented as custom HTML controls with custom event handling. It is in fact an iteration on the system we are actively using at the company. Recently I had a privilege of reviewing a web app that is directly relevant to my work field. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |