Angular 2

[GaryParticipant]

Would like to see adoption of Angular 2 later this year.
Gary

[Peter StoevKeymaster]

Ok, Gary. We’ll think about this.

Best Regards,
Peter Stoev

jQWidgets Team
http://www.jqwidgets.com

[gouletfParticipant]

Yep, I would like to see that happen too!

Frederic

[Peter StoevKeymaster]

Hi Frederic,

We’re following very closely the Angular2 development. Our team is actively working towards evaluating the best possible way to support Angular2 in our UI widgets framework. We’ll announce more details shortly and we can assure you that once Angular2 is released, you will see first-class jQWidgets integration with Angular2.

Best Regards,
Peter Stoev

jQWidgets Team
http://www.jqwidgets.com

[mbassmanParticipant]

Any news on angular 2?

We are starting new projects with angular 2, and it seems a shame to need new components.

thanks,
mike

[Peter StoevKeymaster]

Hi Mike,

As soon as our Angular 2 components are ready, we will publish them on our website. We are still working on this and there is still a lot of work. In the recent releases we will first release Typescript definitions and after that we will have Angular 2 integration.

Best Regards,
Peter Stoev

jQWidgets Team
http://www.jqwidgets.com

[Peter StoevKeymaster]

With our newest release of jQWidgets, Angular 2 Components and Typescript Definitions are now available for all widgets.

Angular 2 Demos – http://www.jqwidgets.com/jquery-widgets-demo/demos/angularjs2-demos/index.htm
Typescript Demos – http://www.jqwidgets.com/jquery-widgets-demo/demos/typescript/index.htm

Soon are expected React JS Components.

Best Regards,
Peter Stoev

jQWidgets Team
http://www.jqwidgets.com

[c-myers1Participant]

Hello Peter,

I’ve waited ages for the ng2 widgets but no joy: what you released seems to be for RC1 but we are on RC5 today and there are huge changes. Or have I misunderstood what it says at http://www.jqwidgets.com/jquery-widgets-documentation/documentation/angular2/angular2.htm?search= especially at:

var ngVer = ‘@2.0.0-rc.1’; // lock in the angular package version; do not let it float to current!

[Peter StoevKeymaster]

Hi c-myers1,

We will update the version the demos refer, soon. I do not think that there will be any changes in the Angular 2 components needed.

For example you may use the following systemjs.config.js with Angular RC5.

(function (global) {
    // map tells the System loader where to look for things
    var map = {
        'app': 'app', // 'dist',
        '@angular': 'https://npmcdn.com/@angular',
        'angular2-in-memory-web-api': 'https://npmcdn.com/angular2-in-memory-web-api',
        'rxjs': 'https://npmcdn.com/rxjs',
        'ts': 'https://npmcdn.com/plugin-typescript@4.0.10/lib/plugin.js',
        'typescript': 'https://npmcdn.com/typescript@1.8.10/lib/typescript.js'
    };
    // packages tells the System loader how to load when no filename and/or no extension
    var packages = {
        'app': { main: 'main.js', defaultExtension: 'js' },
        'rxjs': { defaultExtension: 'js' },
        'angular2-in-memory-web-api': { main: 'index.js', defaultExtension: 'js' },
    };
    var ngPackageNames = [
      'common',
      'compiler',
      'core',
      'forms',
      'http',
      'platform-browser',
      'platform-browser-dynamic',
      'router',
      'router-deprecated',
      'upgrade',
    ];
    // Individual files (~300 requests):
    function packIndex(pkgName) {
        packages['@angular/' + pkgName] = { main: 'index.js', defaultExtension: 'js' };
    }
    // Bundled (~40 requests):
    function packUmd(pkgName) {
        packages['@angular/' + pkgName] = { main: 'bundles/' + pkgName + '.umd.js', defaultExtension: 'js' };
    }
    // Most environments should use UMD; some (Karma) need the individual index files
    var setPackageConfig = System.packageWithIndex ? packIndex : packUmd;
    // Add package entries for angular packages
    ngPackageNames.forEach(setPackageConfig);

    var config = {
        transpiler: 'ts',
        defaultJSExtensions: true,
        typescriptOptions: {
            tsconfig: true
        },
        meta: {
            'typescript': {
                "exports": "ts"
            }
        },
        map: map,
        packages: packages
    }
    System.config(config);
})(this);

Best Regards,
Peter Stoev

jQWidgets Team
http://www.jqwidgets.com/

[adminKeymaster]

We just updated the systemjs.config.js for our angular 2 components demos and they now use Angular 2 RC 5.

[c-myers1Participant]

Thanks but some things are a bit confusing for a newbie to both ng2 and jaw like me. For instance, why are you not using ngModules (I know it’s kind of optional). Also why must use of jaw widgets surface obscure features like ViewChild and AfterViewChecked?

[Peter StoevKeymaster]

For the purpose of our samples we needed to use only the things we used. If you wish, you can use other features of Angular 2.

Best Regards,
Peter Stoev

jQWidgets Team
http://www.jqwidgets.com/

[sna.arunParticipant]

Typescript definitions are missing in jQWidgets node package (For e.g. jqwidgets-ts folder). It will be more developer friendly, if the entire set is available in the package.

[Peter StoevKeymaster]

Hi sna.arun,

Thank you for your opinion.

Best Regards,
Peter Stoev

jQWidgets Team
http://www.jqwidgets.com/

[c-myers1Participant]

@Peter Stoev: My comment is not a criticism but seeking to understand as I’m new to both ng2 and your widgets. I was basically using widgets of another vendor jquery based but evaluating jqwidgets as an option as my old provider will not have ng2 compatible widgets for a while.

Now your write-up at http://www.jqwidgets.com/jquery-widgets-documentation/documentation/angular2/angular2.htm?search= suggests that ViewChild, AfterViewChecked need to be used with any widget used. In some other libraries I’ve seen, these are not explicitly utilized. Can you just make it simple for me to understand?

[Author]

Posts