|
|
Search Tutorials
MotivationBeing over the major hurdles as far as component creation is concerned, you bask in the glow from excited faces of your designers and developers eager to exploit the magic of your triangle component. One group whose faces are surprisingly not glowing is the Quality Assurance people, who now tell you that you have made it so easy to produce isosceles triangles for Flash movies that people are using them improperly. In fact, they tell you that if the base and height are out of a certain proportion, the triangle is no longer user friendly. The head of Quality Assurance tells you that you must incorporate a 'user-friendly' metric into your component to warn developers when triangles are becoming dangerously unfriendly. To help, she gives you the industry-accepted, friendliness-to-user quotient for isosceles triangles: fuqu = (base * 4.211) / height The ideal fuqu is 4.211, and the more it departs (either higher or lower) from this value, the more unfriendly the triangle becomes. Creating triangles with fuqu's below 2.211 or above 6.211 is even grounds for dismissal at your company. Your altruistic side decides you need to alert users of your component before they make a fatal mistake. You will create a custom UI for the triangle component that alerts the user if the triangle violates corporate policy, based on the base and height they enter. This will not help programmers who script the component dynamically, but they are likely beyond hope already.
|
||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||
|