Re: [dash-dev] Tentative proposal for architecture...

[Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx>]

I agree with you Paul, but I think we should look at the problem slightly differently: the choice to include _javascript_ as the default language is a choice we make as to which set of plug-ins we put into our standard Europa feature. I think the standard Europa feature should be:

• core (includes "run", "edit", and "share" functions)
  
• _javascript_/Rhino extension to core
• standard DOM extensions to core (Resources, View, Editors, Sharing, etc)
  

Then we include the _javascript_/Rhino feature along with all the other language features (and the more exotic DOM features) as just features on our update site. Easy to install; solves all the problems at once.

Perhaps this is what you were saying, I just used different words?

Paul Colton wrote:

It seems what is needed to support 'any' scripting language in EMonkey it at least the following:

- a 'core' DOM extension point that is Java-only and scripting language agnostic

- we decide on a reasonable set of core DOM extensions (i.e. Resources, Views, Editors, Sharing, etc.)

- scripting language specific extensions for making the core DOM more script language 'native' (i.e. more "pythony")

I'd also suggest:

- _javascript_ is the default, full implementation of the core DOM -- other languages can write extensions to the core and be available as downloadable extensions