Hi Carlos, I was thinking about like that some time, but in the end I decided to have strong typed mechanism rather than generic.
W don't have in our MDL all icons - Let user implement for himself whatever he want's to have. For me have specific class which makes one thing is a way better than have class which taking some string parameter and it can be everything. MaterialIcon can be an additional option, but if you add it - I think most users stops using/implement - specific type icons. That was my point of view... Piotr ----- Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.2333347.n4.nabble.com/FlexJS-About-Material-Icons-tp58562p58563.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
