Premium

Resource virtualization & print

Keep large scheduling surfaces practical by mounting the visible resource or date window with overscan. Print layouts provide a separate presentation path for reviewing schedules outside the interactive viewport.

Loading interactive demo…

What you configure

resourceTimeGrid
Tune the date-by-resource column threshold and overscan.
resourceTimeline
Configure independent resource and slot virtualization thresholds.
print styles
Check page orientation, repeated headings, and your application's print overrides.

Essential integration

This assumes the shared Quick start already provides premiumLicense and, for UI views, premiumCalendarOptions. Only the feature-specific setup is shown.

Feature-specific TypeScript
import { WtsCalendar } from '@wts-calendar/core';
import { resourceSchedulingModule } from '@wts-calendar/core/resource-scheduling';

const calendar = new WtsCalendar({
  ...premiumCalendarOptions,
  plugins: [resourceSchedulingModule],
  view: 'resource-timeline',
  resources: Array.from({ length: 300 }, (_, index) => ({
    id: 'resource-' + index,
    title: 'Resource ' + (index + 1),
  })),
  events: [
    {
      id: 'work',
      title: 'Scheduled work',
      resourceId: 'resource-0',
      start: '2026-09-07',
      end: '2026-09-10',
      isAllDay: true,
    },
  ],
  resourceTimeline: {
    durationDays: 30,
    slotWidth: 100,
    rowMinHeight: 42,
    resourceVirtualizationThreshold: 20,
    resourceOverscan: 2,
    slotVirtualizationThreshold: 15,
    slotOverscan: 2,
  },
});

// Invoke from your application's Print button. Browser print hooks expand the view.
export function printSchedule() {
  window.print();
}

Behavior and lifecycle

  • Virtualization keeps headers, event geometry, selection state, and lifecycle hooks synchronized.
  • Scrolling changes mounted UI, not the underlying resource or event collection.

Limits and responsibilities

  • Virtualized off-screen elements should not be treated as a complete DOM export of the schedule.
  • Browser print results depend on data volume, page size, and host styles; validate the intended print workflow.
Premium

Enable this capability

Optional module
@wts-calendar/core/resource-scheduling
Local capability ID
resource-scheduling · enabled by package-wide Premium

Use the request form to describe your project and deployment origins. Pricing and terms are confirmed privately. A WTS license is separate from provider credentials; do not send passwords or production access tokens.

The live example uses a browser-visible deployment key restricted to this package and approved origins. It does not collect license keys or visitor credentials.

Request Premium pricing

Share the details we need to respond to your request.

Optional for this inquiry, but required before deployment. Add one origin per line without a page path. Registered HTTP localhost origins are allowed for development.

Don’t include license keys, passwords, or confidential information.