Hi Boris, Far-sighted comment. Direct references to Java library really cause some portable problems. I guess, it is trade-off. One thing is, for the current osgi, the libraries shipped with JVM are unbound to the bundle. In current usage of Eclipse plugin, there are many many direct references coupling in tbe different plugins(already mentioned in the e4 whitepaper). If using JavaScript bundle under this pattern, I guess we have no chance to escape the coupling life. Maybe e4 service-based programming model is good to solve this problem?
I will really appreciate it if I would do some useful things in the e4. I try to find some bugs in e4.language, but there seem only several new bugs there.(or I am wrong in using the bugzilla?) I hope my joining will not disturb their development plan. At least, I can just do some documenting works. Yeah:) Best regards, Jin Mingjian 2009/9/1 Boris Bokowski <[email protected]> > Hi Jin Mingjian, > > Jin Mingjian wrote on 08/31/2009 02:47:21 AM: > > > I post a blog writing today to address your question. Check it at[1]. > > > Great - thanks a lot! > > I think it would be great to work on more advanced examples, like how one > JavaScript bundle can call another JavaScript bundle's API, and how a > JavaScript bundle can interface with a Java bundle through its API. I am > not sure if calling the Java library ("java.lang.System.out.println") is a > good idea, since it will lead to a JavaScript bundle that can only be used > from Rhino inside of a Java VM. Ideally, JavaScript bundles should run in > other contexts as well (in the browser, or a JavaScript VM like V8). > > > is there some space to join the e4 javascript effort? I can > > arrange some free time recently and I am interested in your js > > tooling support. > > I'll leave it to Simon to respond. You are of course very much invited to > join the e4 project. > > Boris > > > [1] http://jmj-eclipse.blogspot.com/2009/08/e4-09-review-02-how-to- > > write-helloworld.html > > [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=284930 > > > _______________________________________________ > e4-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/e4-dev > >
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
