but doesn't that mean that we then go back to where we were before the dynapi.
we are back to being at the mercy of the browser.
i personally use the dynapi to make the browser behave in a standard manner.
there are too many differences between the method of event control between the
browsers to
Additionally, I would imagine that eventually that "new" API will/should be
allot more powerful with extended animation capabilities, integration of new
elements [cursor control, opacity, SVG, etc ].
This API is about at it's maximum potential and over the next 6 months will
hopefully clean up it
That would be a nightmare to keep consistent and way too much
overkill. DOM API's do not need to be as complex the DynAPI. For
instance, there is not need to have functions to set the css
properties, when they can be accessed directly (of course it could be
an extension). Also, things like eve
A note on my msg:
I did a check and the only places where there are is. clauses (meaning
difference between dom and non dom) is in besic API files (events and
dynlayer). So really all it is, is a two dynlayer files and two events.
8an
___
Dynapi-Dev m
I hear your views and they sound like pascals (don't leave us here alone!!)
but your missing the point of the API.
Here are the facts
* Writing for DOM is easier
* Writing for DOM saves lines of code
* This DynAPI ver is huge to only a dom one
But you are forgetting a few things:
* At the current
like eventListeners are built-in to DOM
browsers (although slightly different in IE), so there is no need to
create a complex event system.
--
Robert Rainwater
On 5/18/2001, 7:00:54 PM EST, Digital wrote about "[Dynapi-Dev] Development Direction":
> You know what would be nice.
>
remaining 25ish%.
That would be nice...
DS
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Digital
Strider
Sent: Friday, May 18, 2001 3:46 PM
To: [EMAIL PROTECTED]
Subject: RE: Re[2]: [Dynapi-Dev] Development Direction
Nice to hear the voice of Robert again.
With dragging and sliding, and pathanimation etc?
- Original Message -
From: "Robert Rainwater" <[EMAIL PROTECTED]>
To: "Sergi Mansilla" <[EMAIL PROTECTED]>
Sent: 19 May, 2001 00:39
Subject: Re[2]: [Dynapi-Dev] Development Direction
>
> When wri
Nice to hear the voice of Robert again
Agree, but i do like Mr. Bennetts idea of creating a front-end to the
libraries (plural) that sniffs browser capabilities then download the
appropriate code base.
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.gr
API I wrote that is less than 100 lines and just as powerful
as the DynAPI.
--
Robert Rainwater
On 5/18/2001, 5:29:53 AM EST, Sergi wrote about "[Dynapi-Dev] Development Direction":
> Totally agree. Not-DOM Browsers support in a separate js
> Something I'm trying to find out is why NS4 sometimes does,
> and sometimes
> doesn't render css.
i've found a few interesting bugs in ns4 with regards to losing style
sheets. for example if you have any inline divs in the page (with sytle
attribute on the div tag) then ns4 loses the css.
i'
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Richard
Bennett
Sent: Friday, May 18, 2001 2:48 AM
To: [EMAIL PROTECTED]
Subject: Re: [Dynapi-Dev] Development Direction
I think the main priority should be to get what we have finished.
Get something
es etc, as we can always point to
that release if people need v4 support.
If we have some Mac people to do some work there, we should be able to have
a final release in maybe two or three months.
Richard.
- Original Message -
From: "Scott Bristowe" <[EMAIL PROTECTED]>
To: &l
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Scott
Bristowe
Sent: Friday, May 18, 2001 2:04 AM
To: '[EMAIL PROTECTED]'
Subject: SV: [Dynapi-Dev] Development Direction
I am quite sure that we are all *well* aware of your opinion 8an :P
What I asked though, was if there h
Totally agree. Not-DOM Browsers support in a separate js
- Original Message -
From: Eytan Heidingsfeld <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 18, 2001 12:03 PM
Subject: RE: [Dynapi-Dev] Development Direction
> I think we should cut 4.0 dynlayer
]
Ämne: RE: [Dynapi-Dev] Development Direction
I think we should cut 4.0 dynlayer support into a separate file and load
only the right one and in about six months stop supporting it at all.
Bring On The ROCKS!!!
8an
___
Dynapi-Dev mailing list
[EMAIL
I think we should cut 4.0 dynlayer support into a separate file and load
only the right one and in about six months stop supporting it at all.
Bring On The ROCKS!!!
8an
___
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/li
I am curious, has there been any decision on where we are going, ie. Are
there plans to stop supporting "older" browsers in the near future?
Cheers
Scotto
___
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dyn
18 matches
Mail list logo
