From: Robert R. <rra...@ya...> - 2000-11-28 21:03:25
|
I was thinking about a post someone had about getting errors because they didnt include dyndocument.js. Shouldn't dyndocument be a plugin. That way allow of the initialization stuff of the dyndocument can be done in dyndocument.js. This way no dyndocument stuff will be in the dynapi.js file. Isn't that what the plugin idea was for anyway? -- // Robert Rainwater |
From: Scott A. L. <sc...@sc...> - 2000-11-28 22:27:06
|
There's something I don't understand about the current DynAPI implementation. Many of the core scripts have dependencies on the others. DynLayer and DynAPI require DynDocument, and almost all core scripts require BrowserCheck. Yet I see a lot of people including these scripts one-by-one, instead of just including the core.api package. The core scripts probably shouldn't really be treated as optional plug-ins. If DynAPI can't find DynDocument, it will fail when creating the default DynDocument. Etc, etc. -- scott andrew lepera ----------------------------------- web stuff: www.scottandrew.com music stuff: www.walkingbirds.com |
From: Brandon M. <bnd...@ho...> - 2000-11-28 22:38:56
|
DynAPI is very dependent on the DynDocument.js file. DynAPI is the absolute core of DynAPI 2. It is the single place where globally accessed things can be stored. Unassigned layers, DynDocument lists, API options, inclusion routines, etc. DynAPI.dyndoc <- This has become common practice to retrieve the default DynDocument object. Besides, 99.9% of the apps use the API for layers. And this object is required to use layers. I have solved a basic problem of, what if I want to use other objects developed for DynAPI, use the DynAPI object, but not use any layering... (Which I have done). I simply placed this in the loadHandler of the DynAPI object. So.. if these changes where made, I feel that DynDocument could become an "Optional" object when not needed. from: DynAPI.document.findDimensions() if (DynAPI.findLayers) DynAPI.findLayers(DynAPI.document) if (DynAPI.document.captureMouseEvents) DynAPI.document.captureMouseEvents() DynAPI.loaded=false; if (DynAPI.document.invokeEvent) DynAPI.document.invokeEvent('beforeload') if (DynAPI.document.invokeEvent) DynAPI.document.invokeEvent('load') if (DynAPI.onLoad) DynAPI.onLoad() for (var i=0;i<DynAPI.plugins.length; i++) if (DynAPI.plugins[i].onLoad) DynAPI.plugins[i].onLoad() DynAPI.loaded=true if (DynAPI.document.invokeEvent) DynAPI.document.invokeEvent('afterload') if (DynAPI.loaderStart) DynAPI.loaderStart() to: DynAPI.loaded=false; if (typeof DynDocument!='undefined') { DynAPI.document.findDimensions() if (DynAPI.findLayers) DynAPI.findLayers(DynAPI.document) if (DynAPI.document.captureMouseEvents) DynAPI.document.captureMouseEvents() if (DynAPI.document.invokeEvent) DynAPI.document.invokeEvent('beforeload') if (DynAPI.document.invokeEvent) DynAPI.document.invokeEvent('load') } if (DynAPI.onLoad) DynAPI.onLoad() for (var i=0;i<DynAPI.plugins.length; i++) if (DynAPI.plugins[i].onLoad) DynAPI.plugins[i].onLoad() DynAPI.loaded=true if (DynAPI.loaderStart) DynAPI.loaderStart() if (typeof DynDocument!='undefined') { if (DynAPI.document.invokeEvent) DynAPI.document.invokeEvent('afterload') } ----- Original Message ----- From: "Robert Rainwater" <rra...@ya...> To: <dyn...@li...> Sent: Tuesday, November 28, 2000 4:05 PM Subject: [Dynapi-Dev] DynDocument Plugin? > I was thinking about a post someone had about getting errors because > they didnt include dyndocument.js. Shouldn't dyndocument be a plugin. > That way allow of the initialization stuff of the dyndocument can be > done in dyndocument.js. This way no dyndocument stuff will be in the > dynapi.js file. Isn't that what the plugin idea was for anyway? > > -- > // Robert Rainwater > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
From: Craig T. <cr...@re...> - 2000-11-28 23:34:10
|
I'm new, and these are fundamental questions, but there's no faq on the site, so that's OK :) I had a play around with dynapi 12 months ago, remembered it yesterday and was very pleased to find that people had picked up the effort and continued with it. My attitude to web development at the moment is that I'll develop solely for mozilla. So my first question (more are sure to follow :) ) how does this stuff go working with Netscape 6 and Mozilla? Are any of the well-publicised bugs Netscape couldn't be bothered weeding out of their commercialish release limiting on the dynapi libraries? My second question is, are there any showcase sites for the technology yet? My uni crowd have some webspace and are about to undergo redevelopment, but I'd like to see dynapi in action (ideally). Nice work guys! - C |