> - Scripting (possibly; currently has a Mozilla dependency since OSX JDK doesn't include a JavaScript engine and we need to use Rhino)
With regards to this are you talking about Pivot apps interacting with their containing web-page, or actually providing scripting within Pivot? In the latter case I don't see the point in JavaScript support within Pivot. This is Java-land after all and while this is a RIA which can run in a browser, one of the appealing things to a lot of developers will be that they can create a functional, server-backed RIA in Java end to end... so why not just use Groovy and dump JavaScript support within Pivot? Just a thought. Cheers, Chris 2009/4/17 Greg Brown <[email protected]> > I found them extremely valuable in getting up to speed, and it's a >>> nuisance for new people to checkout code from multiple sources. >>> >> >> IMHO, the incompatible code should be moved, and the demos that can >> stay stay. Then it becomes a matter of time when all demos are finally >> Apache Licensed only. Inconvenient, yes, but we look at things in very >> long perspectives here (say Harmony or Geronimo, if you want to look >> at painstakingly long clearance of encumbered code). >> > > I think it is likely that we are always going to have some demos that rely > on incompatible code. However, any demo that doesn't have such a dependency > will probably be rolled into the tutorials, which are included with the > distribution and stored in the ASF SVN; e.g.: > > - Kitchen Sink (already in tutorials) > - Stock Tracker (already in tutorials) > - File browser > - File drag/drop > - Table row editor > - Large data sets > - DOM interaction > - Decorators > - Fixed column tables > - Scripting (possibly; currently has a Mozilla dependency since OSX JDK > doesn't include a JavaScript engine and we need to use Rhino) > > Basically, these demos showcase topics that we haven't gotten to in the > tutorial yet. When we do, I imagine that we'll migrate them. > > G > >
