[richfaces-planning-issues] [JBoss JIRA] Commented: (RFPL-985) Calendar: documentation review and promotion

Ilya Shaikovsky (JIRA) jira-events at lists.jboss.org
Thu Feb 10 09:31:47 EST 2011


    [ https://issues.jboss.org/browse/RFPL-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581370#comment-12581370 ] 

Ilya Shaikovsky commented on RFPL-985:
--------------------------------------

9.2.1. 
"Basic usage of the <rich:calendar> component requires only the value attribute, which holds the currently selected date. Example 9.3, “Basic usage” shows a basic declaration, with the value pointing to a data model. "
I'm confused with dataModel word there. Please change to just "bean property which hold the selected date". Or just cut to have "“Basic usage” shows a basic declaration:"

"9.2.2. Using a data model" - the only thing which is not really clear for now - why I need that dataModel. Also it described in the way I'm starting to think that it's required. I propose at least to change first sentence to
"The <rich:calendar> component supports two different ways of loading additional data from server side for calendar look and feel customization through defining the mode and dataModel attributes. When mode not specified..."

"9.2.3. Client-side customization" A few words about how it works like "dayDisableFunction defined with the Java Script function name which is called for every day of the month and should return if the day is enabled for selection. And dayClassFunction attribute works pretty similar but returning styleClass for each day.

GENERAL POINT to 2 points above.. I prefer to see them after the behavior and appearance and time of the day sections. Them are really more specific and complex features. And I think it's more smooth to start from basic customization points.

"The styling and appearance of the calendar can be fully customized using facets."... I'm really sorry if that is my fault, but facets are not supported at all. And even when it will be added {somepart} customizations will not be there. So let's remove the paragraph and image.

general to add: the component still misses localization of labels info but let's create separate task for that for future in order to finish doc at some point for final. Also additional task on extending the dataModel section with the details and code should be created.

> Calendar: documentation review and promotion
> --------------------------------------------
>
>                 Key: RFPL-985
>                 URL: https://issues.jboss.org/browse/RFPL-985
>             Project: RichFaces Planning
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: components, doc
>    Affects Versions: 4.0.0.Milestone2
>            Reporter: Ilya Shaikovsky
>            Assignee: Ilya Shaikovsky
>             Fix For: 4.0.0.Milestone6
>
>         Attachments: calendar 15_11_10.rtf, calendar.odt
>
>


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the richfaces-planning-issues mailing list