Wicket 7 Component class structures

[hielkehoeve]

We need a new class structure which is maintainable over all the jQuery UI versions. Otherwise we will keep having problems in where we have no idea whether things are or will keep working.

Perhaps we should make a Java generator which scans the JavaScript files for options, methods and events and if needed adds them to the Java files.

Ideas?

[reiern70]

You mean like "a jquery pluggin scanner" that give you a list of features to be supported by a "Java version"of plugin. and possibly a generator.

I think you can access properties ant JavaScript level via $(x).data("plugin name")...

[hielkehoeve]

I meant a unit test or maven plugin or whatever which scans the jQuery UI js files and generates/edits .java files accordingly. This way know if functions have been added to//removed from the jQuery UI js files.

We will only have to implement the body of the generated functions or keep track of removed functions.

[reiern70]

Yes that's what I meant by $(x).data("plugin name"): this gives you a list of plugins functions, properties,

[reiern70]

Well not exactly a list but an object with those properties.

[hielkehoeve]

Lets try some options after I've created a wicket 6 branch.

Hielke
On Nov 26, 2013 5:33 PM, "Ernesto Reinaldo Barreiro" <
notifications@github.com> wrote:

Well not exactly a list but an object with those properties.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/47#issuecomment-29307624
.

[reiern70]

It would help a lot if they make the public API of a plugin in some easily parseable/uanbigous format: we might need types for the parameters/methods and so on if we want to build a generator,