You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(75) |
Nov
(252) |
Dec
(418) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(659) |
Feb
(1039) |
Mar
(870) |
Apr
(235) |
May
(329) |
Jun
(251) |
Jul
(123) |
Aug
(119) |
Sep
(67) |
Oct
(194) |
Nov
(535) |
Dec
(133) |
2002 |
Jan
(122) |
Feb
(24) |
Mar
(29) |
Apr
(28) |
May
(16) |
Jun
(20) |
Jul
(11) |
Aug
(12) |
Sep
(13) |
Oct
(14) |
Nov
(23) |
Dec
(19) |
2003 |
Jan
(28) |
Feb
(170) |
Mar
(288) |
Apr
(211) |
May
(126) |
Jun
(166) |
Jul
(131) |
Aug
(102) |
Sep
(211) |
Oct
(301) |
Nov
(22) |
Dec
(6) |
2004 |
Jan
(14) |
Feb
(16) |
Mar
(7) |
Apr
|
May
(8) |
Jun
(25) |
Jul
(21) |
Aug
(2) |
Sep
(7) |
Oct
|
Nov
(2) |
Dec
(1) |
2005 |
Jan
(4) |
Feb
(2) |
Mar
(14) |
Apr
(24) |
May
(3) |
Jun
(7) |
Jul
(30) |
Aug
(5) |
Sep
(1) |
Oct
(3) |
Nov
|
Dec
(1) |
2006 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
From: Dan W. <da...@wi...> - 2003-05-01 11:02:31
|
On Wed, 2003-04-30 at 23:25, Raymond Irving wrote: > Hello, > > I propose that instead using layers (highlighters) to > create borders in DOM browsers we simply extend the > clipped area (w,h)to twice the border size: > > var w=((this.w+this._borClipOff)||0); > var h=((this.h+this._borClipOff)||0); > this.css.clip='rect(0px '+w+'px '+h+'px 0px)'; My question, why even bother with this in dom browsers, you should be able to set the css border property, and not touch the clipping. Shouldn't we? This would allow some of the special border designs on new browsers(like dashed, dotted, inset, outset, etc.) > > The above will cause layers when viewed in DOM to > appear a little wider than when viewed in IE. This > should not be a problem for most designs as the > deigner can work around this. My main reason for doing > this is obvious... CSS is much faster than using > layers to create borders. > > The designer will also have the option of using > highlighters to create borders in either IE or DOM. > This is done by drawing four child layers around the > parent layer: > > setBorder(size, color, useLyr); > size = size of border > color = color of border (e.g. "#FF00FF" or > {top:"#FFFFFF", right:"C0C0C0", bottom:"C0C0C0", > left:"FFFFFF"}) > useLyr = (Optional) Forces the use of Layers as > borders. This is always true for NS4 but defaults to > false for DOM and IE. > > Do you agree to this implementation? > > -- > Raymond Irving -- Dan Willemsen <da...@wi...> |
From: Raymond I. <xw...@ya...> - 2003-05-01 04:25:42
|
Hello, I propose that instead using layers (highlighters) to create borders in DOM browsers we simply extend the clipped area (w,h)to twice the border size: var w=((this.w+this._borClipOff)||0); var h=((this.h+this._borClipOff)||0); this.css.clip='rect(0px '+w+'px '+h+'px 0px)'; The above will cause layers when viewed in DOM to appear a little wider than when viewed in IE. This should not be a problem for most designs as the deigner can work around this. My main reason for doing this is obvious... CSS is much faster than using layers to create borders. The designer will also have the option of using highlighters to create borders in either IE or DOM. This is done by drawing four child layers around the parent layer: setBorder(size, color, useLyr); size = size of border color = color of border (e.g. "#FF00FF" or {top:"#FFFFFF", right:"C0C0C0", bottom:"C0C0C0", left:"FFFFFF"}) useLyr = (Optional) Forces the use of Layers as borders. This is always true for NS4 but defaults to false for DOM and IE. Do you agree to this implementation? -- Raymond Irving __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com |
From: Doug M. <do...@cr...> - 2003-04-30 12:57:32
|
Windows 2000 - AMD Thunderbird 900Mhz - 256 MB ram Mozilla 1.4a - 300 layers in 681 milliseconds IE 5.5 - 300 layers in 360 milliseconds I suspect that should say "colors in x milliseconds" ? ----- Original Message ----- From: "Raymond Irving" <xw...@ya...> To: <dyn...@li...> Sent: Wednesday, April 30, 2003 12:09 PM Subject: [Dynapi-Dev] DynLayer Highlighters > Hello Everyone, > > Please check out this new Highlighter library that > will be used to create borders, etc: > > http://www24.brinkster.com/dyntools/next/examples/dynapi.api.dynlayer-highli ghter.html > > Note: This demo does not support ns4 as yet. To get > the best results remove the fadeColor() function from > the demo. > > What do you think? Are they fast enough to be used as > highlighters? > > > -- > Raymond Irving > > > > > __________________________________ > Do you Yahoo!? > The New Yahoo! Search - Faster. Easier. Bingo. > http://search.yahoo.com > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://www.mail-archive.com/dyn...@li.../ > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.476 / Virus Database: 273 - Release Date: 4/25/2003 |
From: Dan W. <da...@wi...> - 2003-04-30 11:10:04
|
On Tue, 2003-04-29 at 23:09, Raymond Irving wrote: > Hello Everyone, > > Please check out this new Highlighter library that > will be used to create borders, etc: > > http://www24.brinkster.com/dyntools/next/examples/dynapi.api.dynlayer-highlighter.html > > Note: This demo does not support ns4 as yet. To get > the best results remove the fadeColor() function from > the demo. > > What do you think? Are they fast enough to be used as > highlighters? > > This looks nice. I've been playing with the new Netscape Javascript Debugger, it has the ability to show how many times each function is called, and their average speeds, etc. Its pretty cool. Attached is the output from this page. > -- > Raymond Irving -- Dan Willemsen <da...@wi...> |
From: Raymond I. <xw...@ya...> - 2003-04-30 04:09:10
|
Hello Everyone, Please check out this new Highlighter library that will be used to create borders, etc: http://www24.brinkster.com/dyntools/next/examples/dynapi.api.dynlayer-highlighter.html Note: This demo does not support ns4 as yet. To get the best results remove the fadeColor() function from the demo. What do you think? Are they fast enough to be used as highlighters? -- Raymond Irving __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com |
From: Dan W. <da...@wi...> - 2003-04-29 21:24:54
|
On Tue, 2003-04-29 at 09:52, Joy Ride wrote: > Hello, > > I would like to make few notes about comming release of DynAPI3. I'm sorry > for that I haven't gone trough DynAPI3 code so that I would know wheter > these are allready taken count of. These are based on our experience and if > any one of you have better knowledge if these issues, I would be happy to > know about them. > > 1) There should be attention paid in to image size/sizing issues in DynAPI3. > (At least in DynAPI2 there were several problems related in it.) Netscape > 6/7 and Opera browsers are able to find out image dimensions only after the > whole document is loaded. There for DynAPI should employ mechanism which > prevents image size queries before document is loaded on these browsers. > Exspecially DynAPI core shouldn't rely on image dimensions before document > is fully loaded. > > 2) The Javascript engine of Netscape is very slow on what comes to events. > Special atention should be paid in to performance issues in Netscape > browsers (more shortcuts / performance tweaks?). Exspecially dragging is a > problem in Netscape. Jukka suggested that it might be good idea to consider > different approaches to click events and drag events in Netscape (simplified > drag module for Netscape?). I don't know if this is possible, but maybe it would work better if we use some more native netscape 6+ objects, instead of the standard dom. Netscape has 'behaviors' in their css files for the browsers themselves to call javascript function, say on mouseover of an element, etc. > > 3) In Netscape 4 loading is the hardest issue. Fairly badly documented > feature describes that Netscape 4 can have only one layer open for loading > at the time. Other layers have to be closed before loading stuff in to other > layer (note that Netscape doesn't close layer automaticly). If something is > tried to load in to layer when other layer is open Netscape crashes. This > suggests that some sort of loader is needed (based on our testes, in some > browsers onLoad detection is not 100% acurate). > > 4) Opera 5 is very slooooooow... it may affect in to some script > functionality. > > 5) Definition of looks should be made with styles when ever possible. Style > definitions should be done based on DOM standard. I totally agree with this, unless the current standards(CSS&DOM) are very bad in depicting a certain value and what it means, I say stick with the standards. We could also look at future standards values, like what is defined in CSS3. > Which means that widht > equals in to width of content area. Borders are excluded from this width > (this behavior differes from DynAPI2 approach). Following browsers use DOM > standard in a way described earlier (others need to be fixed "manually" in > dynapi): Opera from version 6 on, Netscape from version 6 on, MSIE from > version 5 on machintosh platfom and MSIE from version 6 on PC platform. On > MSIE6 on PC platfor ther is one catch though. MSIE6 uses DOM behavior only > if there is correct doctype definition (=DOM) and link to correct standard > in HTML file header. Otherwice it uses old aproach, where borders (for > instance) are counted as part of widht. There for there should be (?) some > sort of detection for doctype definition in DynAPI. > > These are the issues, we think that should be dealt with DynAPI3 before > betarelease if they aren't dealt allready. I think that we will be able to > provide the results of browser compability tests (Excel files, we have > tested all the objects and methods separately on each browser) shortly... I > will let you know when we are ready with those. > > > - Juho Risku / Helmi Staff > http://www.visualway.com/helmi > > ___________________________________ Just a few thoughts.... -- Dan Willemsen <da...@wi...> |
From: Joy R. <joy...@ho...> - 2003-04-29 14:52:39
|
Hello, I would like to make few notes about comming release of DynAPI3. I'm sorry for that I haven't gone trough DynAPI3 code so that I would know wheter these are allready taken count of. These are based on our experience and if any one of you have better knowledge if these issues, I would be happy to know about them. 1) There should be attention paid in to image size/sizing issues in DynAPI3. (At least in DynAPI2 there were several problems related in it.) Netscape 6/7 and Opera browsers are able to find out image dimensions only after the whole document is loaded. There for DynAPI should employ mechanism which prevents image size queries before document is loaded on these browsers. Exspecially DynAPI core shouldn't rely on image dimensions before document is fully loaded. 2) The Javascript engine of Netscape is very slow on what comes to events. Special atention should be paid in to performance issues in Netscape browsers (more shortcuts / performance tweaks?). Exspecially dragging is a problem in Netscape. Jukka suggested that it might be good idea to consider different approaches to click events and drag events in Netscape (simplified drag module for Netscape?). 3) In Netscape 4 loading is the hardest issue. Fairly badly documented feature describes that Netscape 4 can have only one layer open for loading at the time. Other layers have to be closed before loading stuff in to other layer (note that Netscape doesn't close layer automaticly). If something is tried to load in to layer when other layer is open Netscape crashes. This suggests that some sort of loader is needed (based on our testes, in some browsers onLoad detection is not 100% acurate). 4) Opera 5 is very slooooooow... it may affect in to some script functionality. 5) Definition of looks should be made with styles when ever possible. Style definitions should be done based on DOM standard. Which means that widht equals in to width of content area. Borders are excluded from this width (this behavior differes from DynAPI2 approach). Following browsers use DOM standard in a way described earlier (others need to be fixed "manually" in dynapi): Opera from version 6 on, Netscape from version 6 on, MSIE from version 5 on machintosh platfom and MSIE from version 6 on PC platform. On MSIE6 on PC platfor ther is one catch though. MSIE6 uses DOM behavior only if there is correct doctype definition (=DOM) and link to correct standard in HTML file header. Otherwice it uses old aproach, where borders (for instance) are counted as part of widht. There for there should be (?) some sort of detection for doctype definition in DynAPI. These are the issues, we think that should be dealt with DynAPI3 before betarelease if they aren't dealt allready. I think that we will be able to provide the results of browser compability tests (Excel files, we have tested all the objects and methods separately on each browser) shortly... I will let you know when we are ready with those. - Juho Risku / Helmi Staff http://www.visualway.com/helmi _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail |
From: Doug M. <do...@cr...> - 2003-04-29 03:21:21
|
----- Original Message ----- From: "Raymond Irving" <xw...@ya...> To: "DynAPI-Dev" <dyn...@li...> Sent: Monday, April 28, 2003 6:12 PM Subject: Re: [Dynapi-Dev] set border bug > > --- Doug Melvin <do...@cr...> wrote: > > > > > > It's good for cross-browser, but it's more > > resource > > > intensive. What I think I might do is remove > > > setBorder() from dynlayer_base and create a > > > cross-browser solution inside a bordermanager.js > > file. > > > Agree? > > > > Possibly a good idea as the border issues are > > getting rather complex.. > > also, we will be able to extend the border manager > > for skining and the like > > > > I'll also remove css border support for all browsers > and use layers inside. > Is that necessary? I see no need to cripple the better browsers (slow them down) just becaue one doesn't support css borders.. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.476 / Virus Database: 273 - Release Date: 4/24/2003 |
From: Kevin <ke...@ke...> - 2003-04-29 01:22:01
|
"Raymond Irving" <xw...@ya...> wrote: > > --- Kevin <ke...@ke...> wrote: > > > > "Raymond Irving" <xw...@ya...> wrote: > > > > > > > > --- Kevin <ke...@ke...> wrote: > > > > > > > > We need a good long think about this. I like one > > > > solution > > > > for all. So NS4 design for me, plus the facility > > to > > > > extend > > > > it as Benoit suggests with corners / images is > > good. > > > > > > > > I would suggest one extra center layer so the > > > > content > > > > won't flow under borders or for external > > content. > > > > So: > > > > 1 - frame (relative or absolute container) > > > > 4 - borders (solid or image) > > > > (4 - corners) (solid or image) > > > > 1 - content (html or external) > > > > -- > > > > 10 > > > > -- > > > > Is this too much or just enough for one cross > > > > browser > > > > solution with extension possibilities? > > > > > > It's good for cross-browser, but it's more > > resource > > > intensive. What I think I might do is remove > > > setBorder() from dynlayer_base and create a > > > cross-browser solution inside a bordermanager.js > > file. > > > Agree? > > > > Yes - border layers inside 1 frame layer plus a > > center > > layer comtent. > > Well, for center layer you can enable the Blackboard. > Or user can implement their own. Blackboard doesn't work on all browsers. If we don't offer a center layer as the doc attribute of the layer/div frame, the content will be clipped under the layer borders. Perhaps this can be a simple border widget with external content enabled. The user can implement their own api as I have had to. It's the only way to find out why some dynapi ideas don't work. I'll try and get something working for the getElmWidth/Height or getContentWidth/Height problem and with setClass cross browser. NS4 is a pain if style sheets are used with a <layer> tag, only left,top / width,height can be dynamically changed, bgcolor, z-index and visibility become read-only. So this breaks setBgColor/setZIndex/setVisible :-( This work is taking up a lot of my time at the moment. So sorry for any delay for the June release date. - Kevin > -- > Raymond Irving > > > > - > > Kevin > > > > > -- > > > Raymond Irving > > > > > > > > > > Kevin > > > > > > > > > -- > > > > > Raymond Irving > > > > > > > > > > > I have a setBorder method that fixes the bug > > and > > > > > > should > > > > > > work ok: > > > > > > > > > > > > p.setBorder=function(w,c,s) { > > > > > > var width=w||0; > > > > > > var > > bstyle=(typeof(s)=='string')?s:'solid'; > > > > > > var > > bcolor=(typeof(c)=='string')?c:'black'; > > > > > > this._border=width+'px '+bstyle+' > > '+bcolor; > > > > > > this._cssBorder='border:'+this._border+'; > > '; > > > > > > var s=this.css; > > > > > > if(s) { > > > > > > s.borderWidth=width+'px'; > > > > > > s.borderStyle=bstyle; > > > > > > s.borderColor=bcolor; > > > > > > } > > > > > > }; > > > > > > > > > > > > Just need to work out what the dynlayer w & > > h > > > > should > > > > > > be > > > > > > as the w & h of a dynlayer should be the > > same as > > > > > > when > > > > > > using a border (internal border layers) in > > ns4. > > > > > > > > > > > > - > > > > > > Kevin > > > > > > > > > > > > > > > > > > > > For example in dom browsers we would > > > > something > > > > > > like: > > > > > > > > > > > > > > > > p.setSize = function(w,h) { > > > > > > > > ..... > > > > > > > > if (cw) this.css.width = > > > > > > > > (this.w-(this._border*2))||0; > > > > > > > > if (ch) this.css.height = > > > > > > > > (this.h-(this._border*2))||0; > > > > > > > > .... > > > > > > > > } > > > > > > > > > > > > > > > > > > > > > > > > What do you think? Any other > > suggestions? > > > > Can we > > > > > > do > > > > > > > > this? > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Raymond Irving > > > > > > > > > > > > > > > > > > > > > > > > > > > > __________________________________________________ > > > > > > > > Do you Yahoo!? > > > > > > > > The New Yahoo! Search - Faster. Easier. > > > > Bingo > > > > > > > > http://search.yahoo.com > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > > > This sf.net email is sponsored > > by:ThinkGeek > > > > > > > > Welcome to geek heaven. > > > > > > > > http://thinkgeek.com/sf > > > > > > > > > > > > _______________________________________________ > > > > > > > > Dynapi-Dev mailing list > > > > > > > > Dyn...@li... > > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > > > -- > > > > > > > Dan Willemsen <da...@wi...> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > > This sf.net email is sponsored > > by:ThinkGeek > > > > > > > Welcome to geek heaven. > > > > > > > http://thinkgeek.com/sf > > > > > > > > > > > _______________________________________________ > > > > > > > Dynapi-Dev mailing list > > > > > > > Dyn...@li... > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > This sf.net email is sponsored by:ThinkGeek > > > > > > Welcome to geek heaven. > > > > > > http://thinkgeek.com/sf > > > > > > > > _______________________________________________ > > > > > > Dynapi-Dev mailing list > > > > > > Dyn...@li... > > > > > > > > > > > > > > > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > > > === message truncated === > > > > > > > > > __________________________________ > > > Do you Yahoo!? > > > The New Yahoo! Search - Faster. Easier. Bingo. > > > http://search.yahoo.com > > > > > > > > > > > > ------------------------------------------------------- > > > === message truncated === > > > __________________________________ > Do you Yahoo!? > The New Yahoo! Search - Faster. Easier. Bingo. > http://search.yahoo.com > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://www.mail-archive.com/dyn...@li.../ |
From: Raymond I. <xw...@ya...> - 2003-04-28 22:56:22
|
--- Kevin <ke...@ke...> wrote: > > "Raymond Irving" <xw...@ya...> wrote: > > > > > --- Kevin <ke...@ke...> wrote: > > > > > > We need a good long think about this. I like one > > > solution > > > for all. So NS4 design for me, plus the facility > to > > > extend > > > it as Benoit suggests with corners / images is > good. > > > > > > I would suggest one extra center layer so the > > > content > > > won't flow under borders or for external > content. > > > So: > > > 1 - frame (relative or absolute container) > > > 4 - borders (solid or image) > > > (4 - corners) (solid or image) > > > 1 - content (html or external) > > > -- > > > 10 > > > -- > > > Is this too much or just enough for one cross > > > browser > > > solution with extension possibilities? > > > > It's good for cross-browser, but it's more > resource > > intensive. What I think I might do is remove > > setBorder() from dynlayer_base and create a > > cross-browser solution inside a bordermanager.js > file. > > Agree? > > Yes - border layers inside 1 frame layer plus a > center > layer comtent. Well, for center layer you can enable the Blackboard. Or user can implement their own. -- Raymond Irving > - > Kevin > > > -- > > Raymond Irving > > > > > > > Kevin > > > > > > > -- > > > > Raymond Irving > > > > > > > > > I have a setBorder method that fixes the bug > and > > > > > should > > > > > work ok: > > > > > > > > > > p.setBorder=function(w,c,s) { > > > > > var width=w||0; > > > > > var > bstyle=(typeof(s)=='string')?s:'solid'; > > > > > var > bcolor=(typeof(c)=='string')?c:'black'; > > > > > this._border=width+'px '+bstyle+' > '+bcolor; > > > > > this._cssBorder='border:'+this._border+'; > '; > > > > > var s=this.css; > > > > > if(s) { > > > > > s.borderWidth=width+'px'; > > > > > s.borderStyle=bstyle; > > > > > s.borderColor=bcolor; > > > > > } > > > > > }; > > > > > > > > > > Just need to work out what the dynlayer w & > h > > > should > > > > > be > > > > > as the w & h of a dynlayer should be the > same as > > > > > when > > > > > using a border (internal border layers) in > ns4. > > > > > > > > > > - > > > > > Kevin > > > > > > > > > > > > > > > > > For example in dom browsers we would > > > something > > > > > like: > > > > > > > > > > > > > > p.setSize = function(w,h) { > > > > > > > ..... > > > > > > > if (cw) this.css.width = > > > > > > > (this.w-(this._border*2))||0; > > > > > > > if (ch) this.css.height = > > > > > > > (this.h-(this._border*2))||0; > > > > > > > .... > > > > > > > } > > > > > > > > > > > > > > > > > > > > > What do you think? Any other > suggestions? > > > Can we > > > > > do > > > > > > > this? > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Raymond Irving > > > > > > > > > > > > > > > > > > > > > > > __________________________________________________ > > > > > > > Do you Yahoo!? > > > > > > > The New Yahoo! Search - Faster. Easier. > > > Bingo > > > > > > > http://search.yahoo.com > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > > This sf.net email is sponsored > by:ThinkGeek > > > > > > > Welcome to geek heaven. > > > > > > > http://thinkgeek.com/sf > > > > > > > > > > _______________________________________________ > > > > > > > Dynapi-Dev mailing list > > > > > > > Dyn...@li... > > > > > > > > > > > > > > > > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > > -- > > > > > > Dan Willemsen <da...@wi...> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > This sf.net email is sponsored > by:ThinkGeek > > > > > > Welcome to geek heaven. > > > > > > http://thinkgeek.com/sf > > > > > > > > > _______________________________________________ > > > > > > Dynapi-Dev mailing list > > > > > > Dyn...@li... > > > > > > > > > > > > > > > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > This sf.net email is sponsored by:ThinkGeek > > > > > Welcome to geek heaven. > > > > > http://thinkgeek.com/sf > > > > > > _______________________________________________ > > > > > Dynapi-Dev mailing list > > > > > Dyn...@li... > > > > > > > > > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > === message truncated === > > > > > > __________________________________ > > Do you Yahoo!? > > The New Yahoo! Search - Faster. Easier. Bingo. > > http://search.yahoo.com > > > > > > > ------------------------------------------------------- > === message truncated === __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com |
From: Kevin <ke...@ke...> - 2003-04-28 22:30:09
|
"Raymond Irving" <xw...@ya...> wrote: > > --- Kevin <ke...@ke...> wrote: > > > > We need a good long think about this. I like one > > solution > > for all. So NS4 design for me, plus the facility to > > extend > > it as Benoit suggests with corners / images is good. > > > > I would suggest one extra center layer so the > > content > > won't flow under borders or for external content. > > So: > > 1 - frame (relative or absolute container) > > 4 - borders (solid or image) > > (4 - corners) (solid or image) > > 1 - content (html or external) > > -- > > 10 > > -- > > Is this too much or just enough for one cross > > browser > > solution with extension possibilities? > > It's good for cross-browser, but it's more resource > intensive. What I think I might do is remove > setBorder() from dynlayer_base and create a > cross-browser solution inside a bordermanager.js file. > Agree? Yes - border layers inside 1 frame layer plus a center layer comtent. - Kevin > -- > Raymond Irving > > > > Kevin > > > > > -- > > > Raymond Irving > > > > > > > I have a setBorder method that fixes the bug and > > > > should > > > > work ok: > > > > > > > > p.setBorder=function(w,c,s) { > > > > var width=w||0; > > > > var bstyle=(typeof(s)=='string')?s:'solid'; > > > > var bcolor=(typeof(c)=='string')?c:'black'; > > > > this._border=width+'px '+bstyle+' '+bcolor; > > > > this._cssBorder='border:'+this._border+'; '; > > > > var s=this.css; > > > > if(s) { > > > > s.borderWidth=width+'px'; > > > > s.borderStyle=bstyle; > > > > s.borderColor=bcolor; > > > > } > > > > }; > > > > > > > > Just need to work out what the dynlayer w & h > > should > > > > be > > > > as the w & h of a dynlayer should be the same as > > > > when > > > > using a border (internal border layers) in ns4. > > > > > > > > - > > > > Kevin > > > > > > > > > > > > > > For example in dom browsers we would > > something > > > > like: > > > > > > > > > > > > p.setSize = function(w,h) { > > > > > > ..... > > > > > > if (cw) this.css.width = > > > > > > (this.w-(this._border*2))||0; > > > > > > if (ch) this.css.height = > > > > > > (this.h-(this._border*2))||0; > > > > > > .... > > > > > > } > > > > > > > > > > > > > > > > > > What do you think? Any other suggestions? > > Can we > > > > do > > > > > > this? > > > > > > > > > > > > > > > > > > -- > > > > > > Raymond Irving > > > > > > > > > > > > > > > > > > __________________________________________________ > > > > > > Do you Yahoo!? > > > > > > The New Yahoo! Search - Faster. Easier. > > Bingo > > > > > > http://search.yahoo.com > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > This sf.net email is sponsored by:ThinkGeek > > > > > > Welcome to geek heaven. > > > > > > http://thinkgeek.com/sf > > > > > > > > _______________________________________________ > > > > > > Dynapi-Dev mailing list > > > > > > Dyn...@li... > > > > > > > > > > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > -- > > > > > Dan Willemsen <da...@wi...> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > This sf.net email is sponsored by:ThinkGeek > > > > > Welcome to geek heaven. > > > > > http://thinkgeek.com/sf > > > > > > > _______________________________________________ > > > > > Dynapi-Dev mailing list > > > > > Dyn...@li... > > > > > > > > > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > This sf.net email is sponsored by:ThinkGeek > > > > Welcome to geek heaven. > > > > http://thinkgeek.com/sf > > > > _______________________________________________ > > > > Dynapi-Dev mailing list > > > > Dyn...@li... > > > > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > === message truncated === > > > __________________________________ > Do you Yahoo!? > The New Yahoo! Search - Faster. Easier. Bingo. > http://search.yahoo.com > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://www.mail-archive.com/dyn...@li.../ |
From: Raymond I. <xw...@ya...> - 2003-04-28 22:12:15
|
--- Doug Melvin <do...@cr...> wrote: > > > > It's good for cross-browser, but it's more > resource > > intensive. What I think I might do is remove > > setBorder() from dynlayer_base and create a > > cross-browser solution inside a bordermanager.js > file. > > Agree? > > Possibly a good idea as the border issues are > getting rather complex.. > also, we will be able to extend the border manager > for skining and the like > I'll also remove css border support for all browsers and use layers inside. -- Raymond Irving > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system > (http://www.grisoft.com). > Version: 6.0.476 / Virus Database: 273 - Release > Date: 4/24/03 __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com |
From: Doug M. <do...@cr...> - 2003-04-28 21:58:20
|
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.476 / Virus Database: 273 - Release Date: 4/24/03 |
From: Raymond I. <xw...@ya...> - 2003-04-28 20:25:29
|
--- Kevin <ke...@ke...> wrote: >.... > In the above the dynLayer width/height will always > be > > 100x100 although the actual elm size will be > 98x98. > > This IMO shouldn't be a problem as the content > inside > > the elm will either wrap or overflow. This will > only > > be true when borders are set for DynLayers on DOM > > browsers. > > Would we have to 'adjust' the dlyr x/y? No, I don't see were we will need to do that. >... What are the > coords of relative elements or when constructing a > widget and bordered elements need to touch? > > > Agree? Or should we use the NS4 design despite the > > draw backs or having to use four additional > layers? > > We need a good long think about this. I like one > solution > for all. So NS4 design for me, plus the facility to > extend > it as Benoit suggests with corners / images is good. > > I would suggest one extra center layer so the > content > won't flow under borders or for external content. > So: > 1 - frame (relative or absolute container) > 4 - borders (solid or image) > (4 - corners) (solid or image) > 1 - content (html or external) > -- > 10 > -- > Is this too much or just enough for one cross > browser > solution with extension possibilities? It's good for cross-browser, but it's more resource intensive. What I think I might do is remove setBorder() from dynlayer_base and create a cross-browser solution inside a bordermanager.js file. Agree? -- Raymond Irving > Kevin > > > -- > > Raymond Irving > > > > > I have a setBorder method that fixes the bug and > > > should > > > work ok: > > > > > > p.setBorder=function(w,c,s) { > > > var width=w||0; > > > var bstyle=(typeof(s)=='string')?s:'solid'; > > > var bcolor=(typeof(c)=='string')?c:'black'; > > > this._border=width+'px '+bstyle+' '+bcolor; > > > this._cssBorder='border:'+this._border+'; '; > > > var s=this.css; > > > if(s) { > > > s.borderWidth=width+'px'; > > > s.borderStyle=bstyle; > > > s.borderColor=bcolor; > > > } > > > }; > > > > > > Just need to work out what the dynlayer w & h > should > > > be > > > as the w & h of a dynlayer should be the same as > > > when > > > using a border (internal border layers) in ns4. > > > > > > - > > > Kevin > > > > > > > > > > > For example in dom browsers we would > something > > > like: > > > > > > > > > > p.setSize = function(w,h) { > > > > > ..... > > > > > if (cw) this.css.width = > > > > > (this.w-(this._border*2))||0; > > > > > if (ch) this.css.height = > > > > > (this.h-(this._border*2))||0; > > > > > .... > > > > > } > > > > > > > > > > > > > > > What do you think? Any other suggestions? > Can we > > > do > > > > > this? > > > > > > > > > > > > > > > -- > > > > > Raymond Irving > > > > > > > > > > > > > > __________________________________________________ > > > > > Do you Yahoo!? > > > > > The New Yahoo! Search - Faster. Easier. > Bingo > > > > > http://search.yahoo.com > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > This sf.net email is sponsored by:ThinkGeek > > > > > Welcome to geek heaven. > > > > > http://thinkgeek.com/sf > > > > > > _______________________________________________ > > > > > Dynapi-Dev mailing list > > > > > Dyn...@li... > > > > > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > -- > > > > Dan Willemsen <da...@wi...> > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > This sf.net email is sponsored by:ThinkGeek > > > > Welcome to geek heaven. > > > > http://thinkgeek.com/sf > > > > > _______________________________________________ > > > > Dynapi-Dev mailing list > > > > Dyn...@li... > > > > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This sf.net email is sponsored by:ThinkGeek > > > Welcome to geek heaven. > > > http://thinkgeek.com/sf > > > _______________________________________________ > > > Dynapi-Dev mailing list > > > Dyn...@li... > > > > > > http://www.mail-archive.com/dyn...@li.../ > === message truncated === __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com |
From: Raymond I. <xw...@ya...> - 2003-04-28 20:16:07
|
--- Kevin <ke...@ke...> wrote: > > "Raymond Irving" <xw...@ya...> wrote: > > > Kevin, > > > > Proposed DynLayer functions for use within > > assignElement(): > > > > p.getElmWidth = function(){ > > var w = parseInt(this.css.width); > > if(isNaN(w)) w=this.getContentWidth(); > > return w; > > }; > > p.getElmHeight = function(){ > > var h = parseInt(this.css.height); > > if(isNaN(h)) h=this.getContentWidth(); > > return h; > > }; > > Not sure if it will work. Is getContentWidth/Height > ever called and on what browsers did you see this? Whenever w==null and h==null then getContenWidth/Height is called to set the size of the layer. > I had come up with a cross browser version: > > p.getElmWidth=function() { > var r=this.elm, s=this.css; > if(r) { s=s.clip||s; return > s.width||r.offsetWidth; } > else return null; > }; > p.getElmHeight=function() { > var r=this.elm, s=this.css; > if(r) { s=s.clip||s; return > s.height||r.offsetHeight; } > else return null; > }; Will the above get the width of the layer when it's defined inside the style sheet? -- Raymond Irving > Unfortunately after HTML has been written the > element has style anyway. So testing for no style > value didn't work for me. We need something else. > Perhaps: > lyr=new DynL:ayer('a',100,100); > setClass('redbg','auto'); > will pull bgColor from the class 'redbg' and 'auto' > to > force getContentWidth/Height() (offsetWidth/Height) > rather than looking at element style (width/height) > which may contain valid size of 'a' or dynlayer size > defined in class 'redbg'. > > - > Kevin > > > while DynLayer._assignElement will now use: > > > > if (dlyr.html!=null && dlyr.html!='' && > (dlyr.w==null > > || dlyr.h==null)) { > > var cw = (dlyr.w==null)? dlyr.getElmWidth() : > null; > > var ch = (dlyr.h==null)? dlyr.getElmHeight() : > null; > > dlyr.setSize(cw,ch); > > } > > > > > > Please run a performance test on this to see if it > is > > ok. > > > > > > Any comments, suggestions? > > > > > > -- > > Raymond Irving > > > > > > --- Kevin <ke...@ke...> wrote: > > > > > > "Raymond Irving" <xw...@ya...> wrote: > > > > > > > > > Hi, > > > > > > > > > > > > > > > When using setClass('whatever',true) you > should > > > always > > > > > create dynlayer with width and height or 0. > This > > > is to > > > > > prevent dynlayer from attempting to autosize > the > > > > > layer. > > > > > > I disagree the w & h should be defaulted to null > in > > > the > > > constructor and not be touched until > _assignElement. > > > > > > > > It was suggested once that we get the width > and > > > the > > > > > height from the style of the layer, but that > > > might not > > > > > be a good thing to do as style sheets can > use > > > > > different values for width and height: > > > > > > > > > > width:100px; height:100px; > > > > > width:100%; height:100%; > > > > > width:100cm; height:100cm; > > > > > > A user/developer knowing that pixels are > supported > > > would use px in style sheets as in the same way > > > lyr=new DynLayer('z',10,10,'100%',100%') > > > wouldn't be expected to work in any case. > > > > > > > > If a layer's style width inside the style > sheet > > > was > > > > > set to 100% then the dynlayer would report > the > > > wrong > > > > > size, correct? > > > > > > > > > > Any thoughts on this? Should we document > that > > > users > > > > > set the width and height to 0,0 when using > style > > > > > sheets? Or should we enable > > > DynLayer.assignElement() > > > > > to first check for a valid css width/height > > > before > > > > > calling getContentWidth/Height? > > > > > > Defaults as explained above. Then in > assignElement: > > > 1) call new methods getElmWidth() & > getElmHeight() > > > to satisfy the style sheet requirement > > > then if the user/developer hasn't specified a > style > > > object > > > or class > > > 2) call getContentWidth() & getContentHeight() > to > > > satisfy > > > the auto size requirement (single character > > > DynLayers etc) > > > > > > - > > > Kevin. > > > > > > > > > > > > > -- > > > > > Raymond Irving > > > > > > > > > > > > > > __________________________________________________ > > > > > Do you Yahoo!? > > > > > The New Yahoo! Search - Faster. Easier. > Bingo > > > > > http://search.yahoo.com > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > This sf.net email is sponsored by:ThinkGeek > > > > > Welcome to geek heaven. > > > > > http://thinkgeek.com/sf > > > > > > _______________________________________________ > > > > > Dynapi-Dev mailing list > > > > > Dyn...@li... > > > > > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This sf.net email is sponsored by:ThinkGeek > > > Welcome to geek heaven. > > > http://thinkgeek.com/sf > > > _______________________________________________ > > > Dynapi-Dev mailing list > > > Dyn...@li... > > > > > > http://www.mail-archive.com/dyn...@li.../ > === message truncated === __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com |
From: Kevin <ke...@ke...> - 2003-04-28 19:39:21
|
"Raymond Irving" <xw...@ya...> wrote: > Kevin, > > Proposed DynLayer functions for use within > assignElement(): > > p.getElmWidth = function(){ > var w = parseInt(this.css.width); > if(isNaN(w)) w=this.getContentWidth(); > return w; > }; > p.getElmHeight = function(){ > var h = parseInt(this.css.height); > if(isNaN(h)) h=this.getContentWidth(); > return h; > }; Not sure if it will work. Is getContentWidth/Height ever called and on what browsers did you see this? I had come up with a cross browser version: p.getElmWidth=function() { var r=this.elm, s=this.css; if(r) { s=s.clip||s; return s.width||r.offsetWidth; } else return null; }; p.getElmHeight=function() { var r=this.elm, s=this.css; if(r) { s=s.clip||s; return s.height||r.offsetHeight; } else return null; }; Unfortunately after HTML has been written the element has style anyway. So testing for no style value didn't work for me. We need something else. Perhaps: lyr=new DynL:ayer('a',100,100); setClass('redbg','auto'); will pull bgColor from the class 'redbg' and 'auto' to force getContentWidth/Height() (offsetWidth/Height) rather than looking at element style (width/height) which may contain valid size of 'a' or dynlayer size defined in class 'redbg'. - Kevin > while DynLayer._assignElement will now use: > > if (dlyr.html!=null && dlyr.html!='' && (dlyr.w==null > || dlyr.h==null)) { > var cw = (dlyr.w==null)? dlyr.getElmWidth() : null; > var ch = (dlyr.h==null)? dlyr.getElmHeight() : null; > dlyr.setSize(cw,ch); > } > > > Please run a performance test on this to see if it is > ok. > > > Any comments, suggestions? > > > -- > Raymond Irving > > > --- Kevin <ke...@ke...> wrote: > > > > "Raymond Irving" <xw...@ya...> wrote: > > > > > > > Hi, > > > > > > > > > > > > When using setClass('whatever',true) you should > > always > > > > create dynlayer with width and height or 0. This > > is to > > > > prevent dynlayer from attempting to autosize the > > > > layer. > > > > I disagree the w & h should be defaulted to null in > > the > > constructor and not be touched until _assignElement. > > > > > > It was suggested once that we get the width and > > the > > > > height from the style of the layer, but that > > might not > > > > be a good thing to do as style sheets can use > > > > different values for width and height: > > > > > > > > width:100px; height:100px; > > > > width:100%; height:100%; > > > > width:100cm; height:100cm; > > > > A user/developer knowing that pixels are supported > > would use px in style sheets as in the same way > > lyr=new DynLayer('z',10,10,'100%',100%') > > wouldn't be expected to work in any case. > > > > > > If a layer's style width inside the style sheet > > was > > > > set to 100% then the dynlayer would report the > > wrong > > > > size, correct? > > > > > > > > Any thoughts on this? Should we document that > > users > > > > set the width and height to 0,0 when using style > > > > sheets? Or should we enable > > DynLayer.assignElement() > > > > to first check for a valid css width/height > > before > > > > calling getContentWidth/Height? > > > > Defaults as explained above. Then in assignElement: > > 1) call new methods getElmWidth() & getElmHeight() > > to satisfy the style sheet requirement > > then if the user/developer hasn't specified a style > > object > > or class > > 2) call getContentWidth() & getContentHeight() to > > satisfy > > the auto size requirement (single character > > DynLayers etc) > > > > - > > Kevin. > > > > > > > > > > -- > > > > Raymond Irving > > > > > > > > > > __________________________________________________ > > > > Do you Yahoo!? > > > > The New Yahoo! Search - Faster. Easier. Bingo > > > > http://search.yahoo.com > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > This sf.net email is sponsored by:ThinkGeek > > > > Welcome to geek heaven. > > > > http://thinkgeek.com/sf > > > > _______________________________________________ > > > > Dynapi-Dev mailing list > > > > Dyn...@li... > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > > http://www.mail-archive.com/dyn...@li.../ > > > __________________________________ > Do you Yahoo!? > The New Yahoo! Search - Faster. Easier. Bingo. > http://search.yahoo.com > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://www.mail-archive.com/dyn...@li.../ |
From: Kevin <ke...@ke...> - 2003-04-28 19:39:13
|
Fw: to Dynapi-Dev: ----- Original Message ----- From: "Kevin" <ke...@ke...> To: "Raymond Irving" <xw...@ya...> Sent: Monday, April 28, 2003 6:58 PM Subject: Re: [Dynapi-Dev] set border bug > "Raymond Irving" <xw...@ya...> wrote: > > > > > --- Kevin <ke...@ke...> wrote: > > > Solution. > > > > > > 1) I like the way borders are done in dynapi for > > > ns4. Layers for top, > > > bottom, left and right. So if we implement this for > > > all browsers and > > > not mess with the style it would be consistent, > > > though dynlayer width > > > will include border. > > > > That's true, but this would require us to us more > > layers. The solution is ok for ns4 (as it's an old > > browser) but css now available I think it's much more > > efficient to use css. > > > > > 2) If we mess with border style for dom browsers. > > > For the > > > dynlayer size to consistent with ns4 border > > > implementation > > > it''s the dynlayer width that should be set to the > > > actual element > > > width plus twice the size of the border. > > > > If we set the actual elm size to be less than twice > > the border size then it would be consistent with the > > ns4 implementation: > > > > lyr.w = 100 > > lyr.h = 100 > > lyr.css.width=(lyr.w-(lyr._border*2)) > > lyr.css.height=(lyr.h-(lyr._border*2)) > > The effect will be different in IE5 and IE5.5 and maybe > other browsers. > > > In the above the dynLayer width/height will always be > > 100x100 although the actual elm size will be 98x98. > > This IMO shouldn't be a problem as the content inside > > the elm will either wrap or overflow. This will only > > be true when borders are set for DynLayers on DOM > > browsers. > > Would we have to 'adjust' the dlyr x/y? What are the > coords of relative elements or when constructing a > widget and bordered elements need to touch? > > > Agree? Or should we use the NS4 design despite the > > draw backs or having to use four additional layers? > > We need a good long think about this. I like one solution > for all. So NS4 design for me, plus the facility to extend > it as Benoit suggests with corners / images is good. > > I would suggest one extra center layer so the content > won't flow under borders or for external content. So: > 1 - frame (relative or absolute container) > 4 - borders (solid or image) > (4 - corners) (solid or image) > 1 - content (html or external) > -- > 10 > -- > Is this too much or just enough for one cross browser > solution with extension possibilities? > > Kevin > > > -- > > Raymond Irving > > > > > I have a setBorder method that fixes the bug and > > > should > > > work ok: > > > > > > p.setBorder=function(w,c,s) { > > > var width=w||0; > > > var bstyle=(typeof(s)=='string')?s:'solid'; > > > var bcolor=(typeof(c)=='string')?c:'black'; > > > this._border=width+'px '+bstyle+' '+bcolor; > > > this._cssBorder='border:'+this._border+'; '; > > > var s=this.css; > > > if(s) { > > > s.borderWidth=width+'px'; > > > s.borderStyle=bstyle; > > > s.borderColor=bcolor; > > > } > > > }; > > > > > > Just need to work out what the dynlayer w & h should > > > be > > > as the w & h of a dynlayer should be the same as > > > when > > > using a border (internal border layers) in ns4. > > > > > > - > > > Kevin > > > > > > > > > > > For example in dom browsers we would something > > > like: > > > > > > > > > > p.setSize = function(w,h) { > > > > > ..... > > > > > if (cw) this.css.width = > > > > > (this.w-(this._border*2))||0; > > > > > if (ch) this.css.height = > > > > > (this.h-(this._border*2))||0; > > > > > .... > > > > > } > > > > > > > > > > > > > > > What do you think? Any other suggestions? Can we > > > do > > > > > this? > > > > > > > > > > > > > > > -- > > > > > Raymond Irving > > > > > > > > > > > > > __________________________________________________ > > > > > Do you Yahoo!? > > > > > The New Yahoo! Search - Faster. Easier. Bingo > > > > > http://search.yahoo.com > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > This sf.net email is sponsored by:ThinkGeek > > > > > Welcome to geek heaven. > > > > > http://thinkgeek.com/sf > > > > > _______________________________________________ > > > > > Dynapi-Dev mailing list > > > > > Dyn...@li... > > > > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > -- > > > > Dan Willemsen <da...@wi...> > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > This sf.net email is sponsored by:ThinkGeek > > > > Welcome to geek heaven. > > > > http://thinkgeek.com/sf > > > > _______________________________________________ > > > > Dynapi-Dev mailing list > > > > Dyn...@li... > > > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > > > > > > > > > > ------------------------------------------------------- > > > This sf.net email is sponsored by:ThinkGeek > > > Welcome to geek heaven. > > > http://thinkgeek.com/sf > > > _______________________________________________ > > > Dynapi-Dev mailing list > > > Dyn...@li... > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > > __________________________________ > > Do you Yahoo!? > > The New Yahoo! Search - Faster. Easier. Bingo. > > http://search.yahoo.com > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > http://www.mail-archive.com/dyn...@li.../ > |
From: Kevin <ke...@ke...> - 2003-04-28 19:37:37
|
Fw: to Dynapi-Dev: ----- Original Message ----- From: "Kevin" <ke...@ke...> To: "Doug Melvin" <do...@cr...> Sent: Monday, April 28, 2003 7:29 PM Subject: Re: [Dynapi-Dev] set border bug > "Doug Melvin" <do...@cr...> wrote: > > > I say use CSS where we can. > > A point tho: I have yet to force mozilla to paint the right and bottom > > borders.. > > It may not behave the same in IE5 IE5.5. I posted a setBorder method > to the list that seemed to work in Moz'. Though check first what style > getOuterHTML gives as this has come from my mini api. > > p.setBorder=function(w,c,s) { > var width=w||0; > var bstyle=(typeof(s)=='string')?s:'solid'; > var bcolor=(typeof(c)=='string')?c:'black'; > this._border=width+'px '+bstyle+' '+bcolor; > this._cssBorder='border:'+this._border+'; '; > var s=this.css; > if(s) { > s.borderWidth=width+'px'; > s.borderStyle=bstyle; > s.borderColor=bcolor; > } > }; > > Kevin > > > I'll post an example shortly > > ----- Original Message ----- > > From: "Raymond Irving" <xw...@ya...> > > To: "Dynapi-Dev" <Dyn...@li...> > > Sent: Sunday, April 27, 2003 1:39 PM > > Subject: Re: [Dynapi-Dev] set border bug > > > > > > > > > > --- Kevin <ke...@ke...> wrote: > > > > Solution. > > > > > > > > 1) I like the way borders are done in dynapi for > > > > ns4. Layers for top, > > > > bottom, left and right. So if we implement this for > > > > all browsers and > > > > not mess with the style it would be consistent, > > > > though dynlayer width > > > > will include border. > > > > > > That's true, but this would require us to us more > > > layers. The solution is ok for ns4 (as it's an old > > > browser) but css now available I think it's much more > > > efficient to use css. > > > > > > > 2) If we mess with border style for dom browsers. > > > > For the > > > > dynlayer size to consistent with ns4 border > > > > implementation > > > > it''s the dynlayer width that should be set to the > > > > actual element > > > > width plus twice the size of the border. > > > > > > If we set the actual elm size to be less than twice > > > the border size then it would be consistent with the > > > ns4 implementation: > > > > > > lyr.w = 100 > > > lyr.h = 100 > > > lyr.css.width=(lyr.w-(lyr._border*2)) > > > lyr.css.height=(lyr.h-(lyr._border*2)) > > > > > > In the above the dynLayer width/height will always be > > > 100x100 although the actual elm size will be 98x98. > > > This IMO shouldn't be a problem as the content inside > > > the elm will either wrap or overflow. This will only > > > be true when borders are set for DynLayers on DOM > > > browsers. > > > > > > Agree? Or should we use the NS4 design despite the > > > draw backs or having to use four additional layers? > > > > > > -- > > > Raymond Irving > > > > > > > I have a setBorder method that fixes the bug and > > > > should > > > > work ok: > > > > > > > > p.setBorder=function(w,c,s) { > > > > var width=w||0; > > > > var bstyle=(typeof(s)=='string')?s:'solid'; > > > > var bcolor=(typeof(c)=='string')?c:'black'; > > > > this._border=width+'px '+bstyle+' '+bcolor; > > > > this._cssBorder='border:'+this._border+'; '; > > > > var s=this.css; > > > > if(s) { > > > > s.borderWidth=width+'px'; > > > > s.borderStyle=bstyle; > > > > s.borderColor=bcolor; > > > > } > > > > }; > > > > > > > > Just need to work out what the dynlayer w & h should > > > > be > > > > as the w & h of a dynlayer should be the same as > > > > when > > > > using a border (internal border layers) in ns4. > > > > > > > > - > > > > Kevin > > > > > > > > > > > > > > For example in dom browsers we would something > > > > like: > > > > > > > > > > > > p.setSize = function(w,h) { > > > > > > ..... > > > > > > if (cw) this.css.width = > > > > > > (this.w-(this._border*2))||0; > > > > > > if (ch) this.css.height = > > > > > > (this.h-(this._border*2))||0; > > > > > > .... > > > > > > } > > > > > > > > > > > > > > > > > > What do you think? Any other suggestions? Can we > > > > do > > > > > > this? > > > > > > > > > > > > > > > > > > -- > > > > > > Raymond Irving > > > > > > > > > > > > > > > > __________________________________________________ > > > > > > Do you Yahoo!? > > > > > > The New Yahoo! Search - Faster. Easier. Bingo > > > > > > http://search.yahoo.com > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > This sf.net email is sponsored by:ThinkGeek > > > > > > Welcome to geek heaven. > > > > > > http://thinkgeek.com/sf > > > > > > _______________________________________________ > > > > > > Dynapi-Dev mailing list > > > > > > Dyn...@li... > > > > > > > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > -- > > > > > Dan Willemsen <da...@wi...> > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > This sf.net email is sponsored by:ThinkGeek > > > > > Welcome to geek heaven. > > > > > http://thinkgeek.com/sf > > > > > _______________________________________________ > > > > > Dynapi-Dev mailing list > > > > > Dyn...@li... > > > > > > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > This sf.net email is sponsored by:ThinkGeek > > > > Welcome to geek heaven. > > > > http://thinkgeek.com/sf > > > > _______________________________________________ > > > > Dynapi-Dev mailing list > > > > Dyn...@li... > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > > > > > __________________________________ > > > Do you Yahoo!? > > > The New Yahoo! Search - Faster. Easier. Bingo. > > > http://search.yahoo.com > > > > > > > > > ------------------------------------------------------- > > > This sf.net email is sponsored by:ThinkGeek > > > Welcome to geek heaven. > > > http://thinkgeek.com/sf > > > _______________________________________________ > > > Dynapi-Dev mailing list > > > Dyn...@li... > > > http://www.mail-archive.com/dyn...@li.../ > > > > > > > > > --- > > Outgoing mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.476 / Virus Database: 273 - Release Date: 4/24/2003 > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > http://www.mail-archive.com/dyn...@li.../ > |
From: Doug M. <do...@cr...> - 2003-04-28 18:14:46
|
sounds good to me ----- Original Message ----- From: "Raymond Irving" <xw...@ya...> To: "Dynapi-Dev" <Dyn...@li...> Sent: Monday, April 28, 2003 10:34 AM Subject: Re: [Dynapi-Dev] DynLayer and setClass() > > --- Doug Melvin <do...@cr...> wrote: > > what is this for? > > This will allow DynAPI to set the width/height of the > layer if its was defined via a style sheet. > > For example, lyr.setClass('myclass',true) will cause > dynapi to use "myclass" to setup the css properties > for the DynLayer. > > If no css width/height were defined in the style sheet > then the content width/height will be used as the > dynlayer's width/height. > > > -- > Raymond Irving > > > ----- Original Message ----- > > From: "Raymond Irving" <xw...@ya...> > > To: "Dynapi-Dev" <Dyn...@li...> > > Sent: Sunday, April 27, 2003 11:10 PM > > Subject: Re: [Dynapi-Dev] DynLayer and setClass() > > > > > > > Kevin, > > > > > > Proposed DynLayer functions for use within > > > assignElement(): > > > > > > p.getElmWidth = function(){ > > > var w = parseInt(this.css.width); > > > if(isNaN(w)) w=this.getContentWidth(); > > > return w; > > > }; > > > p.getElmHeight = function(){ > > > var h = parseInt(this.css.height); > > > if(isNaN(h)) h=this.getContentWidth(); > > > return h; > > > }; > > > > > > while DynLayer._assignElement will now use: > > > > > > if (dlyr.html!=null && dlyr.html!='' && > > (dlyr.w==null > > > || dlyr.h==null)) { > > > var cw = (dlyr.w==null)? dlyr.getElmWidth() : > > null; > > > var ch = (dlyr.h==null)? dlyr.getElmHeight() : > > null; > > > dlyr.setSize(cw,ch); > > > } > > > > > > > > > Please run a performance test on this to see if it > > is > > > ok. > > > > > > > > > Any comments, suggestions? > > > > > > > > > -- > > > Raymond Irving > > > > > > > > > --- Kevin <ke...@ke...> wrote: > > > > > > > > "Raymond Irving" <xw...@ya...> wrote: > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > When using setClass('whatever',true) you > > should > > > > always > > > > > > create dynlayer with width and height or 0. > > This > > > > is to > > > > > > prevent dynlayer from attempting to autosize > > the > > > > > > layer. > > > > > > > > I disagree the w & h should be defaulted to null > > in > > > > the > > > > constructor and not be touched until > > _assignElement. > > > > > > > > > > It was suggested once that we get the width > > and > > > > the > > > > > > height from the style of the layer, but that > > > > might not > > > > > > be a good thing to do as style sheets can > > use > > > > > > different values for width and height: > > > > > > > > > > > > width:100px; height:100px; > > > > > > width:100%; height:100%; > > > > > > width:100cm; height:100cm; > > > > > > > > A user/developer knowing that pixels are > > supported > > > > would use px in style sheets as in the same way > > > > lyr=new DynLayer('z',10,10,'100%',100%') > > > > wouldn't be expected to work in any case. > > > > > > > > > > If a layer's style width inside the style > > sheet > > > > was > > > > > > set to 100% then the dynlayer would report > > the > > > > wrong > > > > > > size, correct? > > > > > > > > > > > > Any thoughts on this? Should we document > > that > > > > users > > > > > > set the width and height to 0,0 when using > > style > > > > > > sheets? Or should we enable > > > > DynLayer.assignElement() > > > > > > to first check for a valid css width/height > > > > before > > > > > > calling getContentWidth/Height? > > > > > > > > Defaults as explained above. Then in > > assignElement: > > > > 1) call new methods getElmWidth() & > > getElmHeight() > > > > to satisfy the style sheet requirement > > > > then if the user/developer hasn't specified a > > style > > > > object > > > > or class > > > > 2) call getContentWidth() & getContentHeight() > > to > > > > satisfy > > > > the auto size requirement (single character > > > > DynLayers etc) > > > > > > > > - > > > > Kevin. > > > > > > > > > > > > > > > > -- > > > > > > Raymond Irving > > > > > > > > > > > > > > > > > > __________________________________________________ > > > > > > Do you Yahoo!? > > > > > > The New Yahoo! Search - Faster. Easier. > > Bingo > > > > > > http://search.yahoo.com > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > This sf.net email is sponsored by:ThinkGeek > > > > > > Welcome to geek heaven. > > > > > > http://thinkgeek.com/sf > > > > > > > > _______________________________________________ > > > > > > Dynapi-Dev mailing list > > > > > > Dyn...@li... > > > > > > > > > > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > This sf.net email is sponsored by:ThinkGeek > > > > Welcome to geek heaven. > > > > http://thinkgeek.com/sf > > > > _______________________________________________ > > > > Dynapi-Dev mailing list > > > > Dyn...@li... > > > > > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > > > > > __________________________________ > > > Do you Yahoo!? > > > The New Yahoo! Search - Faster. Easier. Bingo. > > > http://search.yahoo.com > > > > > > > > > > > > ------------------------------------------------------- > > > This sf.net email is sponsored by:ThinkGeek > > > Welcome to geek heaven. > > > http://thinkgeek.com/sf > > > _______________________________________________ > > > Dynapi-Dev mailing list > > > Dyn...@li... > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > > > > > --- > > Outgoing mail is certified Virus Free. > > Checked by AVG anti-virus system > > (http://www.grisoft.com). > > Version: 6.0.476 / Virus Database: 273 - Release > > Date: 4/24/2003 > > > > > > > === message truncated === > > > __________________________________ > Do you Yahoo!? > The New Yahoo! Search - Faster. Easier. Bingo. > http://search.yahoo.com > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://www.mail-archive.com/dyn...@li.../ > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.476 / Virus Database: 273 - Release Date: 4/24/03 |
From: Raymond I. <xw...@ya...> - 2003-04-28 17:32:25
|
--- Mahidine Mendjeli <mme...@gh...> wrote: > 3.0 > where is the alpha1 ??? You can check it out from cvs -- Raymond Irving > i found the problem, > it's because of the security restriction of IE6 SP1 > which doesn't allowed > to fire an action on 'self.onload' > > MM > > ----- Original Message ----- > From: "Raymond Irving" <xw...@ya...> > To: <dyn...@li...> > Sent: Monday, April 28, 2003 4:29 PM > Subject: Re: [Dynapi-Dev] IE 6 SP1 and Onload event > > > > > > --- Mahidine Mendjeli <mme...@gh...> wrote: > > > It seems IE 6 SP1 doesn't allow the possibility > to > > > fire an event when > > > the page is loaded!!! > > > so there is no possibility to create a Layer! > > > Does someone experimented this problem? > > > > What version of DynAPI are you using? This problem > > should have been fixed in 3.0 alpha 1 > > > > -- > > Raymond Irving > > > > > MM > > > > > > ----- Original Message ----- > > > From: <dyn...@li...> > > > To: <dyn...@li...> > > > Sent: Saturday, April 26, 2003 7:17 PM > > > Subject: Dynapi-Dev digest, Vol 1 #1021 - 3 msgs > > > > > > > > > > Send Dynapi-Dev mailing list submissions to > > > > dyn...@li... > > > > > > > > To subscribe or unsubscribe via the World Wide > > > Web, visit > > > > > > > > > > https://lists.sourceforge.net/lists/listinfo/dynapi-dev > > > > or, via email, send a message with subject or > body > > > 'help' to > > > > dyn...@li... > > > > > > > > You can reach the person managing the list at > > > > dyn...@li... > > > > > > > > When replying, please edit your Subject line > so it > > > is more specific > > > > than "Re: Contents of Dynapi-Dev digest..." > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------------- > -- > > > ---- > > > > > > > > > > Today's Topics: > > > > > > > > 1. onCreate bug. (Doug Melvin) > > > > 2. Mozilla cotnentwidth bug. (Doug Melvin) > > > > 3. your email (postmaster) > > > > > > > > > > > > > > > > -------------------------------------------------------------------------- > -- > > > ---- > > > > > > > > > > > _______________________________________________ > > > > Dynapi-Dev mailing list > > > > Dyn...@li... > > > > > > > > > > https://lists.sourceforge.net/lists/listinfo/dynapi-dev > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This sf.net email is sponsored by:ThinkGeek > > > Welcome to geek heaven. > > > http://thinkgeek.com/sf > > > _______________________________________________ > > > Dynapi-Dev mailing list > > > Dyn...@li... > > > > > > http://www.mail-archive.com/dyn...@li.../ > > > > > > __________________________________ > > Do you Yahoo!? > > The New Yahoo! Search - Faster. Easier. Bingo. > > http://search.yahoo.com > > > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://www.mail-archive.com/dyn...@li.../ __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com |
From: Doug M. <do...@cr...> - 2003-04-28 17:27:08
|
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.476 / Virus Database: 273 - Release Date: 4/24/03 |
From: Doug M. <do...@cr...> - 2003-04-28 17:24:40
|
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.476 / Virus Database: 273 - Release Date: 4/24/03 |
From: Mahidine M. <mme...@gh...> - 2003-04-28 16:26:20
|
3.0 where is the alpha1 ??? i found the problem, it's because of the security restriction of IE6 SP1 which doesn't allowed to fire an action on 'self.onload' MM ----- Original Message ----- From: "Raymond Irving" <xw...@ya...> To: <dyn...@li...> Sent: Monday, April 28, 2003 4:29 PM Subject: Re: [Dynapi-Dev] IE 6 SP1 and Onload event > > --- Mahidine Mendjeli <mme...@gh...> wrote: > > It seems IE 6 SP1 doesn't allow the possibility to > > fire an event when > > the page is loaded!!! > > so there is no possibility to create a Layer! > > Does someone experimented this problem? > > What version of DynAPI are you using? This problem > should have been fixed in 3.0 alpha 1 > > -- > Raymond Irving > > > MM > > > > ----- Original Message ----- > > From: <dyn...@li...> > > To: <dyn...@li...> > > Sent: Saturday, April 26, 2003 7:17 PM > > Subject: Dynapi-Dev digest, Vol 1 #1021 - 3 msgs > > > > > > > Send Dynapi-Dev mailing list submissions to > > > dyn...@li... > > > > > > To subscribe or unsubscribe via the World Wide > > Web, visit > > > > > > https://lists.sourceforge.net/lists/listinfo/dynapi-dev > > > or, via email, send a message with subject or body > > 'help' to > > > dyn...@li... > > > > > > You can reach the person managing the list at > > > dyn...@li... > > > > > > When replying, please edit your Subject line so it > > is more specific > > > than "Re: Contents of Dynapi-Dev digest..." > > > > > > > > > > > > > -------------------------------------------------------------------------- -- > > ---- > > > > > > > Today's Topics: > > > > > > 1. onCreate bug. (Doug Melvin) > > > 2. Mozilla cotnentwidth bug. (Doug Melvin) > > > 3. your email (postmaster) > > > > > > > > > > -------------------------------------------------------------------------- -- > > ---- > > > > > > > _______________________________________________ > > > Dynapi-Dev mailing list > > > Dyn...@li... > > > > > > https://lists.sourceforge.net/lists/listinfo/dynapi-dev > > > > > > > > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > > http://www.mail-archive.com/dyn...@li.../ > > > __________________________________ > Do you Yahoo!? > The New Yahoo! Search - Faster. Easier. Bingo. > http://search.yahoo.com > > |
From: Ramesh P. <ra...@in...> - 2003-04-28 16:13:15
|
Once upon a time not very long ago, Raymond Irving wrote: >--- Ramesh Pallikara <ra...@in...> >wrote: > > >>hi, >> >>there's seems to be a painting issue with mozilla >>when a dynlayer >>containing a visible ioelement child is dragged. The >>child layer changes >>it's position even before the parent does. anybody >>experienced this ??? >> >> > >One quick solution is to set the ioelement visible >property to false during a drag event. > >lyr.addEventListener({ > ondragstart:function(e){ > ioelm.setVisible(false); > }, > ondragend:function(e){ > ioelm.setVisible(true); > } >}); > just found one more way :-) setting an optimal drag increment to the layer also makes the behaviour almost non-existent. regardz, ramesh pallikara > >-- >Raymond Irving > > > >>is there a way to overcome this??? >> >>regardz, >>ramesh pallikara >> >>-- >>QOTD: >> "I've always wanted to work in the Federal Mint. >>And then go on >> strike. To make less money." >> >> >> >> >> >> >> >------------------------------------------------------- > > >>This sf.net email is sponsored by:ThinkGeek >>Welcome to geek heaven. >>http://thinkgeek.com/sf >>_______________________________________________ >>Dynapi-Dev mailing list >>Dyn...@li... >> >> >> >http://www.mail-archive.com/dyn...@li.../ > > >__________________________________ >Do you Yahoo!? >The New Yahoo! Search - Faster. Easier. Bingo. >http://search.yahoo.com > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >Dynapi-Dev mailing list >Dyn...@li... >http://www.mail-archive.com/dyn...@li.../ > > > -- QOTD: "I've always wanted to work in the Federal Mint. And then go on strike. To make less money." |
From: Raymond I. <xw...@ya...> - 2003-04-28 14:38:41
|
--- Ramesh Pallikara <ra...@in...> wrote: > hi, > > there's seems to be a painting issue with mozilla > when a dynlayer > containing a visible ioelement child is dragged. The > child layer changes > it's position even before the parent does. anybody > experienced this ??? One quick solution is to set the ioelement visible property to false during a drag event. lyr.addEventListener({ ondragstart:function(e){ ioelm.setVisible(false); }, ondragend:function(e){ ioelm.setVisible(true); } }); -- Raymond Irving > is there a way to overcome this??? > > regardz, > ramesh pallikara > > -- > QOTD: > "I've always wanted to work in the Federal Mint. > And then go on > strike. To make less money." > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://www.mail-archive.com/dyn...@li.../ __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com |