Hi Carlos, I just saw your tweet with the MDL example in front of the MXML for it.
There seemed like a lot of MXML in the example. I was wondering if you considered baking in the Prompt and Disable beads into your example to make it less verbose. The reason the Basic components have TextPromptBead and DisableBead is because not all instances of TextInputs and Buttons have prompts or are disabled, but primarily because there are different implementations of TextPrompts and Disable. Some TextPrompts will go away on focus. Others go away when you start to type. Some restore the prompt if you delete all content from the TextInput, some don't. Some people want to "blur" the visuals of Buttons when disabled, others want to change to a different visual. If MDL has one and only one implementation of TextPrompts and/or Disable then you could just add floatingLabel and enable properties to your MDL TextInput and Buttons and save several lines of MXML. There is no right answer, though, and you can always do both. -Alex