On 1/13/17, 11:13 AM, "piotrz" <piotrzarzyck...@gmail.com> wrote:
>I was working on Big Flex app where we were using SOAP/XML. - I think now >we >can consume XML in FlexJS. Yes. You can migrate today if you are using XML, only need to support one language and don't use modules. Regarding skinning, in theory your company already has CSS for branding other web-pages and hopefully a lot of that can be used in FlexJS assuming the only skinning you need is to brand the app as opposed to offering lots of different skins for your customers to choose. We don't have support for WSDL handling or decoding SOAP to ValueObjects yet, but instead of us having to write that code before we get more customers, I keep hoping that one customer will show up and say "I can't wait to migrate anymore and I think it will be cheaper to have one of my developers help build out this missing feature than to have my team port the whole app to some other JS framework." What I think we need is "credibility" via a testimonial. I think folks who have to migrate now just pass up FlexJS for React or Angular because they aren't sure that FlexJS is ready. FlexJS isn't a "safe" choice yet. That's why if one person can attest that it was safe enough for them, that could cause one more person to not pass on us and get the ball rolling faster. > >Another thing which came up to my mind - Did we ever write any WIKI page >to >show people what actually option of data consuming we have ? > >I think if it will be pointed on WIKI and in Release notes somewhere it >gets >an attention - What do you think ? It should be documented somewhere, but that opens the whole debate about where to document. Some folks don't want to add more stuff to the wiki. IMO, as Peter gets going on Tour De FlexJS, that where we should document the ways to get data. My 2 cents, -Alex