I check the Improvement [WICKET-6684] on version 8.6.0 but I didn't find any
trace of it. Maybe I messed something.
De : Andrea Del Bene [mailto:adelb...@apache.org]
Envoyé : samedi 7 septembre 2019 19:22
À : d...@wicket.apache.org; firstname.lastname@example.org;
The backport of the commit from 9.x (master) is
And I see the lines at:
I think the problem is in the packaging of this webjar.
The folder name in the .jar file
is: /META-INF/resources/webjars/jquery.scroll*T*o/ . Note the capiral T in
scrollTo. It does not match with the Maven artifact id - it uses lower case
Because of this
I will check: I had the impression Martin applied those commits to 8.x
On Mon, Sep 9, 2019 at 11:39 AM Olivier DUTRIEUX <
> I check the Improvement [WICKET-6684] on version 8.6.0 but I didn't find
> any trace of it. Maybe I messed
I believe it should be sufficient to start new VOTE
On Mon, 9 Sep 2019 at 17:17, Andrea Del Bene wrote:
> I'm afraid I did a mistake during the building of this version and I left
> out some of the last changes :-(. I guess we need to perform a 8.6.1 asap.
> Is there any particular action that
On Mon, Sep 9, 2019 at 2:06 PM Sibgha Nazir wrote:
> Any idea, how to fix it?
> On Mon, Sep 9, 2019 at 10:01 AM Martin Grigorov
> > Hi,
The recommended way to refresh kendo ui components - those bound to a
datasource - is to read from the datasource.
See Chart#refresh, it should solve the problem.
Thanks and best regards,
If you check the source
https://github.com/apache/wicket/releases/tag/rel%2Fwicket-8.6.0 , you don' t
see this line
Any idea, how to fix it?
On Mon, Sep 9, 2019 at 10:01 AM Martin Grigorov
> I think the problem is in the packaging of this webjar.
> The folder name in the .jar file
> is: /META-INF/resources/webjars/jquery.scroll*T*o/ . Note the capiral T in
> scrollTo. It does not match with
Doesn't work with this solution as well.
On Mon, Sep 9, 2019 at 6:59 AM Sven Meier wrote:
> I don't know why, but WebJars doesn't seem to be able to determine the
> 'current' version of your dependency.
> Try with "jquery.scrollto/2.1.1/jquery.scrollto.js" instead.
> Hope this helps
I'm afraid I did a mistake during the building of this version and I left
out some of the last changes :-(. I guess we need to perform a 8.6.1 asap.
Is there any particular action that must be taken in situations like this?
Should we notify the ASF?
On Mon, Sep 9, 2019 at 11:48 AM Olivier
No need to notify ASF.
Just fix the problem and start a vote for 8.6.1.
On Mon, Sep 9, 2019 at 1:19 PM Maxim Solodovnik
> I believe it should be sufficient to start new VOTE
> On Mon, 9 Sep 2019 at 17:17, Andrea Del Bene wrote:
> > I'm afraid I did a mistake during the building of
We’ve implemented a „one-page“ application and basically just replacing panels
via Ajax updates.
When those panels contain Kendo Grid or Chart components I can see datasource
items adding up in the DOM for every newly rendered Grid or Chart which
eventually add up so much that the page
OK, but I don't really see how reusing instances of a Kendo Grid really
works in a component based design where the parents of where the Grids are
placed are replaced on the page.
In particular we have a three panes border layout, kind of a 'master-detail'
plus a tree on the left
Sorry, my previous answer was incomplete.
Kendo components do usually have two methods for ajax, #reload and #refresh.
Reload aims to reload the component (ie reattach to the dom) while refresh
aim to refresh the data only.
IIRC, grid and chart are different in the sense that grid
Mail list logo