You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Jurgen Lust (JIRA)" <de...@myfaces.apache.org> on 2006/05/22 15:59:31 UTC

[jira] Commented: (TOMAHAWK-438) Schedule Component TLD changes

    [ http://issues.apache.org/jira/browse/TOMAHAWK-438?page=comments#action_12412778 ] 

Jurgen Lust commented on TOMAHAWK-438:
--------------------------------------

I like you propositions. I will take a look at the patch as soon as possible, and if everything works ok I'll apply it before moving the component to tomahawk, which will probably be tomorrow.

Thanks!

> Schedule Component TLD changes
> ------------------------------
>
>          Key: TOMAHAWK-438
>          URL: http://issues.apache.org/jira/browse/TOMAHAWK-438
>      Project: MyFaces Tomahawk
>         Type: Improvement

>   Components: Schedule
>     Versions: 1.1.3-SNAPSHOT
>  Environment: All
>     Reporter: Julian Ray
>     Assignee: Jurgen Lust
>      Fix For: 1.1.3-SNAPSHOT
>  Attachments: schedule-patch.txt
>
> I would like to propose some changes to the TLD for the sandbox Schedule component as follows:
> [1] Add a requried "mode" property (String) with values "day" "workweek" "week" "month"
> [2] Add an optional "selectedDate" property (Date) value binding which sets the current date
> [3] Change the definition of the "entryRenderer" property to be an optional value binding.
> The reasons for [1] and [2] are that it allows better seperation of the model from the view (and backing bean if used) especially for key view properties. These properties must currently be set on the model which propagates their effect to the view.
> [3] is motivated by a need to subclass ScheduleEntryRenderer and allow additional properties to be used during the rendering. Currently, the property takes a class name and creates an instance using a default constructor.
> I can submit a patch implementing these changes.
> Julian 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira