Comments on: Class-based OOP in Javascript done right

By: OpenLaszlo Project Blog » Legals PR3: Replacing the tablecloth without touching the place settings

Fri, 01 Sep 2006 23:47:53 +0000

[...] Converted all of the OpenLaszlo Runtime to use the proposed ECMA-4 class declaration syntax, and in the process modified them all to directly work with the new OpenLaszlo class model; [...]

By: ptw

ptw — Sun, 26 Mar 2006 15:49:02 +0000

It works in all the browsers I can test (see Does your browser conform? to try your favorite browser). But it does not work in Flash, which is one of our target runtimes.

By: OpenLaszlo Project Blog » Does your Browser conform?

OpenLaszlo Project Blog » Does your Browser conform? — Sun, 26 Mar 2006 15:39:59 +0000

[...] Brendan Eich asks, in a comment on Class-based OOP in Javascript done right: ECMA-262 Edition 3 (http://www.mozilla.org/js/language/E262-3.pdf among other places) specifies (13.2.2 [[Construct]] in function objects, step 7) that the result of new C for a function C is the value returned from C if that value is an object. What browsers fail to get this right? [...]

By: Brendan Eich

Brendan Eich — Sun, 26 Mar 2006 05:43:11 +0000

ECMA-262 Edition 3 (http://www.mozilla.org/js/language/E262-3.pdf among other places) specifies (13.2.2 [[Construct]] in function objects, step 7) that the result of new C for a function C is the value returned from C if that value is an object.

What browsers fail to get this right?

/be

By: jgrandy

jgrandy — Fri, 10 Mar 2006 02:40:37 +0000

Kaj - I agree. The best thing is for the language to support a construct like this natively. We are closely following any ECMA activity around Javascript and will support any class syntax that arrives through the standards process. However we have a somewhat unique need — we compile to multiple runtimes and have to support the same LZX language features across all those runtimes. To that end this library is intended to bring a class model back to ECMA-262 dialects. Note that we aren’t proposing Javascript syntax here — our LZX compiler will still generate ECMA-262 — we’re describing a way of achieving reasonable semantics.

By: Kaj Kandler

Kaj Kandler — Thu, 09 Mar 2006 17:29:32 +0000

Looks like a nice way to do it.

Although having struggled through other ways of doing class based inheritance, I have learned that if you can do it is not the same as if the language is based on it. It simply means that all components of your system have to support the same way to do it. Which burns you more often than not.

What I’m trying to say is we should strive for JavaScript 2.0 to include the propper way to do Class based inheritance.

K
P.S.: I’m missing a “A is intance of class B construct”.

By: Simon

Simon — Thu, 09 Mar 2006 07:07:10 +0000

I think your questions are not going to be answered my friend. No coder will answer you because your questions are not appropriate for a blog like this. They just insult web coders at large. I think the better way would be to start reading the source code and then figure out for yourself what it all means. Unless you have coded a web application using JavaScript, HTML, CSS, DOM, a webserver, a server-side scripting language like PHP and a database, I don’t think you will ever get the answer you want. Sorry.

By: RV

RV — Mon, 27 Feb 2006 14:03:17 +0000

Questions about scalability :
- Is anyone using laszlo to run ondemand applications (ie Software as service applications ) ?
- what are the scalability benchmarks,if any, on running this on a j2ee platform ( a very broad question ,but any available information will be useful).
- is laszlo meant only for intranet applications ,due to performance reasons ?

thanks in advance