Re: [Dynapi-Dev] New OOJS

[Dann <da...@to...>]

Great.

I myself would be greatful if we all would just get this 'version' to work 100%.
I can sympathize with everybody here doing their fancy walks on IDE's, OOP and
what not. The problem is, everybody seems to forget that this effort is
remarkable in that it attempts to close a gap under very difficult
circumstances. Anyone with javascript programming in her/his fingers knows that
it is a far cry from a solid base to build on - and I'm just talking about one
single instance browser/platform. Bring on the incompatibilities,
browser/platform dependencies, implementation differences and the complete bug
circus that comes with it, and you end up with something of a nightmare.

Snap out of it, people : there will never be anything even close to the extent
of what you are dreaming about here, given the circumstances.

What *is* feasible is being done here already as much as possible. Build a
stable core (keep it simple - keep it simple - keep it simple) API to raise the
bar on what you can do in the dreary HTML/CSS universe. And let's face it, while
we're doing it, we're already overkilling it so much that there's nothing left
of what the basic idea of hypertext was al about.

Must sleep now.

CU,
 Dann

Eytan Heidingsfeld wrote:

> Like I have mentioned many times before I don't like how DynAPI is used. It
> is an API not a language, but I'm getting ahead of myself. Let's start at
> the beginning. In the beginning there is JS. Problem number one is that JS
> is class oriented  and not object oriented therefore the "weird" inheriting.
> That problem was later solved by my Inherit method. Problem Number two is
> that although it is a program language that is class oriented it doesn't
> give you the necesary building blocks to use it correctly. Because of this
> reason I decided to write the OOJS (Object Oriented Java Script). Before I
> explain my ideas for how when and where (which you are free and are
> encouraged to criticize) I will warn you that unlike JS which is a scrambled
> mix of Java, C and some other languages this OOJS is Delphi like in syntax.
> The reason for this is that when I started I was doing this for a certain
> project which I would be working on with Delphi programmers. Now for the
> OOJS.
>
> First of all you have the most base object TObject. All objects inherit from
> it! It includes a small amount of properties and methods including a create
> and a destroy (and there events). Then you have TComponent. TComponent is
> the base class used for visual objects. How does it work. It uses the DynAPI
> as I think it is supposed to be used, as an API. That means that I have a
> DynLayer as a private variable. Then I have methods as such DrawComponent,
> Draw and events such as onPaint or onRefresh. Then if you want to create
> your visual component all you have to do is inherit from TComponent and call
> the correct methods. As you may have noticed the event structure is
> different too. It is like in Delphi (big surprise) you define a type which
> is basically a definition of a procedure then you implement it and set a
> property of your object with this procedure and when the object wants to
> invoke it calls its property for the event.
>
> This is just the beginning and I know it is very jumbled. By tomorrow I will
> send out the basic code I have till now and anyone who is interested in
> helping please email me.
>
> Work needed to be done:
> A. Finish fixing up base types
> B. Rewrite DynDocument to a new type called TApplication (no biggie since
> DynDocument is 80 lines)
> C. Start converting objects from the library to the new OOJS model (easy
> enough once model is done)
>
> Any Takers,
>
> Thanx,
> 8an
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev