Currently, activeView is only honored during initial render and cannot be used to programmatically navigate between pages while preserving swipe animations, keyboard navigation, and endless scrolling.

Please add:

• A public API/method to navigate to a specific page programmatically (e.g., scrollTo(index) or controlled activeView support).
• A page/view change event (e.g., onViewChange) that exposes the current page index.
• Built-in support for lazy/on-demand loading scenarios that depend on page change notifications.

This would eliminate the need for DOM-based workarounds (triggering pager dot clicks or querying rendered markup) and enable smooth navigation, lazy loading, and synchronization with external UI components.