I'll get back to this shortly. I'll been busy doing other things.
Behaviours help on some of my cases, they're really one thing I needed,
but I still need a way to control to what pagemap page goes when
constructed. My patch fixes the problem, but I really don't want to use
patched Wicket on
in 1.2 we will have support for partial rendering
So then you don't need it to wrap around a page.
On 11/6/05, Janne Hietamäki [EMAIL PROTECTED] wrote:
Hi,I'm doing some AJAX-stuff, and because there is not yet real support ofrendering single components (and having a URL for a Component) I'm
It is already in CVS HEAD, though not yet accesible through a URL. The
method to call RequestCycle.render(component). It is the first
implementation, so please bare with us if is not perfect yet. Hence,
we appreciate any feedback.
Juergen
On 11/7/05, Johan Compagner [EMAIL PROTECTED] wrote:
in
Juergen Donnerstag wrote:
It is already in CVS HEAD, though not yet accesible through a URL. The
method to call RequestCycle.render(component). It is the first
implementation, so please bare with us if is not perfect yet. Hence,
we appreciate any feedback.
Yep, I have tried that, and I'm
The page must be rendered completly at least once. Thus components can
only be re-rendered. src/test/.../Simple*Test provides some examples.
Juergen
On 11/7/05, Janne Hietamäki [EMAIL PROTECTED] wrote:
Juergen Donnerstag wrote:
It is already in CVS HEAD, though not yet accesible through a
To answer you question: components must be attached to a page. This is
required to find the markup. I don't think we are able to support all
different kind of components without an attached page. Think about
Label etc which don't have an attached markup file.
Juergen
On 11/7/05, Juergen
Juergen Donnerstag wrote:
To answer you question: components must be attached to a page. This is
required to find the markup. I don't think we are able to support all
different kind of components without an attached page. Think about
Label etc which don't have an attached markup file.
Juergen
On 11/7/05, Janne Hietamäki [EMAIL PROTECTED] wrote:
Juergen Donnerstag wrote:
To answer you question: components must be attached to a page. This is
required to find the markup. I don't think we are able to support all
different kind of components without an attached page. Think about
Not a markup container but a panel (that is besides page the one with there own markup)
should be able to render itself completely standalone.
But maybe i am mistaken? juergen?
On 11/7/05, Juergen Donnerstag [EMAIL PROTECTED] wrote:
On 11/7/05, Janne Hietamäki [EMAIL PROTECTED] wrote: Juergen
On 11/7/05, Johan Compagner [EMAIL PROTECTED] wrote:
Not a markup container but a panel (that is besides page the one with there
own markup)
should be able to render itself completely standalone.
But maybe i am mistaken? juergen?
Page and Panel are the only components that could be rendered
Juergen Donnerstag wrote:
Are you sure? Usually you render a page and a textbox which provides
autocompletion. Will you ever render the textbox without prior
rendering a page?
Juergen
Well, yes, I could add all those components to my Page, but that can be
few hundred Panels, and that
Well, yes, I could add all those components to my Page, but that can be
few hundred Panels, and that sound like an overkill to construct.
Specially when probably only few of them will ever be rendered.
Not sure I understand your comment. Lets say you have a standard
wicket application with
Hi,
I'm doing some AJAX-stuff, and because there is not yet real support of
rendering single components (and having a URL for a Component) I'm doing
all this stuff with a AjaxWrapperPage like
public class AjaxWrapperPage extends WebPage {
public AjaxFieldResult(Component component) {
13 matches
Mail list logo
