I think the main priority should be to get what we have finished.
Get something working on the Mac, if it's not, or at least document what can
and can't be done.
Iron out the last NS6 problems, + document what can't be solved yet.
Get a resize fix for ns4 in place, nothing to fancy that'll cause other
bugs.
Then release that so there's one leakfree, cross-browser release available.
This shouldn't be an impossible task anymore.
Something I'm trying to find out is why NS4 sometimes does, and sometimes
doesn't render css.
I'm increasingly manipulating DynLayers css, and assigning css classes to
Dynlayers, but can't get this to work well on NS4.
If it can't be done, I'd like to draw up a kind of frame work, so css
classes can be used, yet something readable still renders on NS4.
I agree wit 8tan that v4 support should probably be split off in the end, to
allow optimizing v5+ code.
What Pascal is doing with DomLib is interesting, but still lacks the power
of DynAPI. It does however demonstrate that many simple things can be done
with just a few lines of code for V5+ browsers.
For instance, every dynlayer already has a scrollpane built in, if you use
the myLayer.css.overflow= 'scroll'; css call. And in IE5.5 it looks a lot
better than any DHTML versions I've seen so far (with style-sheet applied),
so ideally, our scrollpane should use the overflow scrolls for v5+ browsers,
and the current code for v4 browsers.
I could see browser sniffing done at the DynAPI.include(blah); level, so
there are two versions of each widget code. This is especially important for
things like the list widget.
The main thing is, we have gone as far as we can for v4 browsers, they will
never be able to do more than they can now, with the DynAPI, so if we can
iron out the last bugs, people can continue to use that version as long as
they need to support v4 browsers. - Maybe an update can be done when a new
browser is released, but that shouldn't be too much work.
After that we are free to do radical changes 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: <[EMAIL PROTECTED]>
Sent: 18 May, 2001 11:03
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 had been an actual decision made :)
>
> Cheers
> Scotto
>
> -----Ursprungligt meddelande-----
> Fr�n: Eytan Heidingsfeld [mailto:[EMAIL PROTECTED]]
> Skickat: den 18 maj 2001 12:04
> Till: [EMAIL PROTECTED]
> �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 PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
