21 Mar
2007
21 Mar
'07
10 a.m.
On Mar 21, 2007, at 9:52 AM, Luis Arias wrote:
Vincent,
I'm just thinking that one of the requirements for a component
architecture that interacts with the UI is on the order of
granularity. For instance, maybe a component wishes to insert a menu
item some where in the toolbar, or propose a new panel to be available
to the panel manager, or maybe a new feature in the WYSIWYG editor.
Is the page level API that you are discussing here supposed to cover
these types of participation or integration in the UI ?
Another example, let's say we wish to have a component that enables
entering comments that are linked to content in a page and are
displayed "in situ" instead of at the bottom of the page.
Luis, I was only discussing general principles and not details. The
page stuff was only one example of one interface. This is why I said:
"<example - I'm not asking to vote on this, it's just an example to
better visualize what "one Java Interface for each UI contribution"
means>"
:)
Now that said, I need to read Sergiu's emails and answer. That'll
take me a bit as I'm talking at conference today and this is not
something you read quickly. I'll need to digest it :)
Thanks
-Vincent