[
https://issues.apache.org/jira/browse/PIVOT-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868682#action_12868682
]
Noel Grandin commented on PIVOT-31:
-----------------------------------
Greg, that's fine by me.
WRT the ComponentNode use-case you mentioned, that sounds potentially very
useful, but it brings some interesting problems
Problem 1
--------------
It means that the Document model is no longer share-able between multiple
TextArea instances, because the Component will need to get inserted into the
TextArea's containment hierarchy.
I don't see it as a real problem, it's just something that will need to get
noted in the docs and checked for (with nice exceptions) in the code.
Problem 2
--------------
Keyboard/mouse/focus interaction is going to be "interesting" with editable
documents and live components, and will likely lead to some surprising results
when people stick Components into their documents.
I'm inclined to say that we should enforce that we only support live components
in documents in non-editable TextArea's.
> Add rich text support to TextArea
> ---------------------------------
>
> Key: PIVOT-31
> URL: https://issues.apache.org/jira/browse/PIVOT-31
> Project: Pivot
> Issue Type: Improvement
> Components: wtk
> Reporter: Greg Brown
> Assignee: Greg Brown
> Fix For: 1.6
>
> Attachments: patch.txt, patch.txt
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
