At first need to mention that we planning to move without changes almost all the functionality. All the RFC's(features not present in 3.3) listed in jira most likelly will be postponed. And one point - macrosubstitutions will be excluded. From all other points of view - we will have the same impl.

That section briefly lists all the features which should present in base impl:

Popup/inline modes

Month markup should be still based on client templates

All 3.3.3 attributes-based presentation customization

All the converters supported in 3.3.3

ajax/client month's switching mode (See note)

Minimal model support in ajax mode. Including two properties for every CalendarDataModelItemImpl. Minimal support - because the macrosubstitution customization excluded from first version for all the components which used it in 3.3.

isDisabled

styleClass

Client-side customization using custom script functions.

Note: Ajax mode/Minimal Model impl's - not estimated during Server Side functionality estimations. So it will be implemented last if will fit the timing.

Not implemented in M4

Client markup still based on client templates. But server side code related to support of macrosubstitutions should not be migrated. We will discuss that customization additionally after Final and add for all related components(tooltip, FileUpload, progressBar, DnDIndicator).

High level tasks for M5

for inline - the same calendar as for enabled but without controls and selection possibility.

Positioning customization.

offcets, jointpoint, direction to be reviewed and corrected/implemented.

simple dataModel support

getStyleClass and isDisabled should be implemented at model for dateItem

preload dates support in client mode

all the other methods from 3.3.x should be present on interface but just documented as not supported.

Ajax month scrolling

Review and implementation of client side events

in 3.3.x we had bunch of events which were added because of late features addition. Should be revised if all of them still needed and event rising should be corrected in some cases(e.g. ondateselected fired before actual selection in case time in pattern)