In the past, I created 2 new components to make PPR easier from a
declarative stand point. At the time, Adam Winer disagreed with their
inclusion. Now, I wanted to see if there would be any objections to
such components.
I was thinking that that they would go in the sandbox first, then if
+1 Hi, I am not sure about the namespace but I would like to see those
components included. I guess you mean something like a4j:support,
right? And I happen to have that need from time to time...
Cheers,
Bruno
2008/5/15 Andrew Robinson <[EMAIL PROTECTED]>:
> In the past, I created 2 new componen
Andrew Robinson said the following On 5/14/2008 6:40 PM PT:
In the past, I created 2 new components to make PPR easier from a
declarative stand point. At the time, Adam Winer disagreed with their
inclusion. Now, I wanted to see if there would be any objections to
such components.
Adam is pretty
He mentioned ways to do it using backing beans and non-declarative
ways. He also didn't like my "always render" functionality of one of
the components.
Here are the links for just the 2 components that I already did and
bugs and discussions surrounding them (but I think there is room for
more alon
Why doesn't Adam's proposal:
This all seems like enormous overkill *just* to get messages
sent down. We have Javascript that can insert messages
on the client. All we need to do is lean slightly on that code
to reuse it for inserting server-side messages, and this'll work fine
without any archi
Taking one use case and putting it at the framework level will not
address all possible use cases. The desire to have something always
rendered does not have to be limited to messages. Furthermore, this
assumes that messages are always shown using the Trinidad framework,
which is a bad assumption.
Andrew Robinson said the following On 5/15/2008 12:08 PM PT:
Taking one use case and putting it at the framework level will not
address all possible use cases. The desire to have something always
rendered does not have to be limited to messages. Furthermore, this
assumes that messages are always
I would like to get back on track to the original subject and not let
the messaging subject hijack the thread.
Original topic:
Is there enough interest from the developer community in supporting
non-HTML PPR based components oriented for making PPR more declarative
and extend PPR support for non-T
I am not that thrilled to treat ajax/ppr as a special case. Those
components would do that (IMO).
Sent from my iPod.
Am 15.05.2008 um 23:02 schrieb "Andrew Robinson" <[EMAIL PROTECTED]
>:
I would like to get back on track to the original subject and not let
the messaging subject hijack the
OK, looking at the rest of the JIRA issues:
https://issues.apache.org/jira/browse/TRINIDAD-664
Is a request for a component to add partial trigger functionality to
non-Trinidad components. The supplied code is uncommented, so some of
the proposed functionality is unclear, however this raises
I think that there are some good things to think about and talk about
here. I just don't have time at the moment to really dive into this.
Just wanted to respond so as not to look like I am ignoring the
response.
-A
On Fri, May 16, 2008 at 11:08 AM, Blake Sullivan
<[EMAIL PROTECTED]> wrote:
> OK,
11 matches
Mail list logo
