[ http://jira.andromda.org/browse/BPM-277?page=all ]
Wouter Zoons closed BPM-277:
----------------------------
Fix Version: 3.2-RC1
Resolution: Won't Fix
I agree that features such as this one are very useful and improve usability a
lot, but in reality it would become too much to maintain and support, this
would require a non-trivial implementation to say the least .. so unless
someone offers to implement this and can make sure user question can be handled
regarding such a feature I see no possiblity of including it in the codebase
> Tree view for a manageable entities
> -----------------------------------
>
> Key: BPM-277
> URL: http://jira.andromda.org/browse/BPM-277
> Project: Bpm4Struts Cartridge
> Type: Improvement
> Components: CRUD
> Reporter: Andrea Desantis
> Assignee: Wouter Zoons
> Fix For: 3.2-RC1
>
> Sometimes we have to represent an entity as a tree when the table records
> have a gerarchical structure (with parent ref). Es. organization chart, skill
> classification, and so on. It could be very usefull declare an entity "tree
> manageable" and on the crud view see a tree representation. Some actions on
> that tree have to reflect database action: insert, delete, drag and drop,
> rename, ... It should be possible to have a relation with other entities as
> now it do.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.andromda.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
