To add to your point Jordi (and I am nervous)...
Our customers primary users of the application I am currently engaged in
work from PC's, but about 40% of the people/products they coordinate are
creative people. This is a critical part of their business, and the creative
community has a dramatically higher percentage of Mac users.
I think the DynAPI project has huge potential if we keep our eyes on our
users needs, and not on what methodology, principal, or technology we use
(although these are important to us as a group). If we fall into this trap
and go for ease of implementation and sex appeal, it becomes just another
cool idea/toy that never made it in the real world. From my perspective, I
can safely say that our organization (250 developer across the US) would not
be able to use the DynAPI if we don't support the 4.x+ browsers on
PC/Mac(not that this really matters to anyone but me).
Let's concentrate on getting this release working quickly and predictable
cross-platform (Mac/PC), cross-browser (4.x+) before we begin worry about OO
this, or widget that!
Sorry about the soap-box,
Mike Ellis
-----Original Message-----
From: Jordi 'IlMaestro' Ministral [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 06, 2001 08:38
To: [EMAIL PROTECTED]
Subject: Re: [Dynapi-Dev] Netscape 6 discussion
Another ilustrative example: they took me to a project brainstorming. Big
website,
world-wide coverage including the very best of the design community. "Hey,
aren't
you the DHTML guru ? They told us you could add some cool and impressive
effects !!
"
Well, yes, sure. Then they told me the target: 90% Mac users. Should I
suggest they
all upgrade to windows platforms or pray that DynAPI2 behaves in Mac ? At
least I
know the API enought to attemp some bugfixing myself. If I was not that
experimented
and had to watch sourceforge for that fix to come, I would get really really
nervous.
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
