/*! * * Wijmo Library 5.20251.40 * https://developer.mescius.com/wijmo * * Copyright(c) MESCIUS inc. All rights reserved. * * Licensed under the End-User License Agreement For MESCIUS Wijmo Software. * us.sales@mescius.com * https://developer.mescius.com/wijmo/licensing * */ /** * {@module wijmo.angular2.viewer} * Contains Angular 2 components for the wijmo.viewer module. * * wijmo.angular2.viewer is an external TypeScript module that can be imported to your code * using its ambient module name. For example: * * 
import * as wjViewer from 'wijmo/wijmo.angular2.viewer';
*  
* @Component({
*     directives: [wjViewer.WjReportViewer, wjViewer.WjPdfViewer],
*     template: `
*       <wj-report-viewer [reportName]="sales" [serviceUrl]="'webserviceApi'">
*       </wj-report-viewer;`,
*     selector: 'my-cmp',
* })
* export class MyCmp {
*     data: any[];
* }
* */ /** * */ export declare var ___keepComment: any; import { EventEmitter, AfterViewInit, ElementRef, Injector, OnInit, OnDestroy } from '@angular/core'; import { IWjComponentMetadata, IWjComponentMeta } from 'wijmo/wijmo.angular2.directiveBase'; import * as wjcViewer from 'wijmo/wijmo.viewer'; declare var wjReportViewerMeta: IWjComponentMeta; export { wjReportViewerMeta }; /** * Angular 2 component for the {@link wijmo.viewer.ReportViewer} control. * * Use the wj-report-viewer component to add ReportViewer controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjReportViewer component is derived from the ReportViewer control and * inherits all its properties, events and methods. */ export declare class WjReportViewer extends wjcViewer.ReportViewer implements OnInit, OnDestroy, AfterViewInit { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is ''. */ wjModelProperty: string; /** * Allows you to override the global WjOptions.asyncBindings setting for this specific component. * See the WjOptions.{@link WjOptions.asyncBindings} property description for details. */ asyncBindings: boolean; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo pageIndexChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional pageIndexChanged Wijmo event name. */ pageIndexChangedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo viewModeChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional viewModeChanged Wijmo event name. */ viewModeChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the viewMode property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the viewModeChange event name. */ viewModeChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo mouseModeChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional mouseModeChanged Wijmo event name. */ mouseModeChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the mouseMode property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the mouseModeChange event name. */ mouseModeChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo fullScreenChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional fullScreenChanged Wijmo event name. */ fullScreenChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the fullScreen property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the fullScreenChange event name. */ fullScreenChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo zoomFactorChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional zoomFactorChanged Wijmo event name. */ zoomFactorChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the zoomFactor property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the zoomFactorChange event name. */ zoomFactorChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo zoomModeChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional zoomModeChanged Wijmo event name. */ zoomModeChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the zoomMode property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the zoomModeChange event name. */ zoomModeChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo queryLoadingData event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional queryLoadingData Wijmo event name. */ queryLoadingDataNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo beforeSendRequest event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional beforeSendRequest Wijmo event name. */ beforeSendRequestNg: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; } declare var wjPdfViewerMeta: IWjComponentMeta; export { wjPdfViewerMeta }; /** * Angular 2 component for the {@link wijmo.viewer.PdfViewer} control. * * Use the wj-pdf-viewer component to add PdfViewer controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjPdfViewer component is derived from the PdfViewer control and * inherits all its properties, events and methods. */ export declare class WjPdfViewer extends wjcViewer.PdfViewer implements OnInit, OnDestroy, AfterViewInit { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is ''. */ wjModelProperty: string; /** * Allows you to override the global WjOptions.asyncBindings setting for this specific component. * See the WjOptions.{@link WjOptions.asyncBindings} property description for details. */ asyncBindings: boolean; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo pageIndexChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional pageIndexChanged Wijmo event name. */ pageIndexChangedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo viewModeChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional viewModeChanged Wijmo event name. */ viewModeChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the viewMode property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the viewModeChange event name. */ viewModeChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo mouseModeChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional mouseModeChanged Wijmo event name. */ mouseModeChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the mouseMode property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the mouseModeChange event name. */ mouseModeChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo fullScreenChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional fullScreenChanged Wijmo event name. */ fullScreenChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the fullScreen property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the fullScreenChange event name. */ fullScreenChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo zoomFactorChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional zoomFactorChanged Wijmo event name. */ zoomFactorChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the zoomFactor property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the zoomFactorChange event name. */ zoomFactorChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo zoomModeChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional zoomModeChanged Wijmo event name. */ zoomModeChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the zoomMode property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the zoomModeChange event name. */ zoomModeChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo queryLoadingData event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional queryLoadingData Wijmo event name. */ queryLoadingDataNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo beforeSendRequest event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional beforeSendRequest Wijmo event name. */ beforeSendRequestNg: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; } export declare class WjViewerModule { }