Re: Accessing the Markup of a Component

[Sven Meier]

Hi,

there's a difference how borders load markup for their children.

Without any border involved (TestPage1), 
MarkupContainer#getMarkup(child) asks a DefaultMarkupSourcingStrategy to 
resolve the markup, which does some magic to support 
TransparentWebMarkupContainers.


Border#getMarkup(child) on the other hand (TestPage2) just uses the 
fragment of its border to search for that markup.


So it seems your combined usage of TransparentWebMarkupContainers inside 
a border and  is not supported at the moment.


Have fun
Sven


Am 01.06.2018 um 09:48 schrieb Dirk Forchel:

We have a problem accessing the markup (Component#getMarkup()) of a Panel
while inizializing the panel component. Is it ensured, that
Component#getMarkup() always returns an appropriate markup (markup tag)
during initializion?
As soon as we have a Border component, a TransparentWebMarkupContainer and a
corresponding panel in our component hierarchy, we will not have access to
the markup during initialization. Instead, the value returned is null.

There are no problems during the render phase.

Here's a quickstart which shows the problem with a dummy test panel.
quickstart.zip


--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Release WiQuery for Wicket 8

[Emond Papegaaij]

I'm planning to upgrade jQuery UI to the latest version next week. We are
currently migrating all our applications to wicket 8 and also depend on
wiquery quite a lot. It does however seem that jQuery UI is mostly dead.
The rest of the world probably switched to yet another fancy JavaScript ui
library. At least the will make it easy to stay up to date with the latest
version :)

I can't push a release to central, but perhaps Martin can do that when I'm
done? For now you can use a snapshot build. It works, but the UI API might
change a bit before the 8.0 release.

Best regards,
Emond Papegaaij


Op vr 1 jun. 2018 17:36 schreef Thomas Heigl :

> Hi Ernesto,
>
> I'm not sure how many people are still using it. But as I said, my project
> heavily depends on it.
>
> @papegaaij has resolved all the compile errors against 8.0.0-M9 (
> https://github.com/wicketstuff/wiquery) and a simple release of 8.0.0
> would
> be enough for me.
>
> Best,
>
> Thomas
>
> On Fri, Jun 1, 2018 at 5:05 PM, Ernesto Reinaldo Barreiro <
> reier...@gmail.com> wrote:
>
> > Hi,
> >
> > I do not know who is actually using this project. I use to contribute to
> it
> > a few years ago. I haven't used it for ages..
> >
> > On Fri, Jun 1, 2018 at 3:39 PM, Thomas Heigl 
> wrote:
> >
> > > Hi,
> > >
> > > Following the release of Wicket 8.0.0 and WicketStuff 8.0.0, could
> > somebody
> > > please cut a release of WiQuery compatible with the new version?
> > >
> > > Our application still heavily relies on WiQuery and we can't move to
> > Wicket
> > > 8 without it.
> > >
> > > Best,
> > >
> > > Thomas
> > >
> >
> >
> >
> > --
> > Regards - Ernesto Reinaldo Barreiro
> >
>