Polymer, Angular 2.x, ECMAScript 6, etc

Posted by: edvin on 14 September 2017, 2:08 am EST

    • Post Options:
    • Link

    Posted 14 September 2017, 2:08 am EST

    Hi,

    first of all. Congratulations. Your are developing really good stuff.

    Making Wijmo 5 with Angular first class support is good decision.

    We first look at API, features, demos, etc.

    Every looks perfect.

    But if we look around (say: look what Google is doing), there something new is preparing: Angular 2.x, Polymer (web components), Material design (Android “L”), etc.

    What’s your opinion about that ?

    As I said you create good stuff on Angular 1.x, but Google is moving forward to Angular 2.x.

    If we decide to focus energy in new Wijmo we need to know how it fits in Polymer, Material design components, etc.

    I know ECMAScript 6 and Angular 2.x are still in developement.

    But next year …

    What’s your opinion ? Any plans are desirable.

  • Posted 14 September 2017, 2:08 am EST

    Wow, thanks so much for the kind words!

    I guess it is a little too early to be talking about Wijmo 6 (since Wijmo 5 is just in Beta). But let’s do that…

    As you can see with Wijmo 5, we are not afraid to take drastic measures in order to make sure our products are modern and at the same time stable. So, yes, when the time is right, we will be supporting the ES6 and Web Components.

    These things are already on our radar, but they are currently too far off to create a stable product on. I would imagine in a year or two you will see things from us in these areas. But it all depends on the status of the browser ecosystem. We try to stay on the cutting edge, but have to ensure that our products work in Today’s browsers (not just Tomorrow’s).

    I hope this helps. And I hope you can see from Wijmo 5, that we are committed to making modern products.

    Thanks again -Chris (and team)

  • Posted 14 September 2017, 2:08 am EST

    To add a little detail: we wrote Wijmo 5 using TypeScript, which is following the EcmaScript 6 spec. So when EcmaScript 6 does come out, it should be really easy to port Wijmo 5 to that platform.

    Also, although we ship AngularJS directives (and will soon add support for KnockoutJS as well), those are implemented as separate interop layers. Wijmo is completely framework-agnostic, pure JS/HTML/CSS. So when new frameworks come out, we hope we will be able to support them easily as well.

    I’m glad you like the product. We are working hard to add new relevant/useful features and high-quality demos and documentation for the first release, which is coming soon.

    Thanks!

  • Posted 14 September 2017, 2:08 am EST

    Hi Chris & Bernardo.

    Thanks for your responses.

    I hardly wait demos and documentation.

    I know Angular 2.x is only in draft and creating product based on it is to soon.

    Like you said, Wijmo 5 is pure js components. So Wijmo 5 should work inside Polymer. What do you think ? Did you try it ? Build new componets using Wijmo 5 with Polymer could be very useful.

    What about ASP.NET MVC support ? Do you have plans to create MVC helpers ?

    Android L (material design). Are you preparing some styling that Wijmo 5 fits to material design ?

    And finaly: If i using angular directives should intellisense work for directives in

    Visual Studio or WebStorm ?

    Thanks for advance.

    Edvin

  • Posted 14 September 2017, 2:08 am EST

    Hi Edvin

    I have not tried Wijmo 5 with Polymer, but as you said it’s just JavaScript, so it should work fine.

    We do have some samples that use Wijmo 5 in MVC/Razor apps, and that works fine too. But no special support for that. Perhaps Chris can expand on this and on the Android question as well. For now, all I can add is you can simulate Android Material design in CSS to some extent, and that would work well with Wijmo 5 controls (http://www.cssscript.com/android-l-style-animated-ui-button-using-javascript-and-css3/).

    The last part of the question is my favorite, because I am a big fan of IntelliSense. Although we don’t provide it in the beta, it is easy to add and in the to-do list for the very near future. In fact, if you don’t want to wait you can probably try to implement that yourself, here’s a blog that explains how you can do it:

    http://madskristensen.net/post/angularjs-intellisense-in-visual-studio-2012

  • Posted 14 September 2017, 2:08 am EST

    As for the MVC helpers, we have no plans. It seems like most MS devs are leaning towards AngularJS applications and using less server-side rendering. So for now, we are focused on JS.

    If you have genuine interest, I would like to know. And if enough people request it, we are open to it. MVC helpers are just not high on our priority.

  • Posted 31 January 2018, 10:36 pm EST

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels