Closed shuraa closed 13 years ago
If you provide a quickstart then the chance someone to try to debug and improve it will be higher. Otherwise since wicketstuff is community based most probably no one will look into this issue until (s)he face the same problem in his/her application. It shouldn't be a problem to debug it yourself - just find where "InMethod.XTableManager.instance.register" is being called and change the method that renders it to a one that is filtered.
Martin, I'm not very familiar with github. Please, point me where I can read about attaching quickstart and proposed patch to the issue ?
I do not know about a way to attach files to an issue but you could create a git repository and put the quickstart there. After that you can link the repo to this issue.
Ok, I've created a quickstart and publish it on github https://github.com/shuraa/wicketstuff-inmethod-datagrid-issue32
Later I'll add a patch for the issue.
Please, review and apply patch https://github.com/shuraa/wicketstuff-inmethod-datagrid-issue32/blob/master/wicketstuff-core-issue32.patch
The patch looks OK. I'll test it soon and apply it. Unless someone else do it before me.
I have ported shuraa's quickstart to wicket+wicketsuff 1.5 and the issue (js error) is present there too.
Patch was merged to core-1.4.x and master. Thanks to everybody!
I have using JavascriptFilteredIntoFooterHeaderResponse strategy for rendering javascript on my sites. Now I have looking for ways to integrate inmethod DataGrid component and have stuck with javascript initialization issue - in javascript console I've got "Uncaught ReferenceError: InMethod is not defined" on line "InMethod.XTableManager.instance.register("gride", columns, submitStateCallback);". Is there workaround for the issue ?
Env: Wicket 1.4.17, inmethod-grid-1.4.17.1, JDK 1.6u25, Jetty 6
Thank you, Alexander.