> I think the above are the issues we should really be focussing on here.
> Particularly the fact that the API doesn't work on a Mac anymore. That's a
> big let down for the Mac community, and would turn a lot of developers
away
> from using the API. Documentation in my mind is also a biggie.
>
> In saying that, I don't have a Mac to try and fix things on, and I suspect
> neither do any of the core developers.
I have a Mac, and for most of the stuff i'm doing, the DynAPI performs
pretty well, it's not that bad after all.
At moment i have just one big bug in IE i wasn't able to solve. I have
posted it more than once but never got any feedback (anybody interested??)
Usually things happend like this:
1. I discover something that doesn't work.
2. After checking if somebody else knows a solution i try to fix it on my
own.
3. If I come to the conclusion that I will not find a solution in a
reasonable amount of time I make a nice post and hope somebody else can
contribute at least a hint.
4. Unless a solution is found by somebody, I try to avoid the problem.
Things usually get stuck in step 3. More than once there wasn't even an
acknowledgement of the problem, and that's the moment I'm getting kind of
disappointed.
The reason for this situation is obvious: There aren't enough Mac-Developers
working with DynAPI, so there's no communication about bugs, possible
solutions, testers... I don't know how this could be improved. Just wanted
to make you know I'm here.
--
Michael Buerge
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
