I was wondering, where is the original Eclipse Monkey proposal? I would like to be able to reference it in the proposal I am currently writing.
Thanks, James On Fri, May 2, 2008 at 5:55 PM, James Ervin <[EMAIL PROTECTED]> wrote: > > > ---------- Forwarded message ---------- > From: James Ervin <[EMAIL PROTECTED]> > Date: Fri, May 2, 2008 at 7:20 PM > Subject: Re: [dash-dev] Revised home page and now a project plan too > To: Tools for Committer Community <dash-dev@eclipse.org> > > > Yes I concur with Karl. To allay your concerns Steve, I would like to > make the following points. > > First off, groovy-monkey is a working project that I use every day. There > are others that use it too. > > Secondly, I think the biggest thing for existing Eclipse Monkey users will > be getting the Rhino Ecmascript engine to work and to port any DOM over to > the new framework. DOM porting should be relatively simple, it is the > getting Rhino to behave like the other engines that I would love help with. > > Thirdly, don't let the name groovy-monkey fool you, it started off as a > port of Eclipse monkey to groovy, but it is now largely language agnostic. > It leverages the Bean Scripting Framework (not javax.script at this time) > and any therefore implementation of a BSF Engine could be plugged in. The > only thing that is that the engine not only needs to evaluate scripts in the > given language, accept variable bindings, but it must allow for interaction > with POJOs through setting up the classloader for the engine. I couldn't > get Rhino (I am not an expert) nor Jython at the time to function. I > therefore settled on allowing Beanshell, Groovy and Ruby, which is what > groovy-monkey currently supports. In fact there is an extension point that > defines how to plugin in a new language (in the beginning I even tried > getting NetRexx and Tcl to work). > > Thanks, > James > > > On Fri, May 2, 2008 at 6:37 PM, Karl Matthias <[EMAIL PROTECTED]> > wrote: > > > Steve, > > > > Well the tool has already "gone away" in the sense that no one is > > maintaining it actively. It works now, but it won't work or at least will > > not have been tested when Ganymede is released if nobody works on it. There > > is no evidence that that is going to happen. Thus, Bjorn is simply making a > > change to the project status to reflect reality. However, James is stepping > > up to the plate to offer a new direction for Monkey, possibly as a new > > project and I'm sure he'd be happy to receive or help direct any efforts you > > might want to contribute to the project. > > > > Cheers, > > Karl > > > > > > > > Steve Corwin wrote: > > > > > I'm a Java developer who is happy with the Eclipse Monkey project > > > as-is, and rely on it for my daily work in Eclipse. I don't think I could > > > use Eclipse without it. My biggest concern is that all of these proposed > > > changes will cause a currently working tool to go away. > > > > > > -Steve > > > > > > Bjorn Freeman-Benson wrote: > > > > > > > Arnoud, > > > > > > > > > im a flex developer and find the javascript part of monkey quite > > > > > useful. > > > > > Will that part still be supported or is the project moving in > > > > > another direction? > > > > > > > > > James has offered to restart the Monkey project (see other emails on > > > > this dev list). > > > > > > > > > For me its strange that a project like this isn't more popular. > > > > > Being able to script eclipse is awesome! > > > > > > > > > I'm sure that James would welcome your participation and > > > > contributions... without committers, the project isn't going to go > > > > anywhere > > > > (as demonstrated by its lack of progress to date). > > > > > > > > - Bjorn > > > > > > > > -- > > > > [end of message] > > > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > > > _______________________________________________ > > > > dash-dev mailing list > > > > dash-dev@eclipse.org > > > > https://dev.eclipse.org/mailman/listinfo/dash-dev > > > > > > > _______________________________________________ > > > dash-dev mailing list > > > dash-dev@eclipse.org > > > https://dev.eclipse.org/mailman/listinfo/dash-dev > > > > > > > _______________________________________________ > > dash-dev mailing list > > dash-dev@eclipse.org > > https://dev.eclipse.org/mailman/listinfo/dash-dev > > > > > > -- > James E. Ervin, IV > > A human being should be able to change a diaper, plan an invasion, butcher > a hog, conn a ship, design a building, write a sonnet, balance accounts, > build a wall, set a bone, comfort the dying, take orders, give orders, > cooperate, act alone, solve equations, analyze a new problem, pitch manure, > program a computer, cook a tasty meal, fight efficiently, die gallantly. > Specialization is for insects. > -Robert A. Heinlein > > Blog: http://iacobus.blogspot.com > > > > -- > James E. Ervin, IV > > A human being should be able to change a diaper, plan an invasion, butcher > a hog, conn a ship, design a building, write a sonnet, balance accounts, > build a wall, set a bone, comfort the dying, take orders, give orders, > cooperate, act alone, solve equations, analyze a new problem, pitch manure, > program a computer, cook a tasty meal, fight efficiently, die gallantly. > Specialization is for insects. > -Robert A. Heinlein > > Blog: http://iacobus.blogspot.com > -- James E. Ervin, IV A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -Robert A. Heinlein Blog: http://iacobus.blogspot.com
_______________________________________________ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
