On 10/15/13 12:09 PM, "Sharma, Pratyoosh" <pratyoosh.sha...@jpmorgan.com> wrote:
>Ok, makes sense. So if you happen to use PopUp control, the draggable >titlebar bead will be tied to it as a part of component code itself. Yes, preferably via a default custom style property so there isn't an actual class dependency on the implementation. > >Module support will be interesting & probably a relatively more complex >problem to solve & though I am quite new to closure, there seems to be >quite a good amount of material on it, bringing in code for component >just used in modules on need basis makes sense. >I haven't delved too deep into the bead declaration in the CSS & just >wonder how it works on JS, I guess that is one part of the framework I >need to look at little bit deeper into. On the JS side, specifying beads via custom style properties is still work in progress and probably next on my list. My first attempt will be to implement the way we do it in AS on the JS side. >I guess I am good to complete drag feature on PopUp class. Looking forward to seeing it. > >P.S.: A small problem I faced though mxmlc seems to assume that there >will be a .js file for each closure class but that doesn't seems to be >the case for goog.events.BrowserEvent.MouseButton, this causes a >compilation error, had to make a very minor tweak on the dragger requires >to make it work, this is a non sustainable change though that should be >fixed on compiler, I will create a JIRA for this. Yes please do. I also discovered that the goog.require in the closure files aren't as "clean and consistent" as I originally thought. I'll probably teach the compiler not chase down requires in goog files. -Alex >
