You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(83) |
Nov
(319) |
Dec
(441) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(617) |
Feb
(784) |
Mar
(426) |
Apr
(363) |
May
(489) |
Jun
(396) |
Jul
(405) |
Aug
(146) |
Sep
(97) |
Oct
(146) |
Nov
(348) |
Dec
(99) |
2002 |
Jan
(69) |
Feb
(92) |
Mar
(58) |
Apr
(33) |
May
(29) |
Jun
(45) |
Jul
(72) |
Aug
(71) |
Sep
(47) |
Oct
(19) |
Nov
(48) |
Dec
(55) |
2003 |
Jan
(23) |
Feb
(73) |
Mar
(42) |
Apr
(52) |
May
(64) |
Jun
(155) |
Jul
(169) |
Aug
(103) |
Sep
(113) |
Oct
(118) |
Nov
(46) |
Dec
(30) |
2004 |
Jan
(19) |
Feb
(24) |
Mar
(40) |
Apr
(13) |
May
(35) |
Jun
(1) |
Jul
(23) |
Aug
(3) |
Sep
(31) |
Oct
(31) |
Nov
(26) |
Dec
|
2005 |
Jan
(5) |
Feb
(4) |
Mar
(3) |
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
(23) |
Sep
(9) |
Oct
(5) |
Nov
(2) |
Dec
(1) |
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Scott A. L. <sc...@sc...> - 2000-10-26 23:15:24
|
Hello Fredrik, What needs to happen is: when the loadHTML is finished loading content into the scrolling layer, the layer must resize itself to fit the content. When the layer resizes to fit, the scrollbars should activate if it's larger than the containing window pane. I'm not sure how to implement this, though. IlMaestro? scottandrew Hegardt wrote: > > Hi! > > I'm new to DynAPI 2 (actually new to dhtml), and I'm impressed! > > However I have a problem: > > I want to be able to scroll the contents of a layer that is loaded from a separate .html-file. I have tried combining the core.ext.loadhtml.js and the core.ibs.scrollwindow.js, but it doesn't work. Is it possible att all? > > Regards, > > Fredrik Hegardt > > _______________________________________________ > Dynapi-Help mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-help |
From: Jannon F. <ja...@CS...> - 2000-10-26 23:08:46
|
New Guy here, So I'm a long time user of the original DynAPI and am all too familiar with the frustrations involved in using that one and having to tweak it for your specific purposes. I mean I was glad to have it, but I'm really stoked about DynAPI 2. Anyway, decent API documentation is something I am missing. To that end, last week I started to create a documentation system. I've got a real rough mysql schema with tables for packages, classes, methods, properties, parameters, etc. I was just going to set up some servlets and have my own little system, but I think others would benefit. There are two issues: 1. I don't have an mysql account somewhere static (I can't serve off my machine) 2. Documentation bores the hell out of me But I'm more than willing to offer my beginnings as a starting point. It could definitely use some more thinking through and discussion. I orignially started working with Java API documentation in mind. I'm also willing to help develop and host the interface (preferrably using JSP). So, I guess I'll put the sql files up somewhere and we can let the discussion begin. -jannon -- "Sometimes the majority only means that all the fools are on the same side." - ?? > -----Original Message----- > From: dyn...@li... > [mailto:dyn...@li...]On Behalf Of Tarun > Sent: Thursday, October 26, 2000 8:08 AM > To: 'dyn...@li...' > Subject: [Dynapi-Help] Agree with Jack > > > I believe that what Jack says is quite correct. Newbies like us > would love to > contribute something what the experts dont have time to do ,like > maintaining > API documentation (which currently is very little), maybe a > searchable help > system... > If we know where to start we could get working pronto :-) > _______________________________________________ > Dynapi-Help mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-help |
From: Hegardt <he...@mf...> - 2000-10-26 22:06:17
|
Hi! I'm new to DynAPI 2 (actually new to dhtml), and I'm impressed! However I have a problem: I want to be able to scroll the contents of a layer that is loaded from a separate .html-file. I have tried combining the core.ext.loadhtml.js and the core.ibs.scrollwindow.js, but it doesn't work. Is it possible att all? Regards, Fredrik Hegardt |
From: Eytan H. <ey...@tr...> - 2000-10-26 19:49:25
|
Not only libraries or lists as you call them. Maybe we can improve inheritance and create a TObject (for delphi users). Then we will be OOP and not DLOP(Dynamic Layer Oriented). 8an PS I wasn't insulted by anyone thanx |
From: Jack_Speranza <jsp...@gr...> - 2000-10-26 19:30:58
|
I downloaded both the "full" and "core" zip files. As I write this, I'm beginning to think it's entirely possible I did not overwrite the dynapi.js file that was already in my dev environment when I ported the new release over... Ok... I feel *real* stupid now. That's exactly what happened. I just checked the download, and sure enough, the correct dymapi.js file is in there. Despite trying to keep my files current with the sourceForge releases, I must have been continuing to neglect updating the dynapi.js file. I'm very sorry for creating all the "cornfusion"... -----Original Message----- From: Robert Rainwater [mailto:rai...@us...] Sent: Thursday, October 26, 2000 3:18 PM To: Jack_Speranza Subject: Re[4]: [Dynapi-Help] New DynAPI release and DynDocument Event s > So, it appears the most recent release does NOT include the > appropriate dynapi.js code. Hi, Which version did you download? Mine has the getDocument in it from the 10.24 release? Later, Robert <rai...@us...> _______________________________________________ Dynapi-Help mailing list Dyn...@li... http://lists.sourceforge.net/mailman/listinfo/dynapi-help |
From: Robert R. <rai...@us...> - 2000-10-26 19:17:17
|
> So, it appears the most recent release does NOT include the > appropriate dynapi.js code. Hi, Which version did you download? Mine has the getDocument in it from the 10.24 release? Later, Robert <rai...@us...> |
From: Scott A. L. <sc...@sc...> - 2000-10-26 17:54:39
|
I think I understand. You want to create objects that manage other similar objects? Like a 'library' of strings or images that can be referenced easily? I remember StringList, but I see it was postponed as a patch because (I think) it wasn't clear what it does. Maybe some documentation or samples would help? I don't remember anyone laughing at you, but please accept my apologies if there were :-) Eytan Heidingsfeld wrote: > > When I created a StringList type I was laughed at. I mean things like: > > Types - we have to think about that. JS uses variants maybe we should > consider including certain types. Also adding object types such as; > StringList > ImageList > PointerList(in JS is equal to ObjectList) > other types (the only things I can think of now but more will come to me) > Setting ques and more events. > > I have a headace and can't think of many things I though of yesterday. My > ideas aren't complicated but need to be done. > > 8an > > _______________________________________________ > Dynapi-Help mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-help |
From: Pascal B. <pa...@dy...> - 2000-10-26 17:35:05
|
Here's a fix for the inline layers, I'll upload it as patch to sourceforge as well. Simply replace the core.ext.inline file with this code: /* Core DynAPI Distribution AddOn extensions */ DynAPI.findLayers=function(dyndoc,or) { var divs=[] or=or||dyndoc if (is.ns4) divs = dyndoc.doc.layers if (is.ns5) divs = dyndoc.doc.getElementsByTagName("DIV") if (is.ie) divs = dyndoc.doc.all.tags("DIV") for (var i=0; i<divs.length; i++) { if(DynAPI.isDirectChildOf(divs[i],dyndoc.elm)) { var id=is.ns4? divs[i].name : divs[i].id var dlyr=new DynLayer(id) dlyr.parent=dyndoc dlyr.assignElement(divs[i]) dlyr.dyndoc=or if (or.getClass()!=DynDocument) dlyr.isChild=true else { DynAPI.removeFromArray(DynAPI.document.all, dlyr, true) or.all[or.all.length]=dlyr or.all[dlyr.id]=dlyr } dyndoc.children[dyndoc.children.length]=dlyr var index=id.indexOf("Div") if (index>0) dyndoc.doc.window[id.substr(0,index)] = dyndoc.all[id] if (is.ns4) {for (ict in dlyr.doc.images) dlyr.doc.images[ict].lyrobj=dlyr} else if (is.ns5) {for (ict in dlyr.doc.images) dlyr.doc.images[ict].lyrobj=dlyr.elm} else {for (ict in dlyr.elm.all.tags("img")) dlyr.elm.all.tags("img")[ict].lyrobj=dlyr} if (dlyr.updateValues) dlyr.updateValues() DynAPI.findLayers(dlyr,or) } } } DynLayer.prototype.updateValues=function() { if (is.ns) { this.x=parseInt(this.css.left) this.y=parseInt(this.css.top) this.w=is.ns4? this.css.clip.width : parseInt(this.css.width) this.h=is.ns4? this.css.clip.height : parseInt(this.css.height) if (is.ns4) this.clip=[this.css.clip.top,this.css.clip.right,this.css.clip.bottom,this.c ss.clip.left] this.bgColor = this.doc.bgColor!="this.doc.bgColor"?this.doc.bgColor:null this.bgImage = this.elm.background.src!=""?this.elm.background.src:null this.html = this.innerHTML = this.elm.innerHTML = "" } else if (is.ie) { this.x=this.elm.offsetLeft this.y=this.elm.offsetTop this.w=is.ie4? this.css.pixelWidth : this.elm.offsetWidth this.h=is.ie4? this.css.pixelHeight : this.elm.offsetHeight this.bgImage = this.css.backgroundImage this.bgColor = this.css.backgroundColor this.html = this.innerHTML = this.elm.innerHTML } this.z = this.css.zIndex var b = this.css.visibility this.visible = (b=="inherit"||b=="show"||b=="visible"||b=="") } DynAPI.getModel=function() { dom='DYNAPI OBJECT MODEL:\n\n+DynAPI\n' for (var i=0; i<DynAPI.documents.length; i++) { dom+=' +'+DynAPI.documents[i].toString()+'\n' for (var j=0; j<DynAPI.documents[i].all.length; j++) dom+='+'+DynAPI.documents[i].all[j].toString()+'\n' } alert(dom) } DynAPI.isDirectChildOf = function(l, parent) { if(is.ns) return (l.parentLayer == parent) for(var p=l.parentElement;p;p=p.parentElement) if(p.tagName.toLowerCase()=='div') return p==parent return !parent.tagName } //-------------------------------------------------------------------------- ------------------------------- For those who care: There was a problem in the image code, it was resetting the variable i everytime. greets, Pascal Bestebroer pa...@dy... http://www.dynamic-core.net |
From: Scott A. L. <sc...@sc...> - 2000-10-26 17:34:45
|
Hmm. Can you do that in IE too somehow? If so, maybe we should add that as a method of DynDocument. A "clipping" method that sets document width/height at runtime. Ben Sargent wrote: > > My widget basically takes a series of layers and gives them "tree-like" > properties... you can expand and collapse parts of the document without > re-submitting the page. I'm drawing a lot on the DynAPI event model to > ensure cross-broswer (and future browser!) compatibility. The sticking > poing has been Netscape's unwillingness to resize the document... > however, IlMaestro's suggestion (see previous thread) concerning setting > document.height seems to be working very nicely. > > Thanks to everybody for their help and suggestions! > > ben > > Scott Andrew LePera wrote: > > > > I think Tarun is right. In fact, if you use an absolutely positioned > > layer but don't specify height, the content will cause the layer to > > expand vertically, like a table cell (at least it works for me). Maybe > > then you can grab them with findLayers? > > > > Tarun R Elankath wrote: > > > > > > Hey why dont you just use plain statically positioned inline layers with the > > > content instead. Netscape then gives 'em good ol' scollbars. > > > Most of the functionality of Dynlayers is already available to inline layers > > > except for (a few) bugs regarding event capturing in nested layers > > -- > Ben Sargent > Montage eIntegration Inc. > www.montage.ca > GFX: www.infinitespaces.com > PGP: /pgpkey.txt > _______________________________________________ > Dynapi-Help mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-help |
From: Eytan H. <ey...@tr...> - 2000-10-26 17:33:51
|
When I created a StringList type I was laughed at. I mean things like: Types - we have to think about that. JS uses variants maybe we should consider including certain types. Also adding object types such as; StringList ImageList PointerList(in JS is equal to ObjectList) other types (the only things I can think of now but more will come to me) Setting ques and more events. I have a headace and can't think of many things I though of yesterday. My ideas aren't complicated but need to be done. 8an |
From: Ben S. <ben...@tr...> - 2000-10-26 17:28:00
|
My widget basically takes a series of layers and gives them "tree-like" properties... you can expand and collapse parts of the document without re-submitting the page. I'm drawing a lot on the DynAPI event model to ensure cross-broswer (and future browser!) compatibility. The sticking poing has been Netscape's unwillingness to resize the document... however, IlMaestro's suggestion (see previous thread) concerning setting document.height seems to be working very nicely. Thanks to everybody for their help and suggestions! ben Scott Andrew LePera wrote: > > I think Tarun is right. In fact, if you use an absolutely positioned > layer but don't specify height, the content will cause the layer to > expand vertically, like a table cell (at least it works for me). Maybe > then you can grab them with findLayers? > > Tarun R Elankath wrote: > > > > Hey why dont you just use plain statically positioned inline layers with the > > content instead. Netscape then gives 'em good ol' scollbars. > > Most of the functionality of Dynlayers is already available to inline layers > > except for (a few) bugs regarding event capturing in nested layers -- Ben Sargent Montage eIntegration Inc. www.montage.ca GFX: www.infinitespaces.com PGP: /pgpkey.txt |
From: Ben S. <ben...@tr...> - 2000-10-26 17:11:48
|
All hail Jordi, King of the Netscape "feature" work-arounds! that rocks... ben Jordi Ministral wrote: > > The presence of scrollbars in Netscape is calculated once using the document.width > / document.height values. Once the page has been reloaded, these properties can be > set by your scripts in order to make the scrollbars appear. The only problem is > that this can only be done ONCE. Further modifications will be simply ignored. I > don't know the reason for such behaviour. > > Hope this helps > > Ben Sargent wrote: > > > It's helpful in that now I know *where* to start looking for a > > solution. I was hoping that there might be an elegant DynAPI way of > > doing this. My problem is that I'm creating a series of dynlayers whose > > height is determined by their HTML content... which isn't determined > > until after load time. At the very least, I can create a "worst > > possible scenario" page size using some static content, but then my page > > will end up with a lot of blank space at the end :( > > > > ben > > > > Jack_Speranza wrote: > > > > > > I encountered this same problem, and I believe it was addressed at one point > > > in the sourceForge forums (buried deep somewhere by now!). As I understand > > > it, because of the way Netscape operates, it won't provide scrollbars for > > > dynamic layers that appear outside of the visible window (unless there is > > > some static content that is in the same area). My rather inelegant solution > > > was to make sure there was some "invisible" static content wherever I was > > > going to be placing my dynLayers. Don't know if you find this helpful or > > > not... > > > > > > Jack > > > > > > -----Original Message----- > > > From: Ben Sargent [mailto:ben...@tr...] > > > Sent: Thursday, October 26, 2000 11:10 AM > > > To: DynAPI Help > > > Subject: [Dynapi-Help] Big Layers & Netscape Scollbars > > > > > > Hello. I posted this to the forums a few days ago, but it may have > > > gotten lost in the mailing-list shuffle, so hopefully nobody minds if I > > > post it here as well. > > > > > > Basically, I want to create several large layers one after another on a > > > page. However, once the layers (or group of layers) get larger than the > > > browser height, Netscape doesn't provide me with scrollbars. IE is very > > > nice about this. How do I get Netscape to let me scroll down my page? > > > > > > Thanks, > > > ben > > -- -- Ben Sargent Montage eIntegration Inc. www.montage.ca GFX: www.infinitespaces.com PGP: /pgpkey.txt |
From: Pascal B. <pa...@dy...> - 2000-10-26 17:09:25
|
What are you thinking of? could give more detail? Pascal Bestebroer pa...@dy... http://www.dynamic-core.net -----Oorspronkelijk bericht----- Van: dyn...@li... [mailto:dyn...@li...]Namens Eytan Heidingsfeld Verzonden: donderdag 26 oktober 2000 18:36 Aan: dyn...@li... Onderwerp: [Dynapi-Help] OOP Hi, I joined a while back and although being quite have played around with DynAPI. At my office we are working on a project which will involve it too. So I can use it for work and play! Something I always wanted to do was create a more OOP usage for somethings in DynAPI. I liked the include idea and others. I guess I just want to know if anyone wants to help. I won't do it alone because I'll just drift away and forget about it. So, are there any takers? 8an _______________________________________________ Dynapi-Help mailing list Dyn...@li... http://lists.sourceforge.net/mailman/listinfo/dynapi-help |
From: Scott A. L. <sc...@sc...> - 2000-10-26 17:06:04
|
I think Tarun is right. In fact, if you use an absolutely positioned layer but don't specify height, the content will cause the layer to expand vertically, like a table cell (at least it works for me). Maybe then you can grab them with findLayers? Tarun R Elankath wrote: > > Hey why dont you just use plain statically positioned inline layers with the > content instead. Netscape then gives 'em good ol' scollbars. > Most of the functionality of Dynlayers is already available to inline layers > except for (a few) bugs regarding event capturing in nested layers > _______________________________________________ > Dynapi-Help mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-help |
From: Jordi 'I. M. <jmi...@or...> - 2000-10-26 16:57:27
|
Absolutely Scott Andrew LePera wrote: > I think this needs fixed :-) > > getDocument : function(id) { > if (!id) return DynAPI.document > return DynAPI.documents[id] // <--- "documents" not "document" > } > _______________________________________________ > Dynapi-Help mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-help |
From: Tarun R E. <ta...@we...> - 2000-10-26 16:50:21
|
Hey why dont you just use plain statically positioned inline layers with the content instead. Netscape then gives 'em good ol' scollbars. Most of the functionality of Dynlayers is already available to inline layers except for (a few) bugs regarding event capturing in nested layers |
From: Scott A. L. <sc...@sc...> - 2000-10-26 16:44:38
|
I think this needs fixed :-) getDocument : function(id) { if (!id) return DynAPI.document return DynAPI.documents[id] // <--- "documents" not "document" } |
From: Jordi M. <jmi...@or...> - 2000-10-26 16:39:10
|
The presence of scrollbars in Netscape is calculated once using the document.width / document.height values. Once the page has been reloaded, these properties can be set by your scripts in order to make the scrollbars appear. The only problem is that this can only be done ONCE. Further modifications will be simply ignored. I don't know the reason for such behaviour. Hope this helps Ben Sargent wrote: > It's helpful in that now I know *where* to start looking for a > solution. I was hoping that there might be an elegant DynAPI way of > doing this. My problem is that I'm creating a series of dynlayers whose > height is determined by their HTML content... which isn't determined > until after load time. At the very least, I can create a "worst > possible scenario" page size using some static content, but then my page > will end up with a lot of blank space at the end :( > > ben > > Jack_Speranza wrote: > > > > I encountered this same problem, and I believe it was addressed at one point > > in the sourceForge forums (buried deep somewhere by now!). As I understand > > it, because of the way Netscape operates, it won't provide scrollbars for > > dynamic layers that appear outside of the visible window (unless there is > > some static content that is in the same area). My rather inelegant solution > > was to make sure there was some "invisible" static content wherever I was > > going to be placing my dynLayers. Don't know if you find this helpful or > > not... > > > > Jack > > > > -----Original Message----- > > From: Ben Sargent [mailto:ben...@tr...] > > Sent: Thursday, October 26, 2000 11:10 AM > > To: DynAPI Help > > Subject: [Dynapi-Help] Big Layers & Netscape Scollbars > > > > Hello. I posted this to the forums a few days ago, but it may have > > gotten lost in the mailing-list shuffle, so hopefully nobody minds if I > > post it here as well. > > > > Basically, I want to create several large layers one after another on a > > page. However, once the layers (or group of layers) get larger than the > > browser height, Netscape doesn't provide me with scrollbars. IE is very > > nice about this. How do I get Netscape to let me scroll down my page? > > > > Thanks, > > ben > -- > Ben Sargent > Montage eIntegration Inc. > www.montage.ca > GFX: www.infinitespaces.com > PGP: /pgpkey.txt > _______________________________________________ > Dynapi-Help mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-help |
From: Eytan H. <ey...@tr...> - 2000-10-26 16:36:15
|
Hi, I joined a while back and although being quite have played around with DynAPI. At my office we are working on a project which will involve it too. So I can use it for work and play! Something I always wanted to do was create a more OOP usage for somethings in DynAPI. I liked the include idea and others. I guess I just want to know if anyone wants to help. I won't do it alone because I'll just drift away and forget about it. So, are there any takers? 8an |
From: Jordi 'I. M. <jmi...@or...> - 2000-10-26 16:26:13
|
Just in case: getDocument : function(id) { if (!id) return DynAPI.document return DynAPI.document[id] } |
From: Jack_Speranza <jsp...@gr...> - 2000-10-26 16:16:36
|
Yeah... there's never an easy answer (or so it seems :-) My answer to this problem was to create some static visual content that at least made it half-way acceptable for there to be blank space at the bottom of the page (colorful margin layers, footers, etc.). Until I become more familiar with web development (a new career for me...), inelegant solutions look like they will be a part of life... (is it too optomistic for me to think they will ever disappear?) -----Original Message----- From: Ben Sargent [mailto:ben...@tr...] Sent: Thursday, October 26, 2000 12:12 PM To: dyn...@li... Subject: Re: [Dynapi-Help] Big Layers & Netscape Scollbars It's helpful in that now I know *where* to start looking for a solution. I was hoping that there might be an elegant DynAPI way of doing this. My problem is that I'm creating a series of dynlayers whose height is determined by their HTML content... which isn't determined until after load time. At the very least, I can create a "worst possible scenario" page size using some static content, but then my page will end up with a lot of blank space at the end :( ben Jack_Speranza wrote: > > I encountered this same problem, and I believe it was addressed at one point > in the sourceForge forums (buried deep somewhere by now!). As I understand > it, because of the way Netscape operates, it won't provide scrollbars for > dynamic layers that appear outside of the visible window (unless there is > some static content that is in the same area). My rather inelegant solution > was to make sure there was some "invisible" static content wherever I was > going to be placing my dynLayers. Don't know if you find this helpful or > not... > > Jack > > -----Original Message----- > From: Ben Sargent [mailto:ben...@tr...] > Sent: Thursday, October 26, 2000 11:10 AM > To: DynAPI Help > Subject: [Dynapi-Help] Big Layers & Netscape Scollbars > > Hello. I posted this to the forums a few days ago, but it may have > gotten lost in the mailing-list shuffle, so hopefully nobody minds if I > post it here as well. > > Basically, I want to create several large layers one after another on a > page. However, once the layers (or group of layers) get larger than the > browser height, Netscape doesn't provide me with scrollbars. IE is very > nice about this. How do I get Netscape to let me scroll down my page? > > Thanks, > ben -- Ben Sargent Montage eIntegration Inc. www.montage.ca GFX: www.infinitespaces.com PGP: /pgpkey.txt _______________________________________________ Dynapi-Help mailing list Dyn...@li... http://lists.sourceforge.net/mailman/listinfo/dynapi-help |
From: Ben S. <ben...@tr...> - 2000-10-26 16:07:39
|
It's helpful in that now I know *where* to start looking for a solution. I was hoping that there might be an elegant DynAPI way of doing this. My problem is that I'm creating a series of dynlayers whose height is determined by their HTML content... which isn't determined until after load time. At the very least, I can create a "worst possible scenario" page size using some static content, but then my page will end up with a lot of blank space at the end :( ben Jack_Speranza wrote: > > I encountered this same problem, and I believe it was addressed at one point > in the sourceForge forums (buried deep somewhere by now!). As I understand > it, because of the way Netscape operates, it won't provide scrollbars for > dynamic layers that appear outside of the visible window (unless there is > some static content that is in the same area). My rather inelegant solution > was to make sure there was some "invisible" static content wherever I was > going to be placing my dynLayers. Don't know if you find this helpful or > not... > > Jack > > -----Original Message----- > From: Ben Sargent [mailto:ben...@tr...] > Sent: Thursday, October 26, 2000 11:10 AM > To: DynAPI Help > Subject: [Dynapi-Help] Big Layers & Netscape Scollbars > > Hello. I posted this to the forums a few days ago, but it may have > gotten lost in the mailing-list shuffle, so hopefully nobody minds if I > post it here as well. > > Basically, I want to create several large layers one after another on a > page. However, once the layers (or group of layers) get larger than the > browser height, Netscape doesn't provide me with scrollbars. IE is very > nice about this. How do I get Netscape to let me scroll down my page? > > Thanks, > ben -- Ben Sargent Montage eIntegration Inc. www.montage.ca GFX: www.infinitespaces.com PGP: /pgpkey.txt |
From: Scott A. L. <sc...@sc...> - 2000-10-26 15:51:30
|
I think Jack's correct. An empty DynLayer in NS has no "document height" or width until you actually add content to it. As an aside, what I think is interesting is I am always trying to do the opposite: turn the scrollbars *off* in IE. When I have an IE layer with content that exceeds it's clip area, I get browser scrollbars when the hidden content extends off the visible page. I hate that! scottandrew Jack_Speranza wrote: > > I encountered this same problem, and I believe it was addressed at one point > in the sourceForge forums (buried deep somewhere by now!). As I understand > it, because of the way Netscape operates, it won't provide scrollbars for > dynamic layers that appear outside of the visible window (unless there is > some static content that is in the same area). My rather inelegant solution > was to make sure there was some "invisible" static content wherever I was > going to be placing my dynLayers. Don't know if you find this helpful or > not... > > Jack > > -----Original Message----- > From: Ben Sargent [mailto:ben...@tr...] > Sent: Thursday, October 26, 2000 11:10 AM > To: DynAPI Help > Subject: [Dynapi-Help] Big Layers & Netscape Scollbars > > Hello. I posted this to the forums a few days ago, but it may have > gotten lost in the mailing-list shuffle, so hopefully nobody minds if I > post it here as well. > > Basically, I want to create several large layers one after another on a > page. However, once the layers (or group of layers) get larger than the > browser height, Netscape doesn't provide me with scrollbars. IE is very > nice about this. How do I get Netscape to let me scroll down my page? > > Thanks, > ben > > -- > Ben Sargent > Montage eIntegration Inc. > www.montage.ca > GFX: www.infinitespaces.com > PGP: /pgpkey.txt > _______________________________________________ > Dynapi-Help mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-help > _______________________________________________ > Dynapi-Help mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-help |
From: Jack_Speranza <jsp...@gr...> - 2000-10-26 15:14:54
|
I encountered this same problem, and I believe it was addressed at one point in the sourceForge forums (buried deep somewhere by now!). As I understand it, because of the way Netscape operates, it won't provide scrollbars for dynamic layers that appear outside of the visible window (unless there is some static content that is in the same area). My rather inelegant solution was to make sure there was some "invisible" static content wherever I was going to be placing my dynLayers. Don't know if you find this helpful or not... Jack -----Original Message----- From: Ben Sargent [mailto:ben...@tr...] Sent: Thursday, October 26, 2000 11:10 AM To: DynAPI Help Subject: [Dynapi-Help] Big Layers & Netscape Scollbars Hello. I posted this to the forums a few days ago, but it may have gotten lost in the mailing-list shuffle, so hopefully nobody minds if I post it here as well. Basically, I want to create several large layers one after another on a page. However, once the layers (or group of layers) get larger than the browser height, Netscape doesn't provide me with scrollbars. IE is very nice about this. How do I get Netscape to let me scroll down my page? Thanks, ben -- Ben Sargent Montage eIntegration Inc. www.montage.ca GFX: www.infinitespaces.com PGP: /pgpkey.txt _______________________________________________ Dynapi-Help mailing list Dyn...@li... http://lists.sourceforge.net/mailman/listinfo/dynapi-help |
From: Tarun <ta...@we...> - 2000-10-26 15:08:46
|
I believe that what Jack says is quite correct. Newbies like us would love to contribute something what the experts dont have time to do ,like maintaining API documentation (which currently is very little), maybe a searchable help system... If we know where to start we could get working pronto :-) |