This is about the whole redesign issue.
Why
---
One of the reasons for the lack of stability in DynAPI is the way it is put
together. I respect that professor very much and I understand he likes the
model but this exact model is why it crashes and why it develops like it
does.
What
----
What do I mean. I want to rewrite the actual core meaning changing
everything. Making a DynLayer class that is totally independent. Then
creating a whole OO environment (it doesn't matter at this stage if we use
prototypes or classes for OO but the current API misuses OO completely).
Where
-----
I know that you guys want this to be the perfect "Dreamweaver" use solution.
For that this thing has to be modeled in a logical simple way. It also has
to be a whole lot more stable then it is today
When
----
As they say "Never been a better time then right now!" As I previously
stated the development of support for other browsers can be integrated in
the rewrite.
I can see that most ppl disagree with me and like things the way they are, I
hope I can change your mind but I guess its up to the majority.
8an
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
