No subject

Wed Dec 19 16:44:34 CET 2007

method on the class (this is merely a convenience, so you don&#39;t have to implement<br>
the interface in your script, you can simply just use the appropriate method name).<br>
<br>Method m = findMethod(scriptClass, &quot;beforePacks&quot;);<br>if (m != null) {<br>&nbsp; m.invoke( scriptObject, new Object[] { idata, npacks, progressHandler } );<br>}<br><br><br><div class="gmail_quote">On Dec 22, 2007 11:02 AM, Julien Ponge &lt;
<a href="mailto:julien.ponge at">julien.ponge at</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Matthew,
<br><div class="Ih2E3d"><br>&gt; Is there any interest in this?<br><br></div>Yes, supporting scripting languages is a very appealing feature (be<br>it Groovy, Ruby or simply BeanShell). There are 2 things to consider<br>in my opinion.
<br><br>1. This must be optional when generating the installers as most Java<br>dynamic languages runtimes weight at least 1-2Mb each.<br><br>2. I would favor an approach where scripts are referenced rather than<br>included in XML CDATA constructs (think of IDE support for instance).
<br><br>Cheers<br>_______________________________________________<br>izpack-users mailing list<br><a href="mailto:izpack-users at">izpack-users at</a><br><a href="" target="_blank"></a><br></blockquote></div><br>


More information about the izpack-users mailing list