It's the fact that the code won't run unless the demo links against the appropriate jar file containing the scripting engine (and that fact that we then have to include that jar file) that's the problem. Our tutorial web pages could very well contain sections like "this is how you would do that same thing in Groovy, .... and Scala, ....".
But also, there's nothing wrong with writing demos that don't get checked in to SVN or shipped with our distributions. We as a community need to be better about writing articles and getting ourselves "out there". Demos serve as a great way to do just that, even if they don't live in our code base. -T On Fri, Sep 4, 2009 at 11:45 AM, Sandro Martini <[email protected]>wrote: > Ok, excuse me, to ensure that I have understand: > we can't host inside a tutorial web page a fragment of source code > (but without sources outside this HTML page, and without binary code) > like the following, and only referring from there to the Home Page of > that language ? > > Scripting Pivot with Scala: > > bla bla bla ... > > Sample Code: > > object HelloWorld { > def main(args: Array[String]) { > println("Hello, world!") > } > } > > > > Scripting Pivot with Jython (http:// ...): > > ... > > Sample Code: > > print "Hello." > > ... > > > > If we can't publish also samples like these, we can close the related > JIRA ticket, but at least could be interesting (for us, and for Pivot > users) to ensure that some languages are compatible, and so we should > try to make some (private) test, and write in Pivot documentation on > what languages we have tried and are or aren't compatible, right ? > > > Sandro >
