Again me. Have you had enough yet ;-)
Just wanted to explain the whole TCanvas and OOJS stuff. I'm not working
against anyone here and specifically not against pascal. This is an
opensource group and like someone recetly stated it's not you or me it's us.
I am only doing all of this code by myself because you didn't want to do it
without it being tested.
My only concern is that the API is not stable enough no fast enought and not
built well to support future browsers.
I know you all want to get done with NN6 before but I think that this is the
best time to do it. With all these new browsers around. I don't mind if we
call it canvas or dynlayer or if it's my code or pascals. I want the best
code there is that's all!
I know that webos is overkill. What they did is designed an OS. What we are
doing are page add-ons. I was thinking of somthing in the middle. How about
thinking about DynApplications. You can have many running in one browser (or
not). I think that that would be the best model. I also still think that we
should completely seperate widgets from DynLayer. I think the work on DynAPI
should be split in to two:
* DynLayer
Getting the DynLayer 100% compatible (or is much as we can) and then
tweeking it to take up less memory clear the memory it uses and run faster.
* Enviroment for DynLayer
This should include a type of application object which manages memory,
focus, key events. And widget libraries. We should have the group of basic
widgets:
Label, Panel(Form, or somthing like that), Button and the rest
and then we should have packs of widgets that extened functionalitiy?
Anyone agree? Anyone disagree(pascal)?
8an
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
