JavascriptSupport : any reason for limiting addInitializerCall?

[Robin Komiwes]

Hi,

Still on my way to migrate to Tapestry 5.2.0-SNAPSHOT.

Before, we were doing:
support.addInit("appendToZone", link.toAbsoluteURI(),
form.getClientId(), to, position);

Now, there is only:

  void addInitializerCall(String functionName, JSONObject parameter);
  void addInitializerCall(InitializationPriority priority, String
functionName, JSONObject parameter);
  void addInitializerCall(String functionName, String parameter);
  void addInitializerCall(InitializationPriority priority, String
functionName, String parameter);


I was looking for something like:

  void addInitializerCall(String functionName, JSONArray parameter);
  void addInitializerCall(InitializationPriority priority, String
functionName, JSONArray parameter);

or

  void addInitializerCall(String functionName, String... parameter);
  void addInitializerCall(InitializationPriority priority, String
functionName, String... parameter);

These would have let me free from refactoring my JS file.

Is there any reason for this limitation? Is it the new way of doing things?

regards,

Robin

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