I’m not saying you guys should do anything, I’m just telling you what I did J
However, if I say my software is supported in an entire major version without users looking deeper into the docs for minor version coverage, then it had better or I’m in trouble. That’s why I use NN 4.03 and why I ported DynAPI 3 to it.
Don’t get me wrong, I too dream of a day when all we need is the DOM, but until then, cross-browser means v4+.
I was going to say that I could submit my code or a change log, but then in future versions you would be supporting this hated version, which it seems is not desired. I just think if a function returns an explicit value sometimes, it should return an explicit value all of the time. Not every single function.
As I said, I just made those simple changes and everything up to MotionX worked fine.
Is every property and method in the API demonstrated in the examples?
If so, it would give me a good idea of what needs to be done.
Kudos to great work! I’ll just keep mutating the API to my down-level specs.
|
- [Dynapi-Help] Here's a question, help! C Kissinger
- [Dynapi-Help] Here's a question, help! todd and mara
- Re: [Dynapi-Help] Here's a question, help! Bruce Tennant
- Re: [Dynapi-Help] Here's a question, help! Jesse Vitrone
- Re: [Dynapi-Help] Here's a question, help! Raymond Irving