This would be something similar to the one in the sidebar on this site:
http://verteplace.be/en/guestrooms

Notice the "next" button (>) to cycle through the months. This would be easily accomplished through some block theming, jQuery and a new block within the module. It would however requires some sort of interface to indicate which nodes to generate a block for.

Alternatively, views integration and a default view could likely accomplish the same using the ajax feature.

Comments

fietserwin’s picture

Status: Active » Needs review

I added a "viewport" feature. This javascript/jquery based feature allows to define:
- the number of months to show horizontally and vertically
- the number of months to scroll horizontally or the number of rows of months to scroll vertically
- animation speed
- the elements to bind click event handlers to that starts the scrolling

The feature is based on hiding the non visible months of the calendar. So all months that can be viewed should be part of the initial html sent to the browser (can be set via the "Number of months to display" setting). Thus: no ajax calls to fetch new months.

It does not yet have a user interface to enable and configure it. So some custom coding is still needed, but is described in the documentation of the javascript file.

Any feedback about this feature and if it satisfies what was requested is highly welcomed.

fietserwin’s picture

Version: 7.x-2.x-dev » 7.x-2.2
Status: Needs review » Fixed

The viewport functionality and some example code are now complete and part of the 7.x-2.2 release. I think the viewport satisfies the request of the OP to a large/full extend.

The things that can be seen as missing:
- a user interface to enable and configure it
- the buttons to scroll are not part of the viewport (though the viewport does enable/disable them if the id's are passed in) as the rendering, positioning (weight) w.r.t. the calendar, and labelling will be difficult to catch in a configuration UI.

All in all, I think the request has been satisfied, so I will close this issue. Separate issues may be created for individual ameliorations.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.