|
From: Pennell, D. <DPe...@qu...> - 2003-10-15 12:34:13
|
Repost of Michael Lucas-Smith reply to David Pennell: DP>> I think that HostObjectWrapper can be implemented as described (I DP>> believe the Rhino guys did the same thing for Java). This is going DP>> to be appropriate for an audience that you want to give that kind DP>> of power. I also want to support a wrapper style that lets you DP>> have fine-grained control over the permeability between ST and JS. DP>> You might want that control because of security concerns or because DP>> of support concerns - you just might not want users to have access DP>> to ALL DP> objects in your image. I agree entirely. DP>> I'm going to need to put together an example of integrating Smee DP>> with a host application. I'm thinking that with:Style: would make DP>> a nice example. What do you think? I think that's a fantastic idea. Once I've stabalised the dynamic updates and a parcel building problem we have I'll start sending you advanced copies of Tech Preview 2 for you to play with. Tech Preview 2 already includes the ability to use JavaScript, but because of the lack of DOM and host objects in the version I used, it is not terribly useful :) It should be immediately obvious the kinds of support that should be added, not just to support web-js code, but also to support the sorts of operations smalltalkers might want to use. It would be possible to build a development environment for javascript and XML using with:Style. We could clash heads on this after all the core work is done if you like? DP>> Other semi-random thoughts: DP>> - A JS XPath object would make a nice companion to the native DP>> RegExp DP> object. Yep. I'd like to expose XPath's in to the DOM tree of VW's XML objects more, they're underutilitised so far. DP>> - JS in XSLT might be interesting - in both modes There are so many ways to do this? What did you have in mind? (ie: what did you mean by 'both modes') |