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/01/08 23:26:27 UTC
[jira] Created: (MYFACES-1012) better customisation features for
schedule component
better customisation features for schedule component
----------------------------------------------------
Key: MYFACES-1012
URL: http://issues.apache.org/jira/browse/MYFACES-1012
Project: MyFaces
Type: Improvement
Components: Sandbox
Environment: all
Reporter: Jurgen Lust
Attachments: schedule.patch
all css classes can now be overridden using component attributes
---
I have completely rewritten the examples. There are now 4 of them, each demonstrating a different feature
---
the themeing mechanism has changed: instead of using the theme id to determine which css file to load, the theme id is now added to the schedule div css class as a suffix: e.g. schedule-detailed-default, schedule-detailed-outlookxp, schedule-detailed-evolution, ...
This makes it easier to use a custom theme: just copy the appriopriate content of the schedule.css file to your own css, and add a suffix to schedule-detailed and schedule-compact
---
introduced the ScheduleEntryRenderer, which renders the content of a schedule entry. By writing an implementation of this
interface, it is now possible to customize what is rendered inside a schedule entry. Using this mechanism, you can now also
assign different colors to the entries of different persons. I think this is a better solution than the patch introduced by bug nr. 976. The changes to the ScheduleModel that were made here, are therefore undone with this patch
---
fixed a bug in the AbstractScheduleModel that sometimes caused the schedule to contain 0 days after submitting.
---
added a property to the ScheduleModel, entrySelected, which returns true if an entry is currently selected. This is a convenience
method which can for example be used in the 'rendered' or 'disabled' flag of a component.
---
added methods to add and remove entries to the ScheduleModel interface.
--
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
[jira] Updated: (MYFACES-1012) better customisation features for
schedule component
Posted by "Jurgen Lust (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/MYFACES-1012?page=all ]
Jurgen Lust updated MYFACES-1012:
---------------------------------
Attachment: tld-patch.patch
added patch for tld only
> better customisation features for schedule component
> ----------------------------------------------------
>
> Key: MYFACES-1012
> URL: http://issues.apache.org/jira/browse/MYFACES-1012
> Project: MyFaces
> Type: Improvement
> Components: Sandbox
> Environment: all
> Reporter: Jurgen Lust
> Assignee: sean schofield
> Attachments: css-patch.patch, schedule.patch, tld-patch.patch
>
> all css classes can now be overridden using component attributes
> ---
> I have completely rewritten the examples. There are now 4 of them, each demonstrating a different feature
> ---
> the themeing mechanism has changed: instead of using the theme id to determine which css file to load, the theme id is now added to the schedule div css class as a suffix: e.g. schedule-detailed-default, schedule-detailed-outlookxp, schedule-detailed-evolution, ...
> This makes it easier to use a custom theme: just copy the appriopriate content of the schedule.css file to your own css, and add a suffix to schedule-detailed and schedule-compact
> ---
> introduced the ScheduleEntryRenderer, which renders the content of a schedule entry. By writing an implementation of this
> interface, it is now possible to customize what is rendered inside a schedule entry. Using this mechanism, you can now also
> assign different colors to the entries of different persons. I think this is a better solution than the patch introduced by bug nr. 976. The changes to the ScheduleModel that were made here, are therefore undone with this patch
> ---
> fixed a bug in the AbstractScheduleModel that sometimes caused the schedule to contain 0 days after submitting.
> ---
> added a property to the ScheduleModel, entrySelected, which returns true if an entry is currently selected. This is a convenience
> method which can for example be used in the 'rendered' or 'disabled' flag of a component.
> ---
> added methods to add and remove entries to the ScheduleModel interface.
--
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
[jira] Closed: (MYFACES-1012) better customisation features for
schedule component
Posted by "sean schofield (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/MYFACES-1012?page=all ]
sean schofield closed MYFACES-1012:
-----------------------------------
Fix Version: Nightly
Resolution: Fixed
> better customisation features for schedule component
> ----------------------------------------------------
>
> Key: MYFACES-1012
> URL: http://issues.apache.org/jira/browse/MYFACES-1012
> Project: MyFaces
> Type: Improvement
> Components: Sandbox
> Environment: all
> Reporter: Jurgen Lust
> Assignee: sean schofield
> Fix For: Nightly
> Attachments: schedule-new.patch, schedule-no-uuid.patch
>
> all css classes can now be overridden using component attributes
> ---
> I have completely rewritten the examples. There are now 4 of them, each demonstrating a different feature
> ---
> the themeing mechanism has changed: instead of using the theme id to determine which css file to load, the theme id is now added to the schedule div css class as a suffix: e.g. schedule-detailed-default, schedule-detailed-outlookxp, schedule-detailed-evolution, ...
> This makes it easier to use a custom theme: just copy the appriopriate content of the schedule.css file to your own css, and add a suffix to schedule-detailed and schedule-compact
> ---
> introduced the ScheduleEntryRenderer, which renders the content of a schedule entry. By writing an implementation of this
> interface, it is now possible to customize what is rendered inside a schedule entry. Using this mechanism, you can now also
> assign different colors to the entries of different persons. I think this is a better solution than the patch introduced by bug nr. 976. The changes to the ScheduleModel that were made here, are therefore undone with this patch
> ---
> fixed a bug in the AbstractScheduleModel that sometimes caused the schedule to contain 0 days after submitting.
> ---
> added a property to the ScheduleModel, entrySelected, which returns true if an entry is currently selected. This is a convenience
> method which can for example be used in the 'rendered' or 'disabled' flag of a component.
> ---
> added methods to add and remove entries to the ScheduleModel interface.
--
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
[jira] Updated: (MYFACES-1012) better customisation features for
schedule component
Posted by "sean schofield (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/MYFACES-1012?page=all ]
sean schofield updated MYFACES-1012:
------------------------------------
Attachment: (was: schedule.patch)
> better customisation features for schedule component
> ----------------------------------------------------
>
> Key: MYFACES-1012
> URL: http://issues.apache.org/jira/browse/MYFACES-1012
> Project: MyFaces
> Type: Improvement
> Components: Sandbox
> Environment: all
> Reporter: Jurgen Lust
> Assignee: sean schofield
> Attachments: schedule-new.patch
>
> all css classes can now be overridden using component attributes
> ---
> I have completely rewritten the examples. There are now 4 of them, each demonstrating a different feature
> ---
> the themeing mechanism has changed: instead of using the theme id to determine which css file to load, the theme id is now added to the schedule div css class as a suffix: e.g. schedule-detailed-default, schedule-detailed-outlookxp, schedule-detailed-evolution, ...
> This makes it easier to use a custom theme: just copy the appriopriate content of the schedule.css file to your own css, and add a suffix to schedule-detailed and schedule-compact
> ---
> introduced the ScheduleEntryRenderer, which renders the content of a schedule entry. By writing an implementation of this
> interface, it is now possible to customize what is rendered inside a schedule entry. Using this mechanism, you can now also
> assign different colors to the entries of different persons. I think this is a better solution than the patch introduced by bug nr. 976. The changes to the ScheduleModel that were made here, are therefore undone with this patch
> ---
> fixed a bug in the AbstractScheduleModel that sometimes caused the schedule to contain 0 days after submitting.
> ---
> added a property to the ScheduleModel, entrySelected, which returns true if an entry is currently selected. This is a convenience
> method which can for example be used in the 'rendered' or 'disabled' flag of a component.
> ---
> added methods to add and remove entries to the ScheduleModel interface.
--
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
[jira] Commented: (MYFACES-1012) better customisation features for
schedule component
Posted by "Martin Marinschek (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/MYFACES-1012?page=comments#action_12362662 ]
Martin Marinschek commented on MYFACES-1012:
--------------------------------------------
I see that Sean is taking over.
regards,
Martin
> better customisation features for schedule component
> ----------------------------------------------------
>
> Key: MYFACES-1012
> URL: http://issues.apache.org/jira/browse/MYFACES-1012
> Project: MyFaces
> Type: Improvement
> Components: Sandbox
> Environment: all
> Reporter: Jurgen Lust
> Assignee: sean schofield
> Attachments: css-patch.patch, schedule.patch, tld-patch.patch
>
> all css classes can now be overridden using component attributes
> ---
> I have completely rewritten the examples. There are now 4 of them, each demonstrating a different feature
> ---
> the themeing mechanism has changed: instead of using the theme id to determine which css file to load, the theme id is now added to the schedule div css class as a suffix: e.g. schedule-detailed-default, schedule-detailed-outlookxp, schedule-detailed-evolution, ...
> This makes it easier to use a custom theme: just copy the appriopriate content of the schedule.css file to your own css, and add a suffix to schedule-detailed and schedule-compact
> ---
> introduced the ScheduleEntryRenderer, which renders the content of a schedule entry. By writing an implementation of this
> interface, it is now possible to customize what is rendered inside a schedule entry. Using this mechanism, you can now also
> assign different colors to the entries of different persons. I think this is a better solution than the patch introduced by bug nr. 976. The changes to the ScheduleModel that were made here, are therefore undone with this patch
> ---
> fixed a bug in the AbstractScheduleModel that sometimes caused the schedule to contain 0 days after submitting.
> ---
> added a property to the ScheduleModel, entrySelected, which returns true if an entry is currently selected. This is a convenience
> method which can for example be used in the 'rendered' or 'disabled' flag of a component.
> ---
> added methods to add and remove entries to the ScheduleModel interface.
--
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
[jira] Commented: (MYFACES-1012) better customisation features for
schedule component
Posted by "sean schofield (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/MYFACES-1012?page=comments#action_12362667 ]
sean schofield commented on MYFACES-1012:
-----------------------------------------
The latest patch seems to just fix the attributes. I need the one that fixes myfaces_sandbox.tld (at least that was in your original patch.) I think the problem was the TLD was in the wrong location.
Also, maven is complaining about several classes not compiling including ScheduleExampleHandler.java (class or interface expected.) I need to run to a class. I will be back in a couple of hours and will finish up your patch. In the meantime, try a clean checkout and apply your own patch. See if you can't get it working.
> better customisation features for schedule component
> ----------------------------------------------------
>
> Key: MYFACES-1012
> URL: http://issues.apache.org/jira/browse/MYFACES-1012
> Project: MyFaces
> Type: Improvement
> Components: Sandbox
> Environment: all
> Reporter: Jurgen Lust
> Assignee: sean schofield
> Attachments: css-patch.patch, schedule.patch, tld-patch.patch
>
> all css classes can now be overridden using component attributes
> ---
> I have completely rewritten the examples. There are now 4 of them, each demonstrating a different feature
> ---
> the themeing mechanism has changed: instead of using the theme id to determine which css file to load, the theme id is now added to the schedule div css class as a suffix: e.g. schedule-detailed-default, schedule-detailed-outlookxp, schedule-detailed-evolution, ...
> This makes it easier to use a custom theme: just copy the appriopriate content of the schedule.css file to your own css, and add a suffix to schedule-detailed and schedule-compact
> ---
> introduced the ScheduleEntryRenderer, which renders the content of a schedule entry. By writing an implementation of this
> interface, it is now possible to customize what is rendered inside a schedule entry. Using this mechanism, you can now also
> assign different colors to the entries of different persons. I think this is a better solution than the patch introduced by bug nr. 976. The changes to the ScheduleModel that were made here, are therefore undone with this patch
> ---
> fixed a bug in the AbstractScheduleModel that sometimes caused the schedule to contain 0 days after submitting.
> ---
> added a property to the ScheduleModel, entrySelected, which returns true if an entry is currently selected. This is a convenience
> method which can for example be used in the 'rendered' or 'disabled' flag of a component.
> ---
> added methods to add and remove entries to the ScheduleModel interface.
--
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
[jira] Commented: (MYFACES-1012) better customisation features for
schedule component
Posted by "Martin Marinschek (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/MYFACES-1012?page=comments#action_12362661 ]
Martin Marinschek commented on MYFACES-1012:
--------------------------------------------
I just tried to commit your patch, and I seem not to be able to do it - the JSP files are not patchable.
Something like no URL is available for these files?
regards,
Martin
> better customisation features for schedule component
> ----------------------------------------------------
>
> Key: MYFACES-1012
> URL: http://issues.apache.org/jira/browse/MYFACES-1012
> Project: MyFaces
> Type: Improvement
> Components: Sandbox
> Environment: all
> Reporter: Jurgen Lust
> Assignee: sean schofield
> Attachments: css-patch.patch, schedule.patch, tld-patch.patch
>
> all css classes can now be overridden using component attributes
> ---
> I have completely rewritten the examples. There are now 4 of them, each demonstrating a different feature
> ---
> the themeing mechanism has changed: instead of using the theme id to determine which css file to load, the theme id is now added to the schedule div css class as a suffix: e.g. schedule-detailed-default, schedule-detailed-outlookxp, schedule-detailed-evolution, ...
> This makes it easier to use a custom theme: just copy the appriopriate content of the schedule.css file to your own css, and add a suffix to schedule-detailed and schedule-compact
> ---
> introduced the ScheduleEntryRenderer, which renders the content of a schedule entry. By writing an implementation of this
> interface, it is now possible to customize what is rendered inside a schedule entry. Using this mechanism, you can now also
> assign different colors to the entries of different persons. I think this is a better solution than the patch introduced by bug nr. 976. The changes to the ScheduleModel that were made here, are therefore undone with this patch
> ---
> fixed a bug in the AbstractScheduleModel that sometimes caused the schedule to contain 0 days after submitting.
> ---
> added a property to the ScheduleModel, entrySelected, which returns true if an entry is currently selected. This is a convenience
> method which can for example be used in the 'rendered' or 'disabled' flag of a component.
> ---
> added methods to add and remove entries to the ScheduleModel interface.
--
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
[jira] Updated: (MYFACES-1012) better customisation features for
schedule component
Posted by "sean schofield (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/MYFACES-1012?page=all ]
sean schofield updated MYFACES-1012:
------------------------------------
Attachment: (was: tld-patch.patch)
> better customisation features for schedule component
> ----------------------------------------------------
>
> Key: MYFACES-1012
> URL: http://issues.apache.org/jira/browse/MYFACES-1012
> Project: MyFaces
> Type: Improvement
> Components: Sandbox
> Environment: all
> Reporter: Jurgen Lust
> Assignee: sean schofield
> Attachments: schedule-new.patch
>
> all css classes can now be overridden using component attributes
> ---
> I have completely rewritten the examples. There are now 4 of them, each demonstrating a different feature
> ---
> the themeing mechanism has changed: instead of using the theme id to determine which css file to load, the theme id is now added to the schedule div css class as a suffix: e.g. schedule-detailed-default, schedule-detailed-outlookxp, schedule-detailed-evolution, ...
> This makes it easier to use a custom theme: just copy the appriopriate content of the schedule.css file to your own css, and add a suffix to schedule-detailed and schedule-compact
> ---
> introduced the ScheduleEntryRenderer, which renders the content of a schedule entry. By writing an implementation of this
> interface, it is now possible to customize what is rendered inside a schedule entry. Using this mechanism, you can now also
> assign different colors to the entries of different persons. I think this is a better solution than the patch introduced by bug nr. 976. The changes to the ScheduleModel that were made here, are therefore undone with this patch
> ---
> fixed a bug in the AbstractScheduleModel that sometimes caused the schedule to contain 0 days after submitting.
> ---
> added a property to the ScheduleModel, entrySelected, which returns true if an entry is currently selected. This is a convenience
> method which can for example be used in the 'rendered' or 'disabled' flag of a component.
> ---
> added methods to add and remove entries to the ScheduleModel interface.
--
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
[jira] Updated: (MYFACES-1012) better customisation features for
schedule component
Posted by "sean schofield (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/MYFACES-1012?page=all ]
sean schofield updated MYFACES-1012:
------------------------------------
Attachment: (was: css-patch.patch)
> better customisation features for schedule component
> ----------------------------------------------------
>
> Key: MYFACES-1012
> URL: http://issues.apache.org/jira/browse/MYFACES-1012
> Project: MyFaces
> Type: Improvement
> Components: Sandbox
> Environment: all
> Reporter: Jurgen Lust
> Assignee: sean schofield
> Attachments: schedule-new.patch
>
> all css classes can now be overridden using component attributes
> ---
> I have completely rewritten the examples. There are now 4 of them, each demonstrating a different feature
> ---
> the themeing mechanism has changed: instead of using the theme id to determine which css file to load, the theme id is now added to the schedule div css class as a suffix: e.g. schedule-detailed-default, schedule-detailed-outlookxp, schedule-detailed-evolution, ...
> This makes it easier to use a custom theme: just copy the appriopriate content of the schedule.css file to your own css, and add a suffix to schedule-detailed and schedule-compact
> ---
> introduced the ScheduleEntryRenderer, which renders the content of a schedule entry. By writing an implementation of this
> interface, it is now possible to customize what is rendered inside a schedule entry. Using this mechanism, you can now also
> assign different colors to the entries of different persons. I think this is a better solution than the patch introduced by bug nr. 976. The changes to the ScheduleModel that were made here, are therefore undone with this patch
> ---
> fixed a bug in the AbstractScheduleModel that sometimes caused the schedule to contain 0 days after submitting.
> ---
> added a property to the ScheduleModel, entrySelected, which returns true if an entry is currently selected. This is a convenience
> method which can for example be used in the 'rendered' or 'disabled' flag of a component.
> ---
> added methods to add and remove entries to the ScheduleModel interface.
--
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
[jira] Updated: (MYFACES-1012) better customisation features for
schedule component
Posted by "Jurgen Lust (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/MYFACES-1012?page=all ]
Jurgen Lust updated MYFACES-1012:
---------------------------------
Attachment: schedule-no-uuid.patch
removed UUID dependency
> better customisation features for schedule component
> ----------------------------------------------------
>
> Key: MYFACES-1012
> URL: http://issues.apache.org/jira/browse/MYFACES-1012
> Project: MyFaces
> Type: Improvement
> Components: Sandbox
> Environment: all
> Reporter: Jurgen Lust
> Assignee: sean schofield
> Attachments: schedule-new.patch, schedule-no-uuid.patch
>
> all css classes can now be overridden using component attributes
> ---
> I have completely rewritten the examples. There are now 4 of them, each demonstrating a different feature
> ---
> the themeing mechanism has changed: instead of using the theme id to determine which css file to load, the theme id is now added to the schedule div css class as a suffix: e.g. schedule-detailed-default, schedule-detailed-outlookxp, schedule-detailed-evolution, ...
> This makes it easier to use a custom theme: just copy the appriopriate content of the schedule.css file to your own css, and add a suffix to schedule-detailed and schedule-compact
> ---
> introduced the ScheduleEntryRenderer, which renders the content of a schedule entry. By writing an implementation of this
> interface, it is now possible to customize what is rendered inside a schedule entry. Using this mechanism, you can now also
> assign different colors to the entries of different persons. I think this is a better solution than the patch introduced by bug nr. 976. The changes to the ScheduleModel that were made here, are therefore undone with this patch
> ---
> fixed a bug in the AbstractScheduleModel that sometimes caused the schedule to contain 0 days after submitting.
> ---
> added a property to the ScheduleModel, entrySelected, which returns true if an entry is currently selected. This is a convenience
> method which can for example be used in the 'rendered' or 'disabled' flag of a component.
> ---
> added methods to add and remove entries to the ScheduleModel interface.
--
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
[jira] Updated: (MYFACES-1012) better customisation features for
schedule component
Posted by "Jurgen Lust (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/MYFACES-1012?page=all ]
Jurgen Lust updated MYFACES-1012:
---------------------------------
Attachment: tld-patch.patch
correct tld patch added
> better customisation features for schedule component
> ----------------------------------------------------
>
> Key: MYFACES-1012
> URL: http://issues.apache.org/jira/browse/MYFACES-1012
> Project: MyFaces
> Type: Improvement
> Components: Sandbox
> Environment: all
> Reporter: Jurgen Lust
> Assignee: sean schofield
> Attachments: css-patch.patch, schedule.patch, tld-patch.patch, tld-patch.patch
>
> all css classes can now be overridden using component attributes
> ---
> I have completely rewritten the examples. There are now 4 of them, each demonstrating a different feature
> ---
> the themeing mechanism has changed: instead of using the theme id to determine which css file to load, the theme id is now added to the schedule div css class as a suffix: e.g. schedule-detailed-default, schedule-detailed-outlookxp, schedule-detailed-evolution, ...
> This makes it easier to use a custom theme: just copy the appriopriate content of the schedule.css file to your own css, and add a suffix to schedule-detailed and schedule-compact
> ---
> introduced the ScheduleEntryRenderer, which renders the content of a schedule entry. By writing an implementation of this
> interface, it is now possible to customize what is rendered inside a schedule entry. Using this mechanism, you can now also
> assign different colors to the entries of different persons. I think this is a better solution than the patch introduced by bug nr. 976. The changes to the ScheduleModel that were made here, are therefore undone with this patch
> ---
> fixed a bug in the AbstractScheduleModel that sometimes caused the schedule to contain 0 days after submitting.
> ---
> added a property to the ScheduleModel, entrySelected, which returns true if an entry is currently selected. This is a convenience
> method which can for example be used in the 'rendered' or 'disabled' flag of a component.
> ---
> added methods to add and remove entries to the ScheduleModel interface.
--
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
[jira] Updated: (MYFACES-1012) better customisation features for
schedule component
Posted by "Jurgen Lust (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/MYFACES-1012?page=all ]
Jurgen Lust updated MYFACES-1012:
---------------------------------
Attachment: schedule.patch
> better customisation features for schedule component
> ----------------------------------------------------
>
> Key: MYFACES-1012
> URL: http://issues.apache.org/jira/browse/MYFACES-1012
> Project: MyFaces
> Type: Improvement
> Components: Sandbox
> Environment: all
> Reporter: Jurgen Lust
> Attachments: schedule.patch
>
> all css classes can now be overridden using component attributes
> ---
> I have completely rewritten the examples. There are now 4 of them, each demonstrating a different feature
> ---
> the themeing mechanism has changed: instead of using the theme id to determine which css file to load, the theme id is now added to the schedule div css class as a suffix: e.g. schedule-detailed-default, schedule-detailed-outlookxp, schedule-detailed-evolution, ...
> This makes it easier to use a custom theme: just copy the appriopriate content of the schedule.css file to your own css, and add a suffix to schedule-detailed and schedule-compact
> ---
> introduced the ScheduleEntryRenderer, which renders the content of a schedule entry. By writing an implementation of this
> interface, it is now possible to customize what is rendered inside a schedule entry. Using this mechanism, you can now also
> assign different colors to the entries of different persons. I think this is a better solution than the patch introduced by bug nr. 976. The changes to the ScheduleModel that were made here, are therefore undone with this patch
> ---
> fixed a bug in the AbstractScheduleModel that sometimes caused the schedule to contain 0 days after submitting.
> ---
> added a property to the ScheduleModel, entrySelected, which returns true if an entry is currently selected. This is a convenience
> method which can for example be used in the 'rendered' or 'disabled' flag of a component.
> ---
> added methods to add and remove entries to the ScheduleModel interface.
--
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
[jira] Updated: (MYFACES-1012) better customisation features for
schedule component
Posted by "sean schofield (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/MYFACES-1012?page=all ]
sean schofield updated MYFACES-1012:
------------------------------------
Attachment: (was: tld-patch.patch)
> better customisation features for schedule component
> ----------------------------------------------------
>
> Key: MYFACES-1012
> URL: http://issues.apache.org/jira/browse/MYFACES-1012
> Project: MyFaces
> Type: Improvement
> Components: Sandbox
> Environment: all
> Reporter: Jurgen Lust
> Assignee: sean schofield
> Attachments: css-patch.patch, schedule.patch, tld-patch.patch
>
> all css classes can now be overridden using component attributes
> ---
> I have completely rewritten the examples. There are now 4 of them, each demonstrating a different feature
> ---
> the themeing mechanism has changed: instead of using the theme id to determine which css file to load, the theme id is now added to the schedule div css class as a suffix: e.g. schedule-detailed-default, schedule-detailed-outlookxp, schedule-detailed-evolution, ...
> This makes it easier to use a custom theme: just copy the appriopriate content of the schedule.css file to your own css, and add a suffix to schedule-detailed and schedule-compact
> ---
> introduced the ScheduleEntryRenderer, which renders the content of a schedule entry. By writing an implementation of this
> interface, it is now possible to customize what is rendered inside a schedule entry. Using this mechanism, you can now also
> assign different colors to the entries of different persons. I think this is a better solution than the patch introduced by bug nr. 976. The changes to the ScheduleModel that were made here, are therefore undone with this patch
> ---
> fixed a bug in the AbstractScheduleModel that sometimes caused the schedule to contain 0 days after submitting.
> ---
> added a property to the ScheduleModel, entrySelected, which returns true if an entry is currently selected. This is a convenience
> method which can for example be used in the 'rendered' or 'disabled' flag of a component.
> ---
> added methods to add and remove entries to the ScheduleModel interface.
--
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
[jira] Commented: (MYFACES-1012) better customisation features for
schedule component
Posted by "sean schofield (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/MYFACES-1012?page=comments#action_12362689 ]
sean schofield commented on MYFACES-1012:
-----------------------------------------
New problem: the code relies on UUID which is a JDK 1.5 construct. We're trying to stay JDK 1.3 compatible for the time being. Can you rework the patch to be JDK neutral?
> better customisation features for schedule component
> ----------------------------------------------------
>
> Key: MYFACES-1012
> URL: http://issues.apache.org/jira/browse/MYFACES-1012
> Project: MyFaces
> Type: Improvement
> Components: Sandbox
> Environment: all
> Reporter: Jurgen Lust
> Assignee: sean schofield
> Attachments: schedule-new.patch
>
> all css classes can now be overridden using component attributes
> ---
> I have completely rewritten the examples. There are now 4 of them, each demonstrating a different feature
> ---
> the themeing mechanism has changed: instead of using the theme id to determine which css file to load, the theme id is now added to the schedule div css class as a suffix: e.g. schedule-detailed-default, schedule-detailed-outlookxp, schedule-detailed-evolution, ...
> This makes it easier to use a custom theme: just copy the appriopriate content of the schedule.css file to your own css, and add a suffix to schedule-detailed and schedule-compact
> ---
> introduced the ScheduleEntryRenderer, which renders the content of a schedule entry. By writing an implementation of this
> interface, it is now possible to customize what is rendered inside a schedule entry. Using this mechanism, you can now also
> assign different colors to the entries of different persons. I think this is a better solution than the patch introduced by bug nr. 976. The changes to the ScheduleModel that were made here, are therefore undone with this patch
> ---
> fixed a bug in the AbstractScheduleModel that sometimes caused the schedule to contain 0 days after submitting.
> ---
> added a property to the ScheduleModel, entrySelected, which returns true if an entry is currently selected. This is a convenience
> method which can for example be used in the 'rendered' or 'disabled' flag of a component.
> ---
> added methods to add and remove entries to the ScheduleModel interface.
--
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
[jira] Updated: (MYFACES-1012) better customisation features for
schedule component
Posted by "Jurgen Lust (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/MYFACES-1012?page=all ]
Jurgen Lust updated MYFACES-1012:
---------------------------------
Attachment: css-patch.patch
added patch for the css only
> better customisation features for schedule component
> ----------------------------------------------------
>
> Key: MYFACES-1012
> URL: http://issues.apache.org/jira/browse/MYFACES-1012
> Project: MyFaces
> Type: Improvement
> Components: Sandbox
> Environment: all
> Reporter: Jurgen Lust
> Assignee: sean schofield
> Attachments: css-patch.patch, schedule.patch, tld-patch.patch
>
> all css classes can now be overridden using component attributes
> ---
> I have completely rewritten the examples. There are now 4 of them, each demonstrating a different feature
> ---
> the themeing mechanism has changed: instead of using the theme id to determine which css file to load, the theme id is now added to the schedule div css class as a suffix: e.g. schedule-detailed-default, schedule-detailed-outlookxp, schedule-detailed-evolution, ...
> This makes it easier to use a custom theme: just copy the appriopriate content of the schedule.css file to your own css, and add a suffix to schedule-detailed and schedule-compact
> ---
> introduced the ScheduleEntryRenderer, which renders the content of a schedule entry. By writing an implementation of this
> interface, it is now possible to customize what is rendered inside a schedule entry. Using this mechanism, you can now also
> assign different colors to the entries of different persons. I think this is a better solution than the patch introduced by bug nr. 976. The changes to the ScheduleModel that were made here, are therefore undone with this patch
> ---
> fixed a bug in the AbstractScheduleModel that sometimes caused the schedule to contain 0 days after submitting.
> ---
> added a property to the ScheduleModel, entrySelected, which returns true if an entry is currently selected. This is a convenience
> method which can for example be used in the 'rendered' or 'disabled' flag of a component.
> ---
> added methods to add and remove entries to the ScheduleModel interface.
--
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
[jira] Updated: (MYFACES-1012) better customisation features for
schedule component
Posted by "Jurgen Lust (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/MYFACES-1012?page=all ]
Jurgen Lust updated MYFACES-1012:
---------------------------------
Attachment: schedule-new.patch
new schedule patch added. This one replaces the previous three
> better customisation features for schedule component
> ----------------------------------------------------
>
> Key: MYFACES-1012
> URL: http://issues.apache.org/jira/browse/MYFACES-1012
> Project: MyFaces
> Type: Improvement
> Components: Sandbox
> Environment: all
> Reporter: Jurgen Lust
> Assignee: sean schofield
> Attachments: css-patch.patch, schedule-new.patch, schedule.patch, tld-patch.patch
>
> all css classes can now be overridden using component attributes
> ---
> I have completely rewritten the examples. There are now 4 of them, each demonstrating a different feature
> ---
> the themeing mechanism has changed: instead of using the theme id to determine which css file to load, the theme id is now added to the schedule div css class as a suffix: e.g. schedule-detailed-default, schedule-detailed-outlookxp, schedule-detailed-evolution, ...
> This makes it easier to use a custom theme: just copy the appriopriate content of the schedule.css file to your own css, and add a suffix to schedule-detailed and schedule-compact
> ---
> introduced the ScheduleEntryRenderer, which renders the content of a schedule entry. By writing an implementation of this
> interface, it is now possible to customize what is rendered inside a schedule entry. Using this mechanism, you can now also
> assign different colors to the entries of different persons. I think this is a better solution than the patch introduced by bug nr. 976. The changes to the ScheduleModel that were made here, are therefore undone with this patch
> ---
> fixed a bug in the AbstractScheduleModel that sometimes caused the schedule to contain 0 days after submitting.
> ---
> added a property to the ScheduleModel, entrySelected, which returns true if an entry is currently selected. This is a convenience
> method which can for example be used in the 'rendered' or 'disabled' flag of a component.
> ---
> added methods to add and remove entries to the ScheduleModel interface.
--
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