Hi Piotr, First, thanks for the fixes you’ve done so far.
You can make any changes you want to files in the FlexJSJX project. These files get cross-compiled so the refactoring I’m doing doesn’t care what the source looks like. It will make the merge easier if files in the FlexJSUI project don’t have big changes made to them. Not sure how long it will take me to finish up the defineProp change. Maybe I’ll finish by next week or at least be able to check it in. If a component in FlexJSJX has significant differences in AS vs JS, there can be a number of reasons why. It could be: 1) The cross-compiler isn’t generating the right thing 2) The FlexJSUI that components in FlexJSJX usually depend on have a bug. 3) Some new class needs to be added to FlexJSUI to abstract a difference between AS and JS 4) The AS side, especially the layout classes aren’t handling the CSS the same way as the JS side. In those cases I try to fix the AS side. We wan’t the JS code to run as natively as possible. Good luck and feel free to ask more questions, although I’m pretty much done for tonight. -Alex On 3/18/15, 11:19 PM, "piotrz" <piotrzarzyck...@gmail.com> wrote: >Alex, > >I was able to build couple of examples. >DateChooserExample seems for me as a good start to try fix something in >FlexJS. DateField doesn't look good in html version. > >Questions: >1) Should I wait for your refactoring ? >2) How to fix bugs if component looks ok in Flash version, but something >is >wrong on js? > >Piotr > > > >----- >Apache Flex PMC >piotrzarzyck...@gmail.com >-- >View this message in context: >http://apache-flex-development.2333347.n4.nabble.com/FlexJS-Issue-with-bui >lding-example-tp45615p45627.html >Sent from the Apache Flex Development mailing list archive at Nabble.com.
