DLRScript Update

In the next week or so I will be releasing a new version of my DLRScript. It will have external file sourcing/loading via the src attribute (I have that working right now). I would release it today except for 1 issue.

what is in the file is this

//JS:
jsapi.alert("Hi JScript here");

#Python
jsapi.alert("Hi Python here")

#Ruby
$jsapi.alert("Hi, I'm Ruby and YOU are NOT!")

Here's the issue. I think I discovered a bug (in my code). When you try to launch multiple alert boxes you get 1 of them and errors for the rest. Which makes sense to me (as you the user need to click the button on one of the Alerts. I will correct this.

I also discovered another subtle little issue that I want to account for.  The problem is that since we are moving code Asynchronously there are multiple threads involved.  My current development executes code as it gets code back, but it should execute this stuff in the order it appears on the page (I'll be correcting that one too)

Probably the next week or so, and then I'll be moving forward on my other ideas (most notably the Object Model).

Ruby DOM??

While I'm on the subject of Object Models, I had some discussions with some friends to see if I should duplicate client-JavaScript's DOM model or if I should create something else.

The wisdom from both seemed to be that duplicating client-JS' DOM for JScript and Python would be good, but you Ruby guys would something that is Rubyish (no, not rubish... I said Rubyish).  I was wondering if I might get a Ruby programmer to help me understand what that means (cause neither of my friends can answer that question).

So here is the question.  If you had the ability to write Ruby code as a client language (and you can with DLRScript) what would the framework look like? 

Print | posted on Tuesday, March 18, 2008 9:36 AM

Feedback

No comments posted yet.
Title  
Name
Email (never displayed)
Url
Comments   
Please add 8 and 6 and type the answer here: