You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Prakash Udupa N (JIRA)" <de...@myfaces.apache.org> on 2008/11/11 05:23:44 UTC
[jira] Updated: (TRINIDAD-1243) Adding a change implementation to
the ChangeManager framework
[ https://issues.apache.org/jira/browse/TRINIDAD-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prakash Udupa N updated TRINIDAD-1243:
--------------------------------------
Status: Patch Available (was: Open)
> Adding a change implementation to the ChangeManager framework
> -------------------------------------------------------------
>
> Key: TRINIDAD-1243
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1243
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Affects Versions: 1.2.10-core
> Reporter: Prakash Udupa N
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> The ChangeManager/ChangePersistence framework in the package 'org.myfaces.trinidad.change' provides different implementations of 'org.myfaces.trinidad.change.ComponentChange' and 'org.myfaces.trinidad.change.DocumentChange'. This feature is quite useful, especially in realizing customizable applications.
> This framework is lacking a type of Change implementation that allows components to be moved around in the view tree. A strong usecase for this requirement is in a DesignTime@Runtime kind of applications, where users can customize their applications by Drag&Drop of the components around in a canvas.
> I propose to introduce an implementation of 'org.myfaces.trinidad.change.ComponentChange' and 'org.myfaces.trinidad.change.DocumentChange', called MoveChildComponentChange.
> I'll provide a patch soon with this enhancement to Trinidad.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.