Thanks for the info.
Is there a way to use the website code i wrote for 2.54 with DynAPI3 ?

Or is DynAPI3 a completely different thing. What happened to all the DynAPI1
and 2 websites? They all died when IE6 appeared:) ? I cant believe it.

To be honest, I primarilly used DynAPI for it was cross-browser and I didn't
have to worry about optimizing code for different browsers. So this site
didn't use any advanced widgets, mostly dynlayers and mouse events action.

You can see it at>
http://www.comcare.cz/dynapi/archive/dod/latest.html


If it is too difficult i will have to drop it, I just wanted to make 100%
sure there is no way I can make this work within less then 10 hours.

Thanks,
Jirka



-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Leif W
Sent: Thursday, July 28, 2005 4:52 PM
To: dynapi-dev@lists.sourceforge.net
Subject: Re: [Dynapi-Dev] IE6 support for DynAPI2

> Jiří Blažek <[EMAIL PROTECTED]>
> Thu, 28 Jul 2005 10:31:10 AM EDT
> 
> Hi,
> 
> I developed a website back in 2001 based on DynAPI2.
> Now the ppl ask me if it was possible to update it so it works on IE6.
> 
> I tried to find some info and it seems that DynAPI3 supports IE6. 
> Is there a way to upgrade? That is, without rewriting the whole thing :).
> 
> I was using version 2.54
>  
> 
> Thanks,
> Jirka

Hi Jirka,

At present, there has not been much discussion to update DynAPI2 to support
newer browsers.  I'm personally not opposed to it or anything.  It's just
that
trying to get current with DynAPI3 in preparation for a stable release is a
higher priority.  Also my time and resources are limited and I'ving hardware
problems.

DynAPI3 (in CVS) will support IE6 better, but there may be undiscovered
bugs,
as it's still in beta.  The DynAPI3 beta1 release has had a few problems and
is patched in CVS.  A beta2 or rc1 release is planned for early August.  I'm
still learning CVS and the SourceForge system, and while I have computer
problems I can't do much reading or testing of anything.

The DynAPI3 widget sets are different than DynAPI2.  Most DynAPI2 widgets
have
not been ported to DynAPI3.  Those require some non-trivial modifications. 
I'm doing my best to fix my hardware, configure OSes, read about CVS & SF,
and
understand the DynAPI3 code.  If you do find specific problems, or make any
modifications to DynAPI, please submit bug reports, patches, feature
requests,
or new code using trackers on the SF developer's site.

Leif




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Dynapi-Dev mailing list
Dynapi-Dev@lists.sourceforge.net
http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Dynapi-Dev mailing list
Dynapi-Dev@lists.sourceforge.net
http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/

Reply via email to