First thing you should do is get the latest copy of the source using CVS. There is
instructions here:
http://sourceforge.net/cvs/?group_id=5757
The cvs software for RedHat is included on the Redhat CD, or can be downloaded from
ftp.redhat.com
The 11/07 dynapi release is a bit out of date now, some significant updates have been
made since then and should release most of the problems. I develop under Linux (in
fact RH 6.2 also), and everything works very well on Netscape now.
Dan
On Tue, Dec 19, 2000 at 05:15:48PM -0500, Daniel Shriver wrote:
> Hi,
> My system is Linux Zoot (6.2), with Netscape 4.72 running on it, I
> have the 11/07/2000 build of the dynapi.
> I'm working through the tutorial on the dynapi 2 and I'm finding
> erratic behavior. For one thing I find that examples on dragging work
> one day and not the next (giving an error in the dynapi.js of:
>
> JavaScript Error:
> file:/home/DShriver/DHTML_INFO/dyn2_11_07_2000/dynapi/js/dynapi.js,
> line 92:
>
> group is not defined.
>
> JavaScript Error:
> file:/home/DShriver/DHTML_INFO/dyn2_11_07_2000/dynapi/js/dynapi.js,
> line 45:
>
> DynDocument is not defined.
> )
>
> The code looks reasonable and it looks like the variables should be
> defined (there are statements setting them up, so I could only see them
> being undefined if their building blocks were null) and I have not
> touched the API.
>
> Also the previous day I got as far as the widget tutorial and found that
> when I tried open the widget page in my browser
> it killed the browser (I repeated this behavior many times, even after a
> fresh rebooting).
>
> Is there some strange issue with the API not working quite right on
> Linux or with 4.72, or both? Or did I set things up incorrectly.
>
> Also is there some good DHTML ref for building "widgets" out there. All
> I want (right now) out of DHTML is scrollable
> windows. I've done a LOT of surfing to find them and have found
> numerous toolkits but they all seem to have one or more of the following
> flaws:
> -big gaps in browser cross compatability
> -buggy (some of them just don't work right, some have
> problems that can be fixed by me refreshing the page but
> I view this as unacceptable to the end user,
> ...).
> I probably will not want anything else for quite some time and when I do
> it will most likely be some other vanilla content navigation tool. The
> big goal for me is solid browser cross compatablity. It would be
> acceptable for the tools to only work with IE4 (and beyond), and NS4
> (and beyond) on various OS's and boxes.
>
> Ideally I'd like to work with some toolkit that does all the "magic" for
> me (branching around different DOM's and browser flaws) leaving me to
> deal with only logic and presentation issues.
>
>
>
> _______________________________________________
> Dynapi-Help mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/mailman/listinfo/dynapi-help
_______________________________________________
Dynapi-Help mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/dynapi-help
