dynapi-dev — List related to the current DynAPI Core development

[Dynapi-Dev] Core API & GUI Updates

[Raymond I. <xw...@ya...>]

[+] Add dynapi.document.writeStyle()
[+] Add HTMLProgressBar
[+] Add HTMLColorPicker
[*] HTMLMenu addItem() will now respect text
directions from image inputs
[+] Add contMode (Container Mode) to HTMLMenu
addItem() text argument
[+] Add HTMLCel() and HTMLText() to HTMLComponent

[+] Added new examples (See
examples/dynapi.gui.*.html)


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

[Dynapi-Dev] [ dynapi-Bugs-787137 ] Memory leak in DynElement.deleteChild()

[SourceForge.net <no...@so...>]

Bugs item #787137, was opened at 2003-08-12 03:36
Message generated for change (Comment added) made by xwisdom
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=787137&group_id=5757

Category: DynAPI 3 API
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Andrew Gillett (agillett)
Assigned to: Nobody/Anonymous (nobody)
Summary: Memory leak in DynElement.deleteChild()

Initial Comment:
The DynElement.deleteChild() function is implemented 
thus:

p.deleteChild = function(c) {
	c.removeFromParent();
   	c._delete();
};

Although the _delete() function is documented in 
quickref.dynelement.html, it is not implemented 
_anywhere_ in the DynAPI source code, except for 
being set to dynapi.functions.Null in event.js.

If you have a page that repeatedly adds and removes 
DynElements, it will leak memory.  If you replace the call
to _delete() with a call to _destroy(), the memory leak 
goes away:

p.deleteChild = function(c) {
	c.removeFromParent();
   	c._destroy();
};


----------------------------------------------------------------------

>Comment By: Raymond Irving (xwisdom)
Date: 2003-08-14 13:02

Message:
Logged In: YES 
user_id=696242


Thanks for the feedback

Ok. Will keep the delete functions them _destroy() the layers 
as well.


----------------------------------------------------------------------

Comment By: L W (warp9pnt9)
Date: 2003-08-14 12:30

Message:
Logged In: YES 
user_id=706287

My view on the matter.

I think the naming convention would be clearer if the
function that removes children from parents was called
removeChild / removeFromParent, but not destroying the
layer.  I think this is how it works now.  I think the
function that removes the child from the parent AND destroys
the layer should be called deleteChild / deleteFromParent or
maybe destroyChild / destroyFromParent.  I think it's
confusing to add a new name "dispose" when it doesn't
intuitively correspond to an underlying "dispose" function.
 It's a little vague.

----------------------------------------------------------------------

Comment By: Raymond Irving (xwisdom)
Date: 2003-08-14 02:37

Message:
Logged In: YES 
user_id=696242


I see what's happening. IMO deleteChild() and removeChild 
means the same thing, correct? 

When a child layer is removed from the parent it's actually 
deleted from the parent, correct?  The layer is not completly 
destroyed as a reference to it still exists within DynObject.all 
collection. 

Calling _destroy() during a deleteChild() function will not only 
delete the child from its parent but it will also dispose of the 
child object.

I think we should change deleteChild/AllChildren/etc to 
disposeChild/AllChildren/etc wihich will clearly define what is 
been done to the object. The dispose functions will complete 
remove and destroy the object.

Are we all in agreement with changing delete to dispose? Or 
should we add the _destroy() function to deleteChild and 
keep the delete functions?  

(Note: If we keep the delete functions we'll have to 
document that it will completely destroy and remove the layer 
from the system.)



----------------------------------------------------------------------

Comment By: Andrew Gillett (agillett)
Date: 2003-08-14 00:31

Message:
Logged In: YES 
user_id=134108

> Are you using the lastest snapshot?
Yes, I check out the code directly from CVS.
> What browsers are experiencing this memory leak?
IE6 & Mozilla1.4, but that is not really relevant.

On 29/07/2003 12:26 AM (my time), in response to my post 
about a bug in deleteAllChildren(), you wrote:
>To fix the memory and layer problem use the following:
>
>p.deleteAllChildren = function() {
>	var c,l = this.children.length;
>	for(var i=0;i<l;i++) {
>		c=this.children[i];
>		if(c) {
>			c._destroy();
>			c._created = c.isChild = false;
>		};
>		delete this.children[i];
>	}
>	this.children.length = 0;
>};
>
This fix worked perfectly. The _destroy() method is called on 
each child of the layer.

However this is not what was put into CVS.  In the current 
version of event.js, deleteAllChildren() calls deleteFromParent
() which calls deleteChild() which calls _delete() instead of 
_destroy().

It is the call to _delete() that I have a problem with.  There 
is simply no such function.  In line 184 of event.js there is:

... = p._delete = p._destroy = dynapi.functions.Null;

but nowhere else in the entire source tree is _delete() 
defined.


Try the attached example.  On my Windows XP system, IE 
grows by about 6MB each time the "Memory Leak" button is 
pressed.  But if I replace the call to _delete() with a call to 
_destroy() in the deleteChild function, then IE doesn't leak at 
all.


----------------------------------------------------------------------

Comment By: Raymond Irving (xwisdom)
Date: 2003-08-13 13:53

Message:
Logged In: YES 
user_id=696242

Are you using the lastest snapshot?

What browsers are experiencing this memory leak?

You can get the lastest snapshot here:
http://dynapi.sourceforge.net/snapshot/?N=D


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=787137&group_id=5757

[Dynapi-Dev] [ dynapi-Bugs-787137 ] Memory leak in DynElement.deleteChild()

[SourceForge.net <no...@so...>]

Bugs item #787137, was opened at 2003-08-11 23:36
Message generated for change (Comment added) made by warp9pnt9
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=787137&group_id=5757

Category: DynAPI 3 API
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Andrew Gillett (agillett)
Assigned to: Nobody/Anonymous (nobody)
Summary: Memory leak in DynElement.deleteChild()

Initial Comment:
The DynElement.deleteChild() function is implemented 
thus:

p.deleteChild = function(c) {
	c.removeFromParent();
   	c._delete();
};

Although the _delete() function is documented in 
quickref.dynelement.html, it is not implemented 
_anywhere_ in the DynAPI source code, except for 
being set to dynapi.functions.Null in event.js.

If you have a page that repeatedly adds and removes 
DynElements, it will leak memory.  If you replace the call
to _delete() with a call to _destroy(), the memory leak 
goes away:

p.deleteChild = function(c) {
	c.removeFromParent();
   	c._destroy();
};


----------------------------------------------------------------------

Comment By: L W (warp9pnt9)
Date: 2003-08-14 08:30

Message:
Logged In: YES 
user_id=706287

My view on the matter.

I think the naming convention would be clearer if the
function that removes children from parents was called
removeChild / removeFromParent, but not destroying the
layer.  I think this is how it works now.  I think the
function that removes the child from the parent AND destroys
the layer should be called deleteChild / deleteFromParent or
maybe destroyChild / destroyFromParent.  I think it's
confusing to add a new name "dispose" when it doesn't
intuitively correspond to an underlying "dispose" function.
 It's a little vague.

----------------------------------------------------------------------

Comment By: Raymond Irving (xwisdom)
Date: 2003-08-13 22:37

Message:
Logged In: YES 
user_id=696242


I see what's happening. IMO deleteChild() and removeChild 
means the same thing, correct? 

When a child layer is removed from the parent it's actually 
deleted from the parent, correct?  The layer is not completly 
destroyed as a reference to it still exists within DynObject.all 
collection. 

Calling _destroy() during a deleteChild() function will not only 
delete the child from its parent but it will also dispose of the 
child object.

I think we should change deleteChild/AllChildren/etc to 
disposeChild/AllChildren/etc wihich will clearly define what is 
been done to the object. The dispose functions will complete 
remove and destroy the object.

Are we all in agreement with changing delete to dispose? Or 
should we add the _destroy() function to deleteChild and 
keep the delete functions?  

(Note: If we keep the delete functions we'll have to 
document that it will completely destroy and remove the layer 
from the system.)



----------------------------------------------------------------------

Comment By: Andrew Gillett (agillett)
Date: 2003-08-13 20:31

Message:
Logged In: YES 
user_id=134108

> Are you using the lastest snapshot?
Yes, I check out the code directly from CVS.
> What browsers are experiencing this memory leak?
IE6 & Mozilla1.4, but that is not really relevant.

On 29/07/2003 12:26 AM (my time), in response to my post 
about a bug in deleteAllChildren(), you wrote:
>To fix the memory and layer problem use the following:
>
>p.deleteAllChildren = function() {
>	var c,l = this.children.length;
>	for(var i=0;i<l;i++) {
>		c=this.children[i];
>		if(c) {
>			c._destroy();
>			c._created = c.isChild = false;
>		};
>		delete this.children[i];
>	}
>	this.children.length = 0;
>};
>
This fix worked perfectly. The _destroy() method is called on 
each child of the layer.

However this is not what was put into CVS.  In the current 
version of event.js, deleteAllChildren() calls deleteFromParent
() which calls deleteChild() which calls _delete() instead of 
_destroy().

It is the call to _delete() that I have a problem with.  There 
is simply no such function.  In line 184 of event.js there is:

... = p._delete = p._destroy = dynapi.functions.Null;

but nowhere else in the entire source tree is _delete() 
defined.


Try the attached example.  On my Windows XP system, IE 
grows by about 6MB each time the "Memory Leak" button is 
pressed.  But if I replace the call to _delete() with a call to 
_destroy() in the deleteChild function, then IE doesn't leak at 
all.


----------------------------------------------------------------------

Comment By: Raymond Irving (xwisdom)
Date: 2003-08-13 09:53

Message:
Logged In: YES 
user_id=696242

Are you using the lastest snapshot?

What browsers are experiencing this memory leak?

You can get the lastest snapshot here:
http://dynapi.sourceforge.net/snapshot/?N=D


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=787137&group_id=5757

[Dynapi-Dev] [ dynapi-Bugs-787137 ] Memory leak in DynElement.deleteChild()

[SourceForge.net <no...@so...>]

Bugs item #787137, was opened at 2003-08-12 03:36
Message generated for change (Comment added) made by xwisdom
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=787137&group_id=5757

Category: DynAPI 3 API
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Andrew Gillett (agillett)
Assigned to: Nobody/Anonymous (nobody)
Summary: Memory leak in DynElement.deleteChild()

Initial Comment:
The DynElement.deleteChild() function is implemented 
thus:

p.deleteChild = function(c) {
	c.removeFromParent();
   	c._delete();
};

Although the _delete() function is documented in 
quickref.dynelement.html, it is not implemented 
_anywhere_ in the DynAPI source code, except for 
being set to dynapi.functions.Null in event.js.

If you have a page that repeatedly adds and removes 
DynElements, it will leak memory.  If you replace the call
to _delete() with a call to _destroy(), the memory leak 
goes away:

p.deleteChild = function(c) {
	c.removeFromParent();
   	c._destroy();
};


----------------------------------------------------------------------

>Comment By: Raymond Irving (xwisdom)
Date: 2003-08-14 02:37

Message:
Logged In: YES 
user_id=696242


I see what's happening. IMO deleteChild() and removeChild 
means the same thing, correct? 

When a child layer is removed from the parent it's actually 
deleted from the parent, correct?  The layer is not completly 
destroyed as a reference to it still exists within DynObject.all 
collection. 

Calling _destroy() during a deleteChild() function will not only 
delete the child from its parent but it will also dispose of the 
child object.

I think we should change deleteChild/AllChildren/etc to 
disposeChild/AllChildren/etc wihich will clearly define what is 
been done to the object. The dispose functions will complete 
remove and destroy the object.

Are we all in agreement with changing delete to dispose? Or 
should we add the _destroy() function to deleteChild and 
keep the delete functions?  

(Note: If we keep the delete functions we'll have to 
document that it will completely destroy and remove the layer 
from the system.)



----------------------------------------------------------------------

Comment By: Andrew Gillett (agillett)
Date: 2003-08-14 00:31

Message:
Logged In: YES 
user_id=134108

> Are you using the lastest snapshot?
Yes, I check out the code directly from CVS.
> What browsers are experiencing this memory leak?
IE6 & Mozilla1.4, but that is not really relevant.

On 29/07/2003 12:26 AM (my time), in response to my post 
about a bug in deleteAllChildren(), you wrote:
>To fix the memory and layer problem use the following:
>
>p.deleteAllChildren = function() {
>	var c,l = this.children.length;
>	for(var i=0;i<l;i++) {
>		c=this.children[i];
>		if(c) {
>			c._destroy();
>			c._created = c.isChild = false;
>		};
>		delete this.children[i];
>	}
>	this.children.length = 0;
>};
>
This fix worked perfectly. The _destroy() method is called on 
each child of the layer.

However this is not what was put into CVS.  In the current 
version of event.js, deleteAllChildren() calls deleteFromParent
() which calls deleteChild() which calls _delete() instead of 
_destroy().

It is the call to _delete() that I have a problem with.  There 
is simply no such function.  In line 184 of event.js there is:

... = p._delete = p._destroy = dynapi.functions.Null;

but nowhere else in the entire source tree is _delete() 
defined.


Try the attached example.  On my Windows XP system, IE 
grows by about 6MB each time the "Memory Leak" button is 
pressed.  But if I replace the call to _delete() with a call to 
_destroy() in the deleteChild function, then IE doesn't leak at 
all.


----------------------------------------------------------------------

Comment By: Raymond Irving (xwisdom)
Date: 2003-08-13 13:53

Message:
Logged In: YES 
user_id=696242

Are you using the lastest snapshot?

What browsers are experiencing this memory leak?

You can get the lastest snapshot here:
http://dynapi.sourceforge.net/snapshot/?N=D


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=787137&group_id=5757

[Dynapi-Dev] [ dynapi-Bugs-787137 ] Memory leak in DynElement.deleteChild()

[SourceForge.net <no...@so...>]

Bugs item #787137, was opened at 2003-08-12 13:36
Message generated for change (Comment added) made by agillett
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=787137&group_id=5757

Category: DynAPI 3 API
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Andrew Gillett (agillett)
Assigned to: Nobody/Anonymous (nobody)
Summary: Memory leak in DynElement.deleteChild()

Initial Comment:
The DynElement.deleteChild() function is implemented 
thus:

p.deleteChild = function(c) {
	c.removeFromParent();
   	c._delete();
};

Although the _delete() function is documented in 
quickref.dynelement.html, it is not implemented 
_anywhere_ in the DynAPI source code, except for 
being set to dynapi.functions.Null in event.js.

If you have a page that repeatedly adds and removes 
DynElements, it will leak memory.  If you replace the call
to _delete() with a call to _destroy(), the memory leak 
goes away:

p.deleteChild = function(c) {
	c.removeFromParent();
   	c._destroy();
};


----------------------------------------------------------------------

>Comment By: Andrew Gillett (agillett)
Date: 2003-08-14 10:31

Message:
Logged In: YES 
user_id=134108

> Are you using the lastest snapshot?
Yes, I check out the code directly from CVS.
> What browsers are experiencing this memory leak?
IE6 & Mozilla1.4, but that is not really relevant.

On 29/07/2003 12:26 AM (my time), in response to my post 
about a bug in deleteAllChildren(), you wrote:
>To fix the memory and layer problem use the following:
>
>p.deleteAllChildren = function() {
>	var c,l = this.children.length;
>	for(var i=0;i<l;i++) {
>		c=this.children[i];
>		if(c) {
>			c._destroy();
>			c._created = c.isChild = false;
>		};
>		delete this.children[i];
>	}
>	this.children.length = 0;
>};
>
This fix worked perfectly. The _destroy() method is called on 
each child of the layer.

However this is not what was put into CVS.  In the current 
version of event.js, deleteAllChildren() calls deleteFromParent
() which calls deleteChild() which calls _delete() instead of 
_destroy().

It is the call to _delete() that I have a problem with.  There 
is simply no such function.  In line 184 of event.js there is:

... = p._delete = p._destroy = dynapi.functions.Null;

but nowhere else in the entire source tree is _delete() 
defined.


Try the attached example.  On my Windows XP system, IE 
grows by about 6MB each time the "Memory Leak" button is 
pressed.  But if I replace the call to _delete() with a call to 
_destroy() in the deleteChild function, then IE doesn't leak at 
all.


----------------------------------------------------------------------

Comment By: Raymond Irving (xwisdom)
Date: 2003-08-13 23:53

Message:
Logged In: YES 
user_id=696242

Are you using the lastest snapshot?

What browsers are experiencing this memory leak?

You can get the lastest snapshot here:
http://dynapi.sourceforge.net/snapshot/?N=D


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=787137&group_id=5757

[Dynapi-Dev] Box Model Fix for DynLayer?

[Raymond I. <xw...@ya...>]

Hello,

Is there anyone who can implement this box model fix
into DynLayer so we can use CSS border on both IE and
DOM browsers?

http://jscript.dk/Util/BoxModelFix/

Thanks

--
Raymond Irving

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

[Dynapi-Dev] [ dynapi-Bugs-787137 ] Memory leak in DynElement.deleteChild()

[SourceForge.net <no...@so...>]

Bugs item #787137, was opened at 2003-08-12 03:36
Message generated for change (Comment added) made by xwisdom
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=787137&group_id=5757

Category: DynAPI 3 API
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Andrew Gillett (agillett)
Assigned to: Nobody/Anonymous (nobody)
Summary: Memory leak in DynElement.deleteChild()

Initial Comment:
The DynElement.deleteChild() function is implemented 
thus:

p.deleteChild = function(c) {
	c.removeFromParent();
   	c._delete();
};

Although the _delete() function is documented in 
quickref.dynelement.html, it is not implemented 
_anywhere_ in the DynAPI source code, except for 
being set to dynapi.functions.Null in event.js.

If you have a page that repeatedly adds and removes 
DynElements, it will leak memory.  If you replace the call
to _delete() with a call to _destroy(), the memory leak 
goes away:

p.deleteChild = function(c) {
	c.removeFromParent();
   	c._destroy();
};


----------------------------------------------------------------------

>Comment By: Raymond Irving (xwisdom)
Date: 2003-08-13 13:53

Message:
Logged In: YES 
user_id=696242

Are you using the lastest snapshot?

What browsers are experiencing this memory leak?

You can get the lastest snapshot here:
http://dynapi.sourceforge.net/snapshot/?N=D


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=787137&group_id=5757

Re: [Dynapi-Dev] The DynAPI Web Team

[Joy R. <joy...@ho...>]

Hello,

>What is the role of concept designer?

Site structure, basic ideas for UI (wireframe layout), creative ideas / 
design of content (not the graphical design or content production) and the 
script for the site. In concept designers responsiblity is that site meet 
the customer demands. In our projects concept designer is usually the right 
hand of the project manager. To be successfull in concept designers post one 
should be both analytical and creative. Good understandig of web and clear 
vision of where the web is going will help a lot too.

You're interested?-)


- Juho Risku / Helmi Staff
  http:///www.visualway.com/helmi


>From: "Stephen Carroll" <sca...@vi...>
>Reply-To: dyn...@li...
>To: <dyn...@li...>
>Subject: Re: [Dynapi-Dev] The DynAPI Web Team
>Date: Thu, 7 Aug 2003 11:47:50 -0700
>
>What is the role of concept designer?
>
>----- Original Message -----
>From: "Kevin" <ke...@ke...>
>To: <dyn...@li...>
>Sent: Thursday, August 07, 2003 9:13 AM
>Subject: Re: [Dynapi-Dev] The DynAPI Web Team
>
>
> > Raymond Irving wrote:
> >
> > > Hi Everyone
> > >
> > > So far we have the following volunteers:
> > >
> > > 1) Project manager
> > > Joy Ride (Juhu)
> > > 2) Consept designer
> > > 3) Graphic designer
> > > Diane Tomlins
> > > 4) Programmer(s)
> > > Leif W
> > > C Kissinger
> > > 5) Content provider(s)
> > >
> >
> > Perhaps I can help out in a programming role.
> > -
> > Kevin
> >
> > > We need more persons to help out with this part of the
> > > project. It doesn't matter how small or how great a
> > > role you can play. Your time and effort is well
> > > appreciated. Besides that it's just pure fun!
> > >
> > > We need to get this part of the project started as
> > > we're planning to have DynAPI 3.0 stable (or fully
> > > launched) by November.
> > >
> > > Are we in agreement here?
> > >
> > > --
> > > Raymond Irving
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > Yahoo! SiteBuilder - Free, easy-to-use web site design software
> > > http://sitebuilder.yahoo.com
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> > > Data Reports, E-commerce, Portals, and Forums are available now.
> > > Download today and enter to win an XBOX or Visual Studio .NET.
> > >
>http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> > > _______________________________________________
> > > Dynapi-Dev mailing list
> > > Dyn...@li...
> > > http://www.mail-archive.com/dyn...@li.../
> >
> >
>
>
>
>
>-------------------------------------------------------
>This SF.Net email sponsored by: Free pre-built ASP.NET sites including
>Data Reports, E-commerce, Portals, and Forums are available now.
>Download today and enter to win an XBOX or Visual Studio .NET.
>http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
>_______________________________________________
>Dynapi-Dev mailing list
>Dyn...@li...
>http://www.mail-archive.com/dyn...@li.../

_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail

Re: [Dynapi-Dev] The DynAPI Web Team

[Joy R. <joy...@ho...>]

Hello,

>Perhaps I can help out in a programming role.

Thank you. :-)


- Juho Risku / Helmi Staff
  http://www.visualway.com/helmi


>From: "Kevin" <ke...@ke...>
>Reply-To: dyn...@li...
>To: <dyn...@li...>
>Subject: Re: [Dynapi-Dev] The DynAPI Web Team
>Date: Thu, 7 Aug 2003 17:13:07 +0100
>
>Raymond Irving wrote:
>
> > Hi Everyone
> >
> > So far we have the following volunteers:
> >
> > 1) Project manager
> > Joy Ride (Juhu)
> > 2) Consept designer
> > 3) Graphic designer
> > Diane Tomlins
> > 4) Programmer(s)
> > Leif W
> > C Kissinger
> > 5) Content provider(s)
> >
>
>Perhaps I can help out in a programming role.
>-
>Kevin
>
> > We need more persons to help out with this part of the
> > project. It doesn't matter how small or how great a
> > role you can play. Your time and effort is well
> > appreciated. Besides that it's just pure fun!
> >
> > We need to get this part of the project started as
> > we're planning to have DynAPI 3.0 stable (or fully
> > launched) by November.
> >
> > Are we in agreement here?
> >
> > --
> > Raymond Irving
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! SiteBuilder - Free, easy-to-use web site design software
> > http://sitebuilder.yahoo.com
> >
> >
> > -------------------------------------------------------
> > This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> > Data Reports, E-commerce, Portals, and Forums are available now.
> > Download today and enter to win an XBOX or Visual Studio .NET.
> > 
>http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://www.mail-archive.com/dyn...@li.../
>
>
>-------------------------------------------------------
>This SF.Net email sponsored by: Free pre-built ASP.NET sites including
>Data Reports, E-commerce, Portals, and Forums are available now.
>Download today and enter to win an XBOX or Visual Studio .NET.
>http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
>_______________________________________________
>Dynapi-Dev mailing list
>Dyn...@li...
>http://www.mail-archive.com/dyn...@li.../

_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online 
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

[Dynapi-Dev] [ dynapi-Bugs-787137 ] Memory leak in DynElement.deleteChild()

[SourceForge.net <no...@so...>]

Bugs item #787137, was opened at 2003-08-12 13:36
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=787137&group_id=5757

Category: DynAPI 3 API
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Andrew Gillett (agillett)
Assigned to: Nobody/Anonymous (nobody)
Summary: Memory leak in DynElement.deleteChild()

Initial Comment:
The DynElement.deleteChild() function is implemented 
thus:

p.deleteChild = function(c) {
	c.removeFromParent();
   	c._delete();
};

Although the _delete() function is documented in 
quickref.dynelement.html, it is not implemented 
_anywhere_ in the DynAPI source code, except for 
being set to dynapi.functions.Null in event.js.

If you have a page that repeatedly adds and removes 
DynElements, it will leak memory.  If you replace the call
to _delete() with a call to _destroy(), the memory leak 
goes away:

p.deleteChild = function(c) {
	c.removeFromParent();
   	c._destroy();
};


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=787137&group_id=5757

Re: [Dynapi-Dev] New HTMLProgressBar and HTMLColorPicker

[Raymond I. <xw...@ya...>]

Cool! 

This one was design using inline html compoents, so I
did not include any message over the bar.

--
Raymond Irving

--- Jesse Vitrone <je...@6t...> wrote:
> Ahh....you beat me to it :P  I'm testing my progress
> bar, but started 
> working on other stuff and never make a test page
> for people to take a 
> look at.
> 
> Mine looks like the one you have on top, but it
> displays an X% or a 
> message over the bar.
> 
> Jesse
> 
> Raymond Irving wrote:
> 
> >Hello Everyone,
> >
> >Here are two new HTMLComponents for your viewing.
> >
> >Please give your feedback on these.
> >
>
>http://www24.brinkster.com/dyntools/next/examples/dynapi.gui.htmlprogressbar.html
> >
>
>http://www24.brinkster.com/dyntools/next/examples/dynapi.gui.htmlcolorpicker.html
> >
> >
> >--
> >Raymond Irving
> >
> >__________________________________
> >Do you Yahoo!?
> >Yahoo! SiteBuilder - Free, easy-to-use web site
> design software
> >http://sitebuilder.yahoo.com
> >
> >
>
>-------------------------------------------------------
> >This SF.Net email sponsored by: Free pre-built
> ASP.NET sites including
> >Data Reports, E-commerce, Portals, and Forums are
> available now.
> >Download today and enter to win an XBOX or Visual
> Studio .NET.
>
>http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> >_______________________________________________
> >Dynapi-Dev mailing list
> >Dyn...@li...
>
>http://www.mail-archive.com/dyn...@li.../
> >  
> >
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built
> ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are
> available now.
> Download today and enter to win an XBOX or Visual
> Studio .NET.
>
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

Re: [Dynapi-Dev] New HTMLProgressBar and HTMLColorPicker

[Jesse V. <je...@6t...>]

Ahh....you beat me to it :P  I'm testing my progress bar, but started 
working on other stuff and never make a test page for people to take a 
look at.

Mine looks like the one you have on top, but it displays an X% or a 
message over the bar.

Jesse

Raymond Irving wrote:

>Hello Everyone,
>
>Here are two new HTMLComponents for your viewing.
>
>Please give your feedback on these.
>
>http://www24.brinkster.com/dyntools/next/examples/dynapi.gui.htmlprogressbar.html
>
>http://www24.brinkster.com/dyntools/next/examples/dynapi.gui.htmlcolorpicker.html
>
>
>--
>Raymond Irving
>
>__________________________________
>Do you Yahoo!?
>Yahoo! SiteBuilder - Free, easy-to-use web site design software
>http://sitebuilder.yahoo.com
>
>
>-------------------------------------------------------
>This SF.Net email sponsored by: Free pre-built ASP.NET sites including
>Data Reports, E-commerce, Portals, and Forums are available now.
>Download today and enter to win an XBOX or Visual Studio .NET.
>http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
>_______________________________________________
>Dynapi-Dev mailing list
>Dyn...@li...
>http://www.mail-archive.com/dyn...@li.../
>  
>

[Dynapi-Dev] New HTMLProgressBar and HTMLColorPicker

[Raymond I. <xw...@ya...>]

Hello Everyone,

Here are two new HTMLComponents for your viewing.

Please give your feedback on these.

http://www24.brinkster.com/dyntools/next/examples/dynapi.gui.htmlprogressbar.html

http://www24.brinkster.com/dyntools/next/examples/dynapi.gui.htmlcolorpicker.html


--
Raymond Irving

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

[Dynapi-Dev] [ dynapi-Bugs-762495 ] Wrong position retured when page has been scrolled down.

[SourceForge.net <no...@so...>]

Bugs item #762495, was opened at 2003-06-28 22:31
Message generated for change (Comment added) made by bs_php
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=762495&group_id=5757

Category: DynAPI 3 API
Group: Unverified
>Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Sam Blum (bs_php)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong position retured when page has been scrolled down.

Initial Comment:
Reproduced the bug in IE and Mozilla 1.3

To see the effect, open the dynapi example:
examples/dynapi.api.mouseevent.html 
- You should see some colored layers that are cascaded 
in each 
  other in the middle of the page. 
- On the left we have some links to turn mouse-events 
on and off.
- The debugger window should open as well.

The page contains so much info, that a standard scroll-
bar should appear on the right of the browser. If not 
make the browser window less high.

Now do as follows:
A) Turn on the click/dblclick events for the blue layer. 
   This is done by clicking on the 
      "Listen to click/dblclick events -> blue -> on" 
   link (see the page)

B) Then click on the blue layer top left corner and look 
   at the output on the debugger window. It should say 
   something like this: 
   "click blue xy=0,0 pXY=300,200 origin=blue"

   NOTE: 
   xy are the coordinates of the click on the blue layer 
   relative to it's own top left corner. pXY are the 
   absolute coordinates relative to the view (top left 
   corner of the browser).

C) Now scroll down a little and click again on the blue 
   layer (try to hit the same spot). Now in the debugger 
   window look at the result: 
   "click blue xy=0,-148 pXY=300,52 origin=blue"

BUG: 
  Compare the xy result 0,0 and 0,-148. I would have 
  expected to get the same result in case A) and B) 
  for xy (the pXY results are OK). But the y axis has 
  a negative number, caused by the scrolling.
  
  
Side Effect Bug:  
  Next I modified the code and set the red layer 
to 'relative'
  Thus, I added line:  red.setPosition('relative');
  This will position the layers at the bottom of the 
  page. Again try to repeat B) and C) (as good as you 
can) 
  and compare the results:
    "click blue xy=8,496 pXY=308,696 origin=blue"
    "click blue xy=8,396 pXY=308,596 origin=blue"

The effect is the same AND a *side effect* shows up:
alway have an x offset of 8px (13px on IE). But I heard 
that reletive posistioning is problematic.

-- bs_php

----------------------------------------------------------------------

>Comment By: Sam Blum (bs_php)
Date: 2003-08-09 02:13

Message:
Logged In: YES 
user_id=308859

The bug has been verified and a fix for the bug has been 
implemented.  The fix should be available in CVS as well as the 
next official release of the DynAPI.

----------------------------------------------------------------------

Comment By: Sam Blum (bs_php)
Date: 2003-08-09 02:13

Message:
Logged In: YES 
user_id=308859

Look's like it's fixed :)

----------------------------------------------------------------------

Comment By: Sam Blum (bs_php)
Date: 2003-07-04 00:44

Message:
Logged In: YES 
user_id=308859

According to the CVS on sourceforge, no updates have been 
mad to mouse_dom.js in dynapi3x.

Are you using an other CVS? If so can I get access?

-- sam

----------------------------------------------------------------------

Comment By: Raymond Irving (xwisdom)
Date: 2003-06-30 14:55

Message:
Logged In: YES 
user_id=696242

Hi bs_php,

Bug verified and fixed

I've implemented your fix into the MouseEvent files and it 
seems to have resolve the porblem. Many thanks for this fix.

--
Raymond Irving

----------------------------------------------------------------------

Comment By: Sam Blum (bs_php)
Date: 2003-06-29 01:18

Message:
Logged In: YES 
user_id=308859

This would my suggestion for mouse_dom.js

p.getScrollX = function() {return 
document.body.scrollTop||0};
p.getScrollY = function() {return 
document.body.scrollLeft||0};
p.getX=function() {return (this.x||0)  + this.getScrollX()};
p.getY=function() {return (this.y||0)  + this.getScrollY()};


This would my suggestion for mouse_ie.js
p.getScrollX = function() {return window.pageXOffset||0};
p.getScrollY = function() {return window.pageYOffset||0};
p.getX=function() {return (this.x||0)  + this.getScrollX()};
p.getY=function() {return (this.y||0)  + this.getScrollY()};



----------------------------------------------------------------------

Comment By: Sam Blum (bs_php)
Date: 2003-06-29 00:47

Message:
Logged In: YES 
user_id=308859

OK here is the solution ( I know it' currently a hack) 
=================================
For Mozzila 1.3 in mouse_dom.js replace the lines:

  p.getX = function() {return this.x};
  p.getY = function() {return this.y};

with 

  p.getX_ = function() {
    var _x = this.x||0;
    var _xOffset = 0;
    if (this.ns) {
      _xOffset = document.body.scrollTop||0;
    }else{
      _xOffset = window.pageXOffset||0;
    }
    return _x + _xOffset;
  };
  
  p.getY_ = function() {
    var _y = this.y||0;
    var _yOffset = 0;
    if (this.ns) {
      _yOffset = document.body.scrollLeft||0;
    }else{
      _yOffset = window.pageYOffset||0;
    }
    return _y + _yOffset;
  };


NOTE: I've seen in the code that this.x and this.y are refered 
often directly (not using the getX()-methode) so there may 
more to correct then just the methods  

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105757&aid=762495&group_id=5757

Re: [Dynapi-Dev] New Image button - cache problem.

[Raymond I. <xw...@ya...>]

It works grea in Moz (Phoenix 0.5). I think the
problem is with IE. IE always reloads background
images. Don't ask me why :( It's just one of those sad
things.

--
Raymond Irving

--- Kevin <ke...@ke...> wrote:
> 
> Raymond Irving wrote:
> 
> > Hi Kevin,
> > 
> > This seems very strange it would appear that IE
> has a
> > caching problem. I would however try this:
> > 
> > onclick:function(e) {
> >   var o=e.getSource();
> >   setTimeout('winopen('+o.id+');',100)
> > }
> 
> I'll try that.
> 
> > The images should not go blank on each click. Does
> > this occurs when the buttons are click or only
> during
> > the window open statement?
> 
> Click refresh and everything works perfectly
> mouseover/
> mouseout events. After a click the new window had
> focus
> and a mouseover event causes a reload of the image?
> 
> I can't test on other browsers - is Mozilla /
> Netscape - OK
> 
> -
> Kevin
> 
> > --
> > Raymond Irving
> > 
> > --- Kevin <ke...@ke...> wrote:
> > > Hi,
> > > 
> > > If the port5 domain is down I've put a copy of
> the
> > > example on demon:
> > > 
> > >
> >
>
http://www.kegcl.demon.co.uk/examples/demo.getimage3.html
> > > 
> > > -
> > > Kevin
> > > 
> > > > Hi,
> > > > 
> > > > I have found an annoying problem were a cached
> > > image is still reloaded
> > > > under some circumstance - when another window
> has
> > > been opened?  
> > > > 
> > > >
> http://keg.port5.com/examples/demo.getimage3.html
> > > > 
> > > > Click on any folder tab to open the small
> window.
> > > > 
> > > > Note mouse over/out works fine with images
> from
> > > cache until the new
> > > > window is open? I was testing using IE6.
> > > > 
> > > > The idea is not to have 2,3 or 4 images for
> every
> > > button when only one
> > > > set of cached images is needed and just change
> the
> > > label for each button.
> > > > 
> > > > So for a 3 image x 10 menu buttons example
> only 3
> > > images not 30 are
> > > > downloaded - a nice saving in bandwidth!
> > > > 
> > > > If only it worked - any help on caching
> problems
> > > would be appreciated.
> > > > 
> > > > -
> > > > Kevin
> > > > 
> > > > 
> > > > 
> > > >
> > >
> >
>
-------------------------------------------------------
> > > > This SF.Net email sponsored by: Free pre-built
> > > ASP.NET sites including
> > > > Data Reports, E-commerce, Portals, and Forums
> are
> > > available now.
> > > > Download today and enter to win an XBOX or
> Visual
> > > Studio .NET.
> > > >
> > >
> >
>
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> > > >
> _______________________________________________
> > > > Dynapi-Dev mailing list
> > > > Dyn...@li...
> > > >
> > >
> >
>
http://www.mail-archive.com/dyn...@li.../
> > > 
> > > 
> > >
> >
>
-------------------------------------------------------
> > > This SF.Net email sponsored by: Free pre-built
> > > ASP.NET sites including
> > > Data Reports, E-commerce, Portals, and Forums
> are
> > > available now.
> > > Download today and enter to win an XBOX or
> Visual
> > > Studio .NET.
> > >
> >
>
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> > > _______________________________________________
> > > Dynapi-Dev mailing list
> > > Dyn...@li...
> > >
> >
>
http://www.mail-archive.com/dyn...@li.../
> > 
> > 
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! SiteBuilder - Free, easy-to-use web site
> design software
> > http://sitebuilder.yahoo.com
> > 
> > 
> >
>
-------------------------------------------------------
> > This SF.Net email sponsored by: Free pre-built
> ASP.NET sites including
> > Data Reports, E-commerce, Portals, and Forums are
> available now.
> > Download today and enter to win an XBOX or Visual
> Studio .NET.
> >
>
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> >
>
http://www.mail-archive.com/dyn...@li.../
> 
> 
>
-------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built
> ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are
> available now.
> Download today and enter to win an XBOX or Visual
> Studio .NET.
>
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

Re: [Dynapi-Dev] New Image button - cache problem.

[Kevin <ke...@ke...>]

Raymond Irving wrote:

> Hi Kevin,
> 
> This seems very strange it would appear that IE has a
> caching problem. I would however try this:
> 
> onclick:function(e) {
>   var o=e.getSource();
>   setTimeout('winopen('+o.id+');',100)
> }

I'll try that.

> The images should not go blank on each click. Does
> this occurs when the buttons are click or only during
> the window open statement?

Click refresh and everything works perfectly mouseover/
mouseout events. After a click the new window had focus
and a mouseover event causes a reload of the image?

I can't test on other browsers - is Mozilla / Netscape - OK

-
Kevin

> --
> Raymond Irving
> 
> --- Kevin <ke...@ke...> wrote:
> > Hi,
> > 
> > If the port5 domain is down I've put a copy of the
> > example on demon:
> > 
> >
> http://www.kegcl.demon.co.uk/examples/demo.getimage3.html
> > 
> > -
> > Kevin
> > 
> > > Hi,
> > > 
> > > I have found an annoying problem were a cached
> > image is still reloaded
> > > under some circumstance - when another window has
> > been opened?  
> > > 
> > > http://keg.port5.com/examples/demo.getimage3.html
> > > 
> > > Click on any folder tab to open the small window.
> > > 
> > > Note mouse over/out works fine with images from
> > cache until the new
> > > window is open? I was testing using IE6.
> > > 
> > > The idea is not to have 2,3 or 4 images for every
> > button when only one
> > > set of cached images is needed and just change the
> > label for each button.
> > > 
> > > So for a 3 image x 10 menu buttons example only 3
> > images not 30 are
> > > downloaded - a nice saving in bandwidth!
> > > 
> > > If only it worked - any help on caching problems
> > would be appreciated.
> > > 
> > > -
> > > Kevin
> > > 
> > > 
> > > 
> > >
> >
> -------------------------------------------------------
> > > This SF.Net email sponsored by: Free pre-built
> > ASP.NET sites including
> > > Data Reports, E-commerce, Portals, and Forums are
> > available now.
> > > Download today and enter to win an XBOX or Visual
> > Studio .NET.
> > >
> >
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> > > _______________________________________________
> > > Dynapi-Dev mailing list
> > > Dyn...@li...
> > >
> >
> http://www.mail-archive.com/dyn...@li.../
> > 
> > 
> >
> -------------------------------------------------------
> > This SF.Net email sponsored by: Free pre-built
> > ASP.NET sites including
> > Data Reports, E-commerce, Portals, and Forums are
> > available now.
> > Download today and enter to win an XBOX or Visual
> > Studio .NET.
> >
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> >
> http://www.mail-archive.com/dyn...@li.../
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../

Re: [Dynapi-Dev] [ dynapi-Patches-784806 ] Patches/Updates for DynAPI

[Jesse V. <je...@6t...>]

Raymond,
    Yes, it seems to have fixed it.  Thanks.

Jesse

Raymond Irving wrote:

>I've not tested it against you code but in theory it
>should fix the problem. Please try it and let me know.
>
>--
>Raymond Irving
>
>--- Jesse Vitrone <je...@6t...> wrote:
>  
>
>>[-] Fix HTMLMenu bug with submenus by setting 
>>submenus to -x and -y
>>
>>Does this fix the menu problem that I was seeing and
>>we had talked 
>>about?  Or is this something else?
>>
>>Thanks,
>>    Jesse
>>
>>
>>SourceForge.net wrote:
>>
>>    
>>
>>>Patches item #784806, was opened at 2003-08-07
>>>      
>>>
>>14:41
>>    
>>
>>>Message generated for change (Tracker Item
>>>      
>>>
>>Submitted) made by Item Submitter
>>    
>>
>>>You can respond by visiting: 
>>>      
>>>
>>https://sourceforge.net/tracker/?func=detail&atid=305757&aid=784806&group_id=5757
>>    
>>
>>>Category: DynAPI 3 API
>>>Group: None
>>>Status: Open
>>>Resolution: None
>>>Priority: 5
>>>Submitted By: Raymond Irving (xwisdom)
>>>Assigned to: Nobody/Anonymous (nobody)
>>>Summary: Patches/Updates for DynAPI
>>>
>>>Initial Comment:
>>>
>>>Please note the following changes/fixes to API
>>>
>>>[+] Add setItems() function to HTMLListBox
>>>[-] Fix HTMLMenu bug with submenus by setting 
>>>submenus to -x and -y
>>>[-] Fix getImage() bug when using different params
>>>
>>>You can check out the lastest updates inside the
>>>      
>>>
>>cvs
>>    
>>
>>>      
>>>
>>----------------------------------------------------------------------
>>    
>>
>>>You can respond by visiting: 
>>>      
>>>
>>https://sourceforge.net/tracker/?func=detail&atid=305757&aid=784806&group_id=5757
>>    
>>
>>>      
>>>
>>-------------------------------------------------------
>>    
>>
>>>This SF.Net email sponsored by: Free pre-built
>>>      
>>>
>>ASP.NET sites including
>>    
>>
>>>Data Reports, E-commerce, Portals, and Forums are
>>>      
>>>
>>available now.
>>    
>>
>>>Download today and enter to win an XBOX or Visual
>>>      
>>>
>>Studio .NET.
>>
>>http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
>>    
>>
>>>_______________________________________________
>>>Dynapi-Dev mailing list
>>>Dyn...@li...
>>>      
>>>
>>http://www.mail-archive.com/dyn...@li.../
>>    
>>
>>> 
>>>
>>>      
>>>
>>
>>
>>    
>>
>-------------------------------------------------------
>  
>
>>This SF.Net email sponsored by: Free pre-built
>>ASP.NET sites including
>>Data Reports, E-commerce, Portals, and Forums are
>>available now.
>>Download today and enter to win an XBOX or Visual
>>Studio .NET.
>>
>>    
>>
>http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
>  
>
>>_______________________________________________
>>Dynapi-Dev mailing list
>>Dyn...@li...
>>
>>    
>>
>http://www.mail-archive.com/dyn...@li.../
>
>
>__________________________________
>Do you Yahoo!?
>Yahoo! SiteBuilder - Free, easy-to-use web site design software
>http://sitebuilder.yahoo.com
>
>
>-------------------------------------------------------
>This SF.Net email sponsored by: Free pre-built ASP.NET sites including
>Data Reports, E-commerce, Portals, and Forums are available now.
>Download today and enter to win an XBOX or Visual Studio .NET.
>http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
>_______________________________________________
>Dynapi-Dev mailing list
>Dyn...@li...
>http://www.mail-archive.com/dyn...@li.../
>  
>

Re: [Dynapi-Dev] New Image button - cache problem.

[Raymond I. <xw...@ya...>]

Hi Kevin,

This seems very strange it would appear that IE has a
caching problem. I would however try this:

onclick:function(e) {
  var o=e.getSource();
  setTimeout('winopen('+o.id+');',100)
}

The images should not go blank on each click. Does
this occurs when the buttons are click or only during
the window open statement?

--
Raymond Irving

--- Kevin <ke...@ke...> wrote:
> Hi,
> 
> If the port5 domain is down I've put a copy of the
> example on demon:
> 
>
http://www.kegcl.demon.co.uk/examples/demo.getimage3.html
> 
> -
> Kevin
> 
> > Hi,
> > 
> > I have found an annoying problem were a cached
> image is still reloaded
> > under some circumstance - when another window has
> been opened?  
> > 
> > http://keg.port5.com/examples/demo.getimage3.html
> > 
> > Click on any folder tab to open the small window.
> > 
> > Note mouse over/out works fine with images from
> cache until the new
> > window is open? I was testing using IE6.
> > 
> > The idea is not to have 2,3 or 4 images for every
> button when only one
> > set of cached images is needed and just change the
> label for each button.
> > 
> > So for a 3 image x 10 menu buttons example only 3
> images not 30 are
> > downloaded - a nice saving in bandwidth!
> > 
> > If only it worked - any help on caching problems
> would be appreciated.
> > 
> > -
> > Kevin
> > 
> > 
> > 
> >
>
-------------------------------------------------------
> > This SF.Net email sponsored by: Free pre-built
> ASP.NET sites including
> > Data Reports, E-commerce, Portals, and Forums are
> available now.
> > Download today and enter to win an XBOX or Visual
> Studio .NET.
> >
>
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> >
>
http://www.mail-archive.com/dyn...@li.../
> 
> 
>
-------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built
> ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are
> available now.
> Download today and enter to win an XBOX or Visual
> Studio .NET.
>
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

Re: [Dynapi-Dev] Introducing the StyleManager

[Raymond I. <xw...@ya...>]

Hi,

Once I'm done with a simple example I'll post it to
the list.

--
Raymond Irving

--- Kevin <ke...@ke...> wrote:
> 
> Raymond wrote:
> 
> > The StyleManager is not about CSS. It's about
> being
> > able to apply javascript functions to an exiting
> > widget to modify it's functions, change it's look
> and
> > it's behavior.
> > 
> > For example you can use the StyleManager to
> convert an
> > ordinary DynLayer into a button widget by just
> > applying the "ButtonStyle". Later you could then
> > change that layer into a ProgressBar by just
> applying
> > the "ProgressBarStyle".
> > 
> > IMO it's a completely modular and fashionable way
> to
> > design DynAPI widgets. With StyleManager a basic
> > widget can be morphed into another widget by just
> > simply changing the style.
> 
> My thinking is:
> 
> button1=new Button()
> button1.setHighLight(...)
> progressbar1=new ProgressBar()
> progressbar1.setScale(...)
> ...
> Morph button1 to a progressbar
> ...
> button1.setScale(..) ?
> 
> How would we know button1 has new methods as
> setScale() was before meaningless for a button?
> 
> button1 and progessbar1 are instances of their own
> class
> with separate attributes and methods. Morphing
> button1
> to a progressbar? Ok fine, but morphing
> 'setStyle(...) or
> maybe setMorph(...)' is not a method of either class
> but
> more a method of a management class not related to
> (or
> inherited from) a DynLayer.
> 
> Perhaps an example would help in understanding what
> is
> intended in an OOP context. Thanks.
> 
> -
> Kevin.
> 
> > > With an established interface it is preferable
> to
> > > add to,
> > > rather than change and break backward
> compatibility
> > 
> > Ok, I guess we'll just keep the 7th argument and
> use
> > setStyle() to change styles on DynLayers.
> > 
> > --
> > Raymond Irving
> > 
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built
> ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are
> available now.
> Download today and enter to win an XBOX or Visual
> Studio .NET.
>
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
>
http://www.mail-archive.com/dyn...@li.../


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

RE: [Dynapi-Dev] dynapi.util.ioelement-postresponse.php

[Raymond I. <xw...@ya...>]

You'll have to give it a try.

That's very strange though.

--
Raymond Irving

--- Daniel Tiru <de...@ti...> wrote:
> Hi all!
> 
> What i wonder is if someone have tried to load in
> images with the
> ioelement... Just show a layer with a image in?
> 
> Cause sometimes when that is done the image wont
> show, i think this is
> caused byt that the webbrowser somehow loads the
> html first and never
> displays the image... I have no good example for
> this... But can make
> one on request if you dont understand how it works.
> 
> Would the solution under here work you think? As its
> only happening if
> you make the layer and the image in the ioelement,
> and not on the
> mainpage.
> 
> Regards
> Daniel
> 
> -----Original Message-----
> From: dyn...@li...
> [mailto:dyn...@li...] On
> Behalf Of Raymond
> Irving
> Sent: den 7 augusti 2003 17:35
> To: dyn...@li...
> Subject: Re: [Dynapi-Dev]
> dynapi.util.ioelement-postresponse.php
> 
> 
> 
> Good going Leif! 
> 
> I've uploaded the vbscript and jscript versions of
> the ioelement
> server-side libraries to support the new
> wsAddJSCommand() function
> 
> wsAddJSCommand() -  This will allow JavaScript
> commands to be executed on client and should only be
> used when html content is being returned to the
> client
> 
> Please new dynapi.util.ioelement-dynamic-code.html
> example for more info on the execInParent()
> client-side function.
> 
> --
> Raymond Irving
> 
> 
> --- Leif W <war...@us...> wrote:
> > Ahh yeah that makes sense.  Some of the initial
> PHP
> > code was broken so I
> > fixed it.  I added the new code to CVS last night.
> > Sorry for not making it
> > clear.
> > 
> > Leif
> > 
> > ----- Original Message -----
> > From: "Jeremy Wanamaker" <je...@ma...>
> > To: <dyn...@li...>
> > Sent: Wednesday, August 06, 2003 2:45 PM
> > Subject: Re: [Dynapi-Dev]
> > dynapi.util.ioelement-postresponse.php
> > 
> > 
> > > Leif,
> > >
> > > I see now why we haven't been on the same page.
> > The August 6th DynAPI
> > > snapshot contains different versions of the
> > postresponse and ioelmsrv php
> > > files than the August 5th snapshot. So I was
> > pointing out a bug that had
> > > already been fixed. I do agree with you that
> > standardizing the functions
> > > between scripting languages is important to the
> > goal of DynAPI. Keep up
> > the
> > > good work.
> > >
> > > Jeremy
> > >
> > >
> > > ----- Original Message -----
> > > From: "Leif W" <war...@us...>
> > > To: <dyn...@li...>
> > > Sent: Wednesday, August 06, 2003 12:21 PM
> > > Subject: Re: [Dynapi-Dev]
> > dynapi.util.ioelement-postresponse.php
> > >
> > >
> > > > Ahh, I think I see now... there is no need to
> > use extract on $_POST or
> > > $_GET
> > > > in the example.
> > > >
> > > > In the postresponse there's two lines:
> > > >
> > > > $name = wsGetRequest( "name" );
> > > > $color = wsGetRequest( "color" );
> > > >
> > > > This is making use of the wsGetRequest
> function
> > in ioelmsrv.php.  It
> > seems
> > > > redundant, but wsGetRequest will look in
> either
> > $_GET or $_POST
> > depending
> > > on
> > > > the IOMethod used (get, post, upload {which is
> > also post}), or fallback
> > > onto
> > > > the $_SERVER['REQUEST_METHOD'].
> > > >
> > > > Agreed, there's often much more simple and
> > elegant ways of doing things
> > > > natively in PHP than in ASP's JScript and
> > VBScript or in Perl.  But the
> > > > exercise is to create the same library with
> the
> > same functions
> > available,
> > > > and the examples should use those functions.
> > Correct?  Unless I am
> > > missing
> > > > some other fine point...
> > > >
> > > > Leif
> > > >
> > > > ----- Original Message -----
> > > > From: "Jeremy Wanamaker"
> > <je...@ma...>
> > > > To: <dyn...@li...>
> > > > Sent: Wednesday, August 06, 2003 11:16 AM
> > > > Subject: Re: [Dynapi-Dev]
> > dynapi.util.ioelement-postresponse.php
> > > >
> > > >
> > > > > As it stands, the php code in
> > dynapi.util.ioelement-postresponse.php
> > > looks
> > > > > like this:
> > > > >
> > > > > <?
> > > > > // generate javascript variables
> > > > >
> > > > > echo "var response = 'Your name is $name,
> and
> > your favourite color is
> > > > > $color';";
> > > > >
> > > > > ?>
> > > > >
> > > > > The values of $name and $color are coming
> from
> > the post data. If
> > > register
> > > > > globals are turned on, $name and $color will
> > be automatically assigned
> > > > from
> > > > > the $_POST array. If register globals are
> off,
> > you have to reference
> > > these
> > > > > variable from with the $_POST array as
> > follows:
> > > > >
> > > > > echo "var response = 'Your name is
> > $_POST[name], and your favourite
> > > color
> > > > is
> > > > > $_POST[color]';";
> > > > >
> > > > > ... or you can put an
> > > > >
> > > > > extract($_POST);
> > > > >
> > > > > before the echo line. There is the potential
> > to overwrite other
> > > variables
> > > > > with extract if you are not careful. One way
> > to make sure values are
> > not
> > > > > overwritten is to use the EXTR_SKIP flag
> when
> > using extract - see
> > > > > http://php.net/extract - The first method is
> > better though. My main
> > > point
> > > > > was that in the current CVS version, the
> > variables are not referenced
> > > > > correctly if register globals are off.
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

Re: [Dynapi-Dev] The DynAPI Web Team

[Stephen C. <sca...@vi...>]

What is the role of concept designer?

----- Original Message ----- 
From: "Kevin" <ke...@ke...>
To: <dyn...@li...>
Sent: Thursday, August 07, 2003 9:13 AM
Subject: Re: [Dynapi-Dev] The DynAPI Web Team


> Raymond Irving wrote:
>
> > Hi Everyone
> >
> > So far we have the following volunteers:
> >
> > 1) Project manager
> > Joy Ride (Juhu)
> > 2) Consept designer
> > 3) Graphic designer
> > Diane Tomlins
> > 4) Programmer(s)
> > Leif W
> > C Kissinger
> > 5) Content provider(s)
> >
>
> Perhaps I can help out in a programming role.
> -
> Kevin
>
> > We need more persons to help out with this part of the
> > project. It doesn't matter how small or how great a
> > role you can play. Your time and effort is well
> > appreciated. Besides that it's just pure fun!
> >
> > We need to get this part of the project started as
> > we're planning to have DynAPI 3.0 stable (or fully
> > launched) by November.
> >
> > Are we in agreement here?
> >
> > --
> > Raymond Irving
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! SiteBuilder - Free, easy-to-use web site design software
> > http://sitebuilder.yahoo.com
> >
> >
> > -------------------------------------------------------
> > This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> > Data Reports, E-commerce, Portals, and Forums are available now.
> > Download today and enter to win an XBOX or Visual Studio .NET.
> >
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://www.mail-archive.com/dyn...@li.../
>
>

RE: [Dynapi-Dev] dynapi.util.ioelement-postresponse.php

[Daniel T. <de...@ti...>]

Hi all!

What i wonder is if someone have tried to load in images with the
ioelement... Just show a layer with a image in?

Cause sometimes when that is done the image wont show, i think this is
caused byt that the webbrowser somehow loads the html first and never
displays the image... I have no good example for this... But can make
one on request if you dont understand how it works.

Would the solution under here work you think? As its only happening if
you make the layer and the image in the ioelement, and not on the
mainpage.

Regards
Daniel

-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...] On Behalf Of Raymond
Irving
Sent: den 7 augusti 2003 17:35
To: dyn...@li...
Subject: Re: [Dynapi-Dev] dynapi.util.ioelement-postresponse.php



Good going Leif! 

I've uploaded the vbscript and jscript versions of the ioelement
server-side libraries to support the new
wsAddJSCommand() function

wsAddJSCommand() -  This will allow JavaScript
commands to be executed on client and should only be
used when html content is being returned to the client

Please new dynapi.util.ioelement-dynamic-code.html
example for more info on the execInParent()
client-side function.

--
Raymond Irving


--- Leif W <war...@us...> wrote:
> Ahh yeah that makes sense.  Some of the initial PHP
> code was broken so I
> fixed it.  I added the new code to CVS last night.
> Sorry for not making it
> clear.
> 
> Leif
> 
> ----- Original Message -----
> From: "Jeremy Wanamaker" <je...@ma...>
> To: <dyn...@li...>
> Sent: Wednesday, August 06, 2003 2:45 PM
> Subject: Re: [Dynapi-Dev]
> dynapi.util.ioelement-postresponse.php
> 
> 
> > Leif,
> >
> > I see now why we haven't been on the same page.
> The August 6th DynAPI
> > snapshot contains different versions of the
> postresponse and ioelmsrv php
> > files than the August 5th snapshot. So I was
> pointing out a bug that had
> > already been fixed. I do agree with you that
> standardizing the functions
> > between scripting languages is important to the
> goal of DynAPI. Keep up
> the
> > good work.
> >
> > Jeremy
> >
> >
> > ----- Original Message -----
> > From: "Leif W" <war...@us...>
> > To: <dyn...@li...>
> > Sent: Wednesday, August 06, 2003 12:21 PM
> > Subject: Re: [Dynapi-Dev]
> dynapi.util.ioelement-postresponse.php
> >
> >
> > > Ahh, I think I see now... there is no need to
> use extract on $_POST or
> > $_GET
> > > in the example.
> > >
> > > In the postresponse there's two lines:
> > >
> > > $name = wsGetRequest( "name" );
> > > $color = wsGetRequest( "color" );
> > >
> > > This is making use of the wsGetRequest function
> in ioelmsrv.php.  It
> seems
> > > redundant, but wsGetRequest will look in either
> $_GET or $_POST
> depending
> > on
> > > the IOMethod used (get, post, upload {which is
> also post}), or fallback
> > onto
> > > the $_SERVER['REQUEST_METHOD'].
> > >
> > > Agreed, there's often much more simple and
> elegant ways of doing things
> > > natively in PHP than in ASP's JScript and
> VBScript or in Perl.  But the
> > > exercise is to create the same library with the
> same functions
> available,
> > > and the examples should use those functions.
> Correct?  Unless I am
> > missing
> > > some other fine point...
> > >
> > > Leif
> > >
> > > ----- Original Message -----
> > > From: "Jeremy Wanamaker"
> <je...@ma...>
> > > To: <dyn...@li...>
> > > Sent: Wednesday, August 06, 2003 11:16 AM
> > > Subject: Re: [Dynapi-Dev]
> dynapi.util.ioelement-postresponse.php
> > >
> > >
> > > > As it stands, the php code in
> dynapi.util.ioelement-postresponse.php
> > looks
> > > > like this:
> > > >
> > > > <?
> > > > // generate javascript variables
> > > >
> > > > echo "var response = 'Your name is $name, and
> your favourite color is
> > > > $color';";
> > > >
> > > > ?>
> > > >
> > > > The values of $name and $color are coming from
> the post data. If
> > register
> > > > globals are turned on, $name and $color will
> be automatically assigned
> > > from
> > > > the $_POST array. If register globals are off,
> you have to reference
> > these
> > > > variable from with the $_POST array as
> follows:
> > > >
> > > > echo "var response = 'Your name is
> $_POST[name], and your favourite
> > color
> > > is
> > > > $_POST[color]';";
> > > >
> > > > ... or you can put an
> > > >
> > > > extract($_POST);
> > > >
> > > > before the echo line. There is the potential
> to overwrite other
> > variables
> > > > with extract if you are not careful. One way
> to make sure values are
> not
> > > > overwritten is to use the EXTR_SKIP flag when
> using extract - see
> > > > http://php.net/extract - The first method is
> better though. My main
> > point
> > > > was that in the current CVS version, the
> variables are not referenced
> > > > correctly if register globals are off.
> > > >
> > > > Jeremy
> > > >
> > > > ----- Original Message -----
> > > > From: "Leif W" <war...@us...>
> > > > To: <dyn...@li...>
> > > > Sent: Wednesday, August 06, 2003 10:19 AM
> > > > Subject: Re: [Dynapi-Dev]
> dynapi.util.ioelement-postresponse.php
> > > >
> > > >
> > > > > Hi,
> > > > >
> > > > > I am not sure I understand this... All the
> variables exist in $_GET,
> > > > $_POST,
> > > > > $_COOKIES, $_FILES, so in the script I
> referenced them as such.  I
> > read
> > > my
> > > > > php.ini and the manual.  The extract will
> bring all the assosciative
> > > array
> > > > > elements into the current symbol table.  But
> if you do this, isn't
> > there
> > > a
> > > > > risk of clobbering existing variables in
> use?  If the PHP script
> > exists
> > > on
> > > > a
> > > > > server, and someone can figure out which
> variable names we're using,
> > > they
> > > > > may be able to override our variables and
> gain more control of the
> > > script
> > > > > than we want.  Shouldn't we just abide by
> the default of leaving the
> > > data
> > > > in
> > > > > the $_GET, $_POST, $_COOKIES, $_FILES
> arrays, and not override the
> > > default
> > > > > behaviour of disabling the register_globals,
> and so not risk
> > > compromising
> > > > > security?
> > > > >
> > > > > Leif
> > > > >
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "Jeremy Wanamaker"
> <je...@ma...>
> > > > > To: <dyn...@li...>
> > > > > Sent: Wednesday, August 06, 2003 9:14 AM
> > > > > Subject: [Dynapi-Dev]
> dynapi.util.ioelement-postresponse.php
> > > > >
> > > > >
> > > > > > The dynapi.util.ioelement-postresponse.php
> example script will not
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01
/01
_______________________________________________
Dynapi-Dev mailing list
Dyn...@li...
http://www.mail-archive.com/dyn...@li.../

Re: [Dynapi-Dev] New Image button - cache problem.

[Kevin <ke...@ke...>]

Hi,

If the port5 domain is down I've put a copy of the example on demon:

http://www.kegcl.demon.co.uk/examples/demo.getimage3.html

-
Kevin

> Hi,
> 
> I have found an annoying problem were a cached image is still reloaded
> under some circumstance - when another window has been opened?  
> 
> http://keg.port5.com/examples/demo.getimage3.html
> 
> Click on any folder tab to open the small window.
> 
> Note mouse over/out works fine with images from cache until the new
> window is open? I was testing using IE6.
> 
> The idea is not to have 2,3 or 4 images for every button when only one
> set of cached images is needed and just change the label for each button.
> 
> So for a 3 image x 10 menu buttons example only 3 images not 30 are
> downloaded - a nice saving in bandwidth!
> 
> If only it worked - any help on caching problems would be appreciated.
> 
> -
> Kevin
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../

Re: [Dynapi-Dev] The DynAPI Web Team

[Kevin <ke...@ke...>]

Raymond Irving wrote:

> Hi Everyone
> 
> So far we have the following volunteers:
> 
> 1) Project manager
> Joy Ride (Juhu)
> 2) Consept designer
> 3) Graphic designer
> Diane Tomlins
> 4) Programmer(s)
> Leif W
> C Kissinger
> 5) Content provider(s)
>

Perhaps I can help out in a programming role.
-
Kevin
 
> We need more persons to help out with this part of the
> project. It doesn't matter how small or how great a
> role you can play. Your time and effort is well
> appreciated. Besides that it's just pure fun! 
> 
> We need to get this part of the project started as
> we're planning to have DynAPI 3.0 stable (or fully
> launched) by November.
> 
> Are we in agreement here?
> 
> --
> Raymond Irving
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../

Re: [Dynapi-Dev] Introducing the StyleManager

[Kevin <ke...@ke...>]

Raymond wrote:

> The StyleManager is not about CSS. It's about being
> able to apply javascript functions to an exiting
> widget to modify it's functions, change it's look and
> it's behavior.
> 
> For example you can use the StyleManager to convert an
> ordinary DynLayer into a button widget by just
> applying the "ButtonStyle". Later you could then
> change that layer into a ProgressBar by just applying
> the "ProgressBarStyle".
> 
> IMO it's a completely modular and fashionable way to
> design DynAPI widgets. With StyleManager a basic
> widget can be morphed into another widget by just
> simply changing the style.

My thinking is:

button1=new Button()
button1.setHighLight(...)
progressbar1=new ProgressBar()
progressbar1.setScale(...)
...
Morph button1 to a progressbar
...
button1.setScale(..) ?

How would we know button1 has new methods as
setScale() was before meaningless for a button?

button1 and progessbar1 are instances of their own class
with separate attributes and methods. Morphing button1
to a progressbar? Ok fine, but morphing 'setStyle(...) or
maybe setMorph(...)' is not a method of either class but
more a method of a management class not related to (or
inherited from) a DynLayer.

Perhaps an example would help in understanding what is
intended in an OOP context. Thanks.

-
Kevin.

> > With an established interface it is preferable to
> > add to,
> > rather than change and break backward compatibility
> 
> Ok, I guess we'll just keep the 7th argument and use
> setStyle() to change styles on DynLayers.
> 
> --
> Raymond Irving
>