Menu
▾
▴
dynapi-dev — List related to the current DynAPI Core development
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: Michael P. <mp...@ph...> - 2001-01-05 14:34:35
|
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
You may also find it interesting that individual files can be referred
to with as many subdirectories as you want. This is one of the advantages
of using an array rather than a fixed search system.
<p>Michael Pemberton wrote:
<blockquote TYPE=CITE>I was looking at a way of making the DynAPI.include
method more simple. Here's what I came up with:
<p><tt>include : function(src,path) {</tt>
<br><tt> srcArray = src.split('.');</tt>
<br><tt> if (!path) var path=DynAPI.librarypath;</tt>
<br><tt> var pckg=srcArray[0];</tt>
<br><tt> var grp=srcArray[1];</tt>
<br><tt> var file=srcArray[2];</tt>
<br><tt> if (file=='*') {</tt>
<br><tt> if (DynAPI.packages[pckg]) group=DynAPI.packages[pckg][grp];</tt>
<br><tt> if (group) for (var i in group) document.write('<script
language="Javascript1.2" src="'+path+pckg+'/'+grp+'/'+group[i]+'.js"><\/script>');</tt>
<br><tt> else alert('include()\n\nThe following package
could not be loaded:\n'+src+'\n\nmake sure you specified the correct path.');</tt>
<br><tt> } else {</tt>
<br><tt> if (path[path.length-1] != "/") path +=
"/";</tt>
<br><tt> document.write('<script language="Javascript1.2"
src="'+path+srcArray.join('/')+'.js"><\/script>');</tt>
<br><tt> };</tt>
<br><tt>}</tt>
<p>This way, there is no more searching for '.' over and over again.
<br>Also, you can now refer to individual files (even you own external
files) using '.' instead of '/'. This way, it fits the library syntax.
Hope this is of some use.
<p>Robert Rainwater wrote:
<blockquote TYPE=CITE>I've updated my current version to do this for a
while, but just haven't put
<br>it in CVS. I will update CVS soon so that the include will work
that way.
<p>Robert
<br>----- Original Message -----
<br>From: "Michael Bürge" <mb...@st...>
<br>To: <dyn...@li...>
<br>Sent: Tuesday, January 02, 2001 6:58 PM
<br>Subject: [Dynapi-Dev] DynAPI.include()
<p>> hi there.
<br>>
<br>> this is my first post to this list, and i would like to use the
<br>opportunity to thank you for the great work you're all doing. i just
started
<br>dealing with
<br>> the dynapi after having spent a _lot_ of time putting together something
<br>similar on my own (i now finally gave up, mainly because it's just
way too
<br>much
<br>> work keeping everything up to date).
<br>>
<br>> now to the real issue of this post:
<br>>
<br>> the following is an excerpt from part 1 one of the tutorials written
by
<br>Pascal, describing the include() function:
<br>>
<br>> * DynAPI.include('myownfile.js','location/path')
<br>> Include your own file not located in the [dynapi base path] location
<br>> * DynAPI.include('myownfile.js','./')
<br>> Include your own file located at the current file location.
<br>>
<br>> i like these features, so i tried to use them bu it didn't work.
looking
<br>at the code i realised that they weren't implemented at all. i don't
know if
<br>> somebody did already implement them, but both the current distro
and the
<br>current CVS-version do not contain them.
<br>> so here's my version:
<br>>
<br>> include : function(src,path) {
<br>> if(src.substring(src.length-3)!=".js") src+=".js";
<br>> if (!path) var path=DynAPI.librarypath;
<br>> else {
<br>> if (path=="./") path = "";
<br>> else if (path[path.length-1]
!= "/") path += "/";
<br>> document.write('<script language="Javascript1.2"
src="'+ path + src
<br>+ '"></script>');
<br>> return;
<br>> }
<br>> ....some more stuff....
<br>> }
<br>>
<br>> hope this is usefull, and sorry if i missed the version containing
those
<br>features. (BTW: is was pretty hard for me to find out where to get
the
<br>current
<br>> files, so a few hints on the project-webpage would save a great deal
of
<br>time to people interested in looking at the current work going on)
<br>>
<br>> that all for now.
<br>> greets.
<br>> michael buerge
<br>>
<br>>
<br>> _______________________________________________
<br>> Dynapi-Dev mailing list
<br>> Dyn...@li...
<br>> <a href="http://lists.sourceforge.net/mailman/listinfo/dynapi-dev">http://lists.sourceforge.net/mailman/listinfo/dynapi-dev</a>
<p>_______________________________________________
<br>Dynapi-Dev mailing list
<br>Dyn...@li...
<br><a href="http://lists.sourceforge.net/mailman/listinfo/dynapi-dev">http://lists.sourceforge.net/mailman/listinfo/dynapi-dev</a></blockquote>
_______________________________________________ Dynapi-Dev mailing list
Dyn...@li... <A HREF="http://lists.sourceforge.net/mailman/listinfo/dynapi-dev">http://lists.sourceforge.net/mailman/listinfo/dynapi-dev</A></blockquote>
</html>
|
|
From: Michael P. <mp...@ph...> - 2001-01-05 14:23:18
|
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
I was looking at a way of making the DynAPI.include method more simple.
Here's what I came up with:
<p><tt>include : function(src,path) {</tt>
<br><tt> srcArray = src.split('.');</tt>
<br><tt> if (!path) var path=DynAPI.librarypath;</tt>
<br><tt> var pckg=srcArray[0];</tt>
<br><tt> var grp=srcArray[1];</tt>
<br><tt> var file=srcArray[2];</tt>
<br><tt> if (file=='*') {</tt>
<br><tt> if (DynAPI.packages[pckg]) group=DynAPI.packages[pckg][grp];</tt>
<br><tt> if (group) for (var i in group) document.write('<script
language="Javascript1.2" src="'+path+pckg+'/'+grp+'/'+group[i]+'.js"><\/script>');</tt>
<br><tt> else alert('include()\n\nThe following package
could not be loaded:\n'+src+'\n\nmake sure you specified the correct path.');</tt>
<br><tt> } else {</tt>
<br><tt> if (path[path.length-1] != "/") path +=
"/";</tt>
<br><tt> document.write('<script language="Javascript1.2"
src="'+path+srcArray.join('/')+'.js"><\/script>');</tt>
<br><tt> };</tt>
<br><tt>}</tt>
<p>This way, there is no more searching for '.' over and over again.
<br>Also, you can now refer to individual files (even you own external
files) using '.' instead of '/'. This way, it fits the library syntax.
Hope this is of some use.
<p>Robert Rainwater wrote:
<blockquote TYPE=CITE>I've updated my current version to do this for a
while, but just haven't put
<br>it in CVS. I will update CVS soon so that the include will work
that way.
<p>Robert
<br>----- Original Message -----
<br>From: "Michael Bürge" <mb...@st...>
<br>To: <dyn...@li...>
<br>Sent: Tuesday, January 02, 2001 6:58 PM
<br>Subject: [Dynapi-Dev] DynAPI.include()
<p>> hi there.
<br>>
<br>> this is my first post to this list, and i would like to use the
<br>opportunity to thank you for the great work you're all doing. i just
started
<br>dealing with
<br>> the dynapi after having spent a _lot_ of time putting together something
<br>similar on my own (i now finally gave up, mainly because it's just
way too
<br>much
<br>> work keeping everything up to date).
<br>>
<br>> now to the real issue of this post:
<br>>
<br>> the following is an excerpt from part 1 one of the tutorials written
by
<br>Pascal, describing the include() function:
<br>>
<br>> * DynAPI.include('myownfile.js','location/path')
<br>> Include your own file not located in the [dynapi base path] location
<br>> * DynAPI.include('myownfile.js','./')
<br>> Include your own file located at the current file location.
<br>>
<br>> i like these features, so i tried to use them bu it didn't work.
looking
<br>at the code i realised that they weren't implemented at all. i don't
know if
<br>> somebody did already implement them, but both the current distro
and the
<br>current CVS-version do not contain them.
<br>> so here's my version:
<br>>
<br>> include : function(src,path) {
<br>> if(src.substring(src.length-3)!=".js") src+=".js";
<br>> if (!path) var path=DynAPI.librarypath;
<br>> else {
<br>> if (path=="./") path = "";
<br>> else if (path[path.length-1]
!= "/") path += "/";
<br>> document.write('<script language="Javascript1.2"
src="'+ path + src
<br>+ '"></script>');
<br>> return;
<br>> }
<br>> ....some more stuff....
<br>> }
<br>>
<br>> hope this is usefull, and sorry if i missed the version containing
those
<br>features. (BTW: is was pretty hard for me to find out where to get
the
<br>current
<br>> files, so a few hints on the project-webpage would save a great deal
of
<br>time to people interested in looking at the current work going on)
<br>>
<br>> that all for now.
<br>> greets.
<br>> michael buerge
<br>>
<br>>
<br>> _______________________________________________
<br>> Dynapi-Dev mailing list
<br>> Dyn...@li...
<br>> <a href="http://lists.sourceforge.net/mailman/listinfo/dynapi-dev">http://lists.sourceforge.net/mailman/listinfo/dynapi-dev</a>
<p>_______________________________________________
<br>Dynapi-Dev mailing list
<br>Dyn...@li...
<br><a href="http://lists.sourceforge.net/mailman/listinfo/dynapi-dev">http://lists.sourceforge.net/mailman/listinfo/dynapi-dev</a></blockquote>
</html>
|
|
From: Gino M. <gin...@br...> - 2001-01-05 13:08:52
|
Please do! I just joined the list yesterday, and while my project doesn't use inline creation, I know of others where I work that would benefit from this. Thanks, Gino > -----Original Message----- > From: Pascal [mailto:pb...@oi...] > Sent: Friday, January 05, 2001 2:40 AM > To: dyn...@li... > Subject: RE: [Dynapi-Dev] Snapshot broken > > > I posted a fix a few days ago for the inline creation, making > it work under > IE5+ and Mozilla.. haven't tested IE4. > > If you want I can post it again when I get home. > > > Pascal Bestebroer (pb...@oi...) > Software ontwikkelaar > Oberon Informatiesystemen b.v. > http://www.oibv.com > > > -----Oorspronkelijk bericht----- > > Van: dyn...@li... > > [mailto:dyn...@li...]Namens > Robert Rainwater > > Verzonden: donderdag 4 januari 2001 19:29 > > Aan: dyn...@li... > > Onderwerp: Re: [Dynapi-Dev] Snapshot broken > > > > > > I can do that in a few days. There a few updates I need to > > make to CVS > > though. > > > > Like the include bug and the loadQueue array bug. Hopefully, > > I will have > > the release ready in a few days. I'll post a release > > candidate first and > > then after some testing, I'll post a new release on Sourceforge. > > > > Also, if anyone knows of any other bug fixes, please let me > > know (I think > > there was one in the inlinecreation). Does the inline > > creation work in IE > > yet? I noticed the getOuterHTML for IE is empty. > > > > Robert Rainwater > > > > ----- Original Message ----- > > From: "Pascal Bestebroer" <pa...@dy...> > > To: <dyn...@li...> > > Sent: Thursday, January 04, 2001 1:09 PM > > Subject: RE: [Dynapi-Dev] Snapshot broken > > > > > > > Yes there have been changes made to the DynAPI code in two > > months, but the > > > release version was a stable one ,working. The major things > > done in the > > last > > > two months are widgets and modifications of old code, not > > new code. So I > > > don't think the release is an obsolete version.. it works. > > > > > > One idea is that maybe one of the admins (not me) can take > > the current > > code > > > and create one new release out of it (fixing known bugs but > > do nothing > > else > > > with it, not adding any new code posted in this list) this > > should give a > > new > > > updated release version containing the new widgets (and > > style) and the > > > current code. > > > > > > Anybody up for it :-) > > > > > > > > > Pascal Bestebroer > > > pa...@dy... > > > http://www.dynamic-core.net > > > > > > > -----Oorspronkelijk bericht----- > > > > Van: dyn...@li... > > > > [mailto:dyn...@li...]Namens > Peter Curran > > > > Verzonden: donderdag 4 januari 2001 18:44 > > > > Aan: dyn...@li... > > > > Onderwerp: Re: [Dynapi-Dev] Snapshot broken > > > > > > > > > > > > At 09:14 AM 04/01/01 -0800, "Robert Rainwater" > > > > <rra...@ya...> wrote: > > > > ><snip> > > > > >I would be hesitant to post a link on the site, since > > most developers > > and > > > > >testers are subscribed to this list. Putting a link > on the site > > > > would cause > > > > >people to download it and use it as final code. > > > > > > > > > >Robert Rainwater > > > > > > > > But what choice is there? The current "release" is nearly > > two months > > old. > > > > We know there have been a tremendous number of bug fixes, > > > > enhancements, and > > > > style changes since then. People really only have a choice of > > > > using a very > > > > old and substantially obsolete "release," or the current code. > > > > > > > > This is not meant as a criticism - obviously, this is free code, > > > > people are > > > > doing the best they can, following their own > priorities, etc. But > > > > the fact > > > > remains that releases aren't happening, and are very > difficult to > > arrange > > > > in this style of development. > > > > > > > > Unless the developers institute such practices as code freezes, > > > > bug-fix-only periods, extensive testing, etc., there is never > > > > likely to be > > > > a "stable" version for use as a new release. This type of > > > > development will > > > > always have segments under active development (until the > > code becomes > > > > obsolete and development stops). > > > > > > > > Unless you are planning some kind of active process to bring > > > > about a stable > > > > code package that can be a new release, the new code is really > > > > all that is > > > > available. > > > > > > > > > > > > -- > > > > Peter Curran Software Developer Casebank > Technologies Inc. > > > > pc...@ca... 905 > 792-0618 X535 > > > > > > > > > > > > _______________________________________________ > > > > Dynapi-Dev mailing list > > > > Dyn...@li... > > > > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > > > > > > > > > > > > _______________________________________________ > > > Dynapi-Dev mailing list > > > Dyn...@li... > > > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > > > > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > |
|
From: <cam...@ya...> - 2001-01-05 10:50:50
|
This is an old thread, but I just found a (kind of)problem with IlMaestro's solution. The obvious way to set the html to '' is to call setHTML. However setHTML invokes a load event, which is not desirable behaviour when you are destroying the layer (particularly if you are listening for these load events). If setHTML could be passed a second parameter to tell it not to invoke events (like setSize) then this wouldn't be a problem. The other problem with setting the HTML to '' is if you have a layer with lots of children you can visibly see netscape rerendering each layer. So perhaps the layer should be hidden before the setHTML happens. I've found that setting the layer HTML to null when destroying layers greatly improved netscapes stability. I think it's definetly worth adding to the API. I could have a go at it myself but I don't have access to CVS, how should I submit any changes I've made? --- Jordi 'IlMaestro' Ministral <jmi...@or...> wrote: > Netscape does not allow physical layers to be > destroyed. Therefore DynAPI > simply hides the layer and adds it to a temporary > array. Any layer created > after this will make the API reuse one of the > deleted ones, and then content > will be overriden and thus the flash movie > destroyed. Simply set the HTML > content of the layer to "" before destroying it and > you will destroy the flash > movie. > > I'll update the API's delete() method so it does it, > but in the meantime you'll > have to do it in your own code. > > Cya > > > Cameron Hart wrote: > > > I've discovered a problem with a site I'm building > at the moment. I'm using > > layers that contain flash movies. These layers can > be created and destroyed > > an unlimited number of times while using the site. > I discoved that when I > > put a flash movie on a layer that contains sound, > in netscape i can still > > hear the movie playing after i've destroyed the > layer containing the flash > > movie. > > > > So it appears that Netscape is not destroying the > contents of the DynLayer. > > > > I suspect that it is not only flash that this is > happening with. Perhaps > > other content is not being destroyed either. > > > > Has anyone come across this before? > > > > Thanks, > > > > Cameron. > > > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > __________________________________________________ Do You Yahoo!? Yahoo! Photos - Share your holiday photos online! http://photos.yahoo.com/ |
|
From: <cam...@ya...> - 2001-01-05 10:32:08
|
> > Why not just capture the onload event. Thats why > it is > > invoked there. Or > > am I missing something here? I've had lots of problems with the onload in LoadPanel. Mostly in Netscape. The problem is I think Netscape fires an onload event before it renders the HTML. So if you try and get the contentHeight of the LoadPanel onload it is often 0 in Netscape. This doesn't happen in the sample that is in the snapshot, but it does as soon as you start loading largish pages into the LoadPanel. Of course this doesn't solve the problem below... One question Mark, are you resizing the LoadPanel in your onload handler? > No - I think that I was missing something :). I > added an onload event listener for the panel and > that works like a charm...except in IE (5.00) the > event gets called twice for some reason. I haven't > been able to track it down yet. It doesn't seem to > be a big deal other than viewing my widget resize > twice before the content is displayed in the panel. > It's strange cause when I create a panel, I initally > have to set the size to my layer's wxh. Then, when > the onload event occurs I see the panel getting > resized (in IE) to my layer's wxh, then again to the > content height. I added a fix in my onload function > for IE that says: > > if (is.ie && e.getSource().isReloading == null) > return; > > but this seems like kinda of hack. > > On a side note, the widget I'm creating is a wizard > (which I need to use for a current project that I'm > working on). I'd eventually like to contribute this > to the dyanpi project. How can I go about this ?? > > thanks, > > > -Mark Haviland > ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÃÊv©ðÞ¾f¢)à+-)Ú¦/ÃzÿåËlþÊ.Ç¢¸ þwÛiÿÿåËlþÊ.Ç¢¸ þwþf¢f§þX¬¶)ߣ÷rªbýׯ > > __________________________________________________ Do You Yahoo!? Yahoo! Photos - Share your holiday photos online! http://photos.yahoo.com/ |
|
From: Scott B. <sco...@se...> - 2001-01-05 08:47:50
|
Hi,
I have just joined the list so forgive me if this has already been
discussed.
The scroll window and menulist don't seem to work too well in IE 5.5, is
this just
me or have other people had this problem as well?
Yours sincerely,
Scott Bristowe
|
|
From: Raymond S. <dst...@or...> - 2001-01-05 07:43:40
|
Robert,
I posted this prior. Not sure if my solution is the cleanest, but it
worked. Basically if you set a negative variable in setAngleIncrement to
reverse circle animation 'then' use generatePath method IE5 or IE 5.5 freeze
up solid. Fix below and attached.
POSTED PRIOR____________________________________________________________
If you generated a path with a (-) negative number in setAngleIncrement
method (to allow you to determine direction, clockwise(-) or counter
clockwise(+) it would freeze up during this line "for (var
a=this.angle;a<=this.angle+Math.PI*2;a+=this.angleinc) {" in the
generatePath method of circle.js. This method is critical because it allows
you to inherit both 'loop' and 'reset' functionality from pathanim.js and
have some real fun. Now you setAngleIncrement as a positive for speed and
use setDirection (+ or - 1) to set path direction. Tested in both IE and NS
on WinME.
added/changed the following lines. Full js file attached.
____________________________________________________________________________
____________
this.direction = 1
CircleAnimation.prototype.setDirection = function (d) {
this.direction = d;
CircleAnimation.prototype.generatePath = function(centerX,centerY) {
if (centerX==null) centerX = this.dlyr!=null? this.dlyr.x : 0;
if (centerY==null) centerY = this.dlyr!=null? this.dlyr.y : 0;
var path = [];
var i = 0;
for (var a=this.angle;a<=this.angle+Math.PI*2;a+=this.angleinc) {
path[i] = Math.round(centerX + this.hradius*Math.cos(this.direction*a));
path[i+1] = Math.round(centerY - this.vradius*Math.sin(this.direction*a));
i+=2;
}
return path;
};
____________________________________________________________________________
____________
cheers,
Ray
----- Original Message -----
From: "Robert Rainwater" <rra...@ya...>
To: <dyn...@li...>
Sent: Thursday, January 04, 2001 10:28 AM
Subject: Re: [Dynapi-Dev] Snapshot broken
> I can do that in a few days. There a few updates I need to make to CVS
> though.
>
> Like the include bug and the loadQueue array bug. Hopefully, I will have
> the release ready in a few days. I'll post a release candidate first and
> then after some testing, I'll post a new release on Sourceforge.
>
> Also, if anyone knows of any other bug fixes, please let me know (I think
> there was one in the inlinecreation). Does the inline creation work in IE
> yet? I noticed the getOuterHTML for IE is empty.
>
> Robert Rainwater
>
> ----- Original Message -----
> From: "Pascal Bestebroer" <pa...@dy...>
> To: <dyn...@li...>
> Sent: Thursday, January 04, 2001 1:09 PM
> Subject: RE: [Dynapi-Dev] Snapshot broken
>
>
> > Yes there have been changes made to the DynAPI code in two months, but
the
> > release version was a stable one ,working. The major things done in the
> last
> > two months are widgets and modifications of old code, not new code. So I
> > don't think the release is an obsolete version.. it works.
> >
> > One idea is that maybe one of the admins (not me) can take the current
> code
> > and create one new release out of it (fixing known bugs but do nothing
> else
> > with it, not adding any new code posted in this list) this should give a
> new
> > updated release version containing the new widgets (and style) and the
> > current code.
> >
> > Anybody up for it :-)
> >
> >
> > Pascal Bestebroer
> > pa...@dy...
> > http://www.dynamic-core.net
> >
> > > -----Oorspronkelijk bericht-----
> > > Van: dyn...@li...
> > > [mailto:dyn...@li...]Namens Peter Curran
> > > Verzonden: donderdag 4 januari 2001 18:44
> > > Aan: dyn...@li...
> > > Onderwerp: Re: [Dynapi-Dev] Snapshot broken
> > >
> > >
> > > At 09:14 AM 04/01/01 -0800, "Robert Rainwater"
> > > <rra...@ya...> wrote:
> > > ><snip>
> > > >I would be hesitant to post a link on the site, since most developers
> and
> > > >testers are subscribed to this list. Putting a link on the site
> > > would cause
> > > >people to download it and use it as final code.
> > > >
> > > >Robert Rainwater
> > >
> > > But what choice is there? The current "release" is nearly two months
> old.
> > > We know there have been a tremendous number of bug fixes,
> > > enhancements, and
> > > style changes since then. People really only have a choice of
> > > using a very
> > > old and substantially obsolete "release," or the current code.
> > >
> > > This is not meant as a criticism - obviously, this is free code,
> > > people are
> > > doing the best they can, following their own priorities, etc. But
> > > the fact
> > > remains that releases aren't happening, and are very difficult to
> arrange
> > > in this style of development.
> > >
> > > Unless the developers institute such practices as code freezes,
> > > bug-fix-only periods, extensive testing, etc., there is never
> > > likely to be
> > > a "stable" version for use as a new release. This type of
> > > development will
> > > always have segments under active development (until the code becomes
> > > obsolete and development stops).
> > >
> > > Unless you are planning some kind of active process to bring
> > > about a stable
> > > code package that can be a new release, the new code is really
> > > all that is
> > > available.
> > >
> > >
> > > --
> > > Peter Curran Software Developer Casebank Technologies Inc.
> > > pc...@ca... 905 792-0618 X535
> > >
> > >
> > > _______________________________________________
> > > Dynapi-Dev mailing list
> > > Dyn...@li...
> > > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
> > >
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>
|
|
From: Pascal <pb...@oi...> - 2001-01-05 07:40:22
|
I posted a fix a few days ago for the inline creation, making it work under IE5+ and Mozilla.. haven't tested IE4. If you want I can post it again when I get home. Pascal Bestebroer (pb...@oi...) Software ontwikkelaar Oberon Informatiesystemen b.v. http://www.oibv.com > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Robert Rainwater > Verzonden: donderdag 4 januari 2001 19:29 > Aan: dyn...@li... > Onderwerp: Re: [Dynapi-Dev] Snapshot broken > > > I can do that in a few days. There a few updates I need to > make to CVS > though. > > Like the include bug and the loadQueue array bug. Hopefully, > I will have > the release ready in a few days. I'll post a release > candidate first and > then after some testing, I'll post a new release on Sourceforge. > > Also, if anyone knows of any other bug fixes, please let me > know (I think > there was one in the inlinecreation). Does the inline > creation work in IE > yet? I noticed the getOuterHTML for IE is empty. > > Robert Rainwater > > ----- Original Message ----- > From: "Pascal Bestebroer" <pa...@dy...> > To: <dyn...@li...> > Sent: Thursday, January 04, 2001 1:09 PM > Subject: RE: [Dynapi-Dev] Snapshot broken > > > > Yes there have been changes made to the DynAPI code in two > months, but the > > release version was a stable one ,working. The major things > done in the > last > > two months are widgets and modifications of old code, not > new code. So I > > don't think the release is an obsolete version.. it works. > > > > One idea is that maybe one of the admins (not me) can take > the current > code > > and create one new release out of it (fixing known bugs but > do nothing > else > > with it, not adding any new code posted in this list) this > should give a > new > > updated release version containing the new widgets (and > style) and the > > current code. > > > > Anybody up for it :-) > > > > > > Pascal Bestebroer > > pa...@dy... > > http://www.dynamic-core.net > > > > > -----Oorspronkelijk bericht----- > > > Van: dyn...@li... > > > [mailto:dyn...@li...]Namens Peter Curran > > > Verzonden: donderdag 4 januari 2001 18:44 > > > Aan: dyn...@li... > > > Onderwerp: Re: [Dynapi-Dev] Snapshot broken > > > > > > > > > At 09:14 AM 04/01/01 -0800, "Robert Rainwater" > > > <rra...@ya...> wrote: > > > ><snip> > > > >I would be hesitant to post a link on the site, since > most developers > and > > > >testers are subscribed to this list. Putting a link on the site > > > would cause > > > >people to download it and use it as final code. > > > > > > > >Robert Rainwater > > > > > > But what choice is there? The current "release" is nearly > two months > old. > > > We know there have been a tremendous number of bug fixes, > > > enhancements, and > > > style changes since then. People really only have a choice of > > > using a very > > > old and substantially obsolete "release," or the current code. > > > > > > This is not meant as a criticism - obviously, this is free code, > > > people are > > > doing the best they can, following their own priorities, etc. But > > > the fact > > > remains that releases aren't happening, and are very difficult to > arrange > > > in this style of development. > > > > > > Unless the developers institute such practices as code freezes, > > > bug-fix-only periods, extensive testing, etc., there is never > > > likely to be > > > a "stable" version for use as a new release. This type of > > > development will > > > always have segments under active development (until the > code becomes > > > obsolete and development stops). > > > > > > Unless you are planning some kind of active process to bring > > > about a stable > > > code package that can be a new release, the new code is really > > > all that is > > > available. > > > > > > > > > -- > > > Peter Curran Software Developer Casebank Technologies Inc. > > > pc...@ca... 905 792-0618 X535 > > > > > > > > > _______________________________________________ > > > Dynapi-Dev mailing list > > > Dyn...@li... > > > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > > > > > > > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > |
|
From: Robert R. <rra...@ya...> - 2001-01-05 01:05:38
|
I can do that in a few days. There a few updates I need to make to CVS though. Like the include bug and the loadQueue array bug. Hopefully, I will have the release ready in a few days. I'll post a release candidate first and then after some testing, I'll post a new release on Sourceforge. Also, if anyone knows of any other bug fixes, please let me know (I think there was one in the inlinecreation). Does the inline creation work in IE yet? I noticed the getOuterHTML for IE is empty. Robert Rainwater ----- Original Message ----- From: "Pascal Bestebroer" <pa...@dy...> To: <dyn...@li...> Sent: Thursday, January 04, 2001 1:09 PM Subject: RE: [Dynapi-Dev] Snapshot broken > Yes there have been changes made to the DynAPI code in two months, but the > release version was a stable one ,working. The major things done in the last > two months are widgets and modifications of old code, not new code. So I > don't think the release is an obsolete version.. it works. > > One idea is that maybe one of the admins (not me) can take the current code > and create one new release out of it (fixing known bugs but do nothing else > with it, not adding any new code posted in this list) this should give a new > updated release version containing the new widgets (and style) and the > current code. > > Anybody up for it :-) > > > Pascal Bestebroer > pa...@dy... > http://www.dynamic-core.net > > > -----Oorspronkelijk bericht----- > > Van: dyn...@li... > > [mailto:dyn...@li...]Namens Peter Curran > > Verzonden: donderdag 4 januari 2001 18:44 > > Aan: dyn...@li... > > Onderwerp: Re: [Dynapi-Dev] Snapshot broken > > > > > > At 09:14 AM 04/01/01 -0800, "Robert Rainwater" > > <rra...@ya...> wrote: > > ><snip> > > >I would be hesitant to post a link on the site, since most developers and > > >testers are subscribed to this list. Putting a link on the site > > would cause > > >people to download it and use it as final code. > > > > > >Robert Rainwater > > > > But what choice is there? The current "release" is nearly two months old. > > We know there have been a tremendous number of bug fixes, > > enhancements, and > > style changes since then. People really only have a choice of > > using a very > > old and substantially obsolete "release," or the current code. > > > > This is not meant as a criticism - obviously, this is free code, > > people are > > doing the best they can, following their own priorities, etc. But > > the fact > > remains that releases aren't happening, and are very difficult to arrange > > in this style of development. > > > > Unless the developers institute such practices as code freezes, > > bug-fix-only periods, extensive testing, etc., there is never > > likely to be > > a "stable" version for use as a new release. This type of > > development will > > always have segments under active development (until the code becomes > > obsolete and development stops). > > > > Unless you are planning some kind of active process to bring > > about a stable > > code package that can be a new release, the new code is really > > all that is > > available. > > > > > > -- > > Peter Curran Software Developer Casebank Technologies Inc. > > pc...@ca... 905 792-0618 X535 > > > > > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
|
From: Pascal B. <pa...@dy...> - 2001-01-04 18:36:19
|
And also, the guy/girl/admin creating the new release might also want to take a look at my latest release.. it contains alot of little changes and updates, and a new set of tutorials + developer reference.. which need some minor changing to make them DynAPI2 compatible but should provide alot of help for new developers. Pascal Bestebroer pa...@dy... http://www.dynamic-core.net > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Scott Andrew > LePera > Verzonden: donderdag 4 januari 2001 19:23 > Aan: dyn...@li... > Onderwerp: Re: [Dynapi-Dev] Snapshot broken > > > I'd like to mention that, in my experience, patches posted to this list > tend to get lost in the sheer volume of messages. If you have patches > that improve the overall API, don't forget to post them to sourceforge > too. > > scottandrew > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > |
|
From: Scott A. L. <sc...@sc...> - 2001-01-04 18:22:22
|
I'd like to mention that, in my experience, patches posted to this list tend to get lost in the sheer volume of messages. If you have patches that improve the overall API, don't forget to post them to sourceforge too. scottandrew |
|
From: Pascal B. <pa...@dy...> - 2001-01-04 18:04:55
|
Yes there have been changes made to the DynAPI code in two months, but the release version was a stable one ,working. The major things done in the last two months are widgets and modifications of old code, not new code. So I don't think the release is an obsolete version.. it works. One idea is that maybe one of the admins (not me) can take the current code and create one new release out of it (fixing known bugs but do nothing else with it, not adding any new code posted in this list) this should give a new updated release version containing the new widgets (and style) and the current code. Anybody up for it :-) Pascal Bestebroer pa...@dy... http://www.dynamic-core.net > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Peter Curran > Verzonden: donderdag 4 januari 2001 18:44 > Aan: dyn...@li... > Onderwerp: Re: [Dynapi-Dev] Snapshot broken > > > At 09:14 AM 04/01/01 -0800, "Robert Rainwater" > <rra...@ya...> wrote: > ><snip> > >I would be hesitant to post a link on the site, since most developers and > >testers are subscribed to this list. Putting a link on the site > would cause > >people to download it and use it as final code. > > > >Robert Rainwater > > But what choice is there? The current "release" is nearly two months old. > We know there have been a tremendous number of bug fixes, > enhancements, and > style changes since then. People really only have a choice of > using a very > old and substantially obsolete "release," or the current code. > > This is not meant as a criticism - obviously, this is free code, > people are > doing the best they can, following their own priorities, etc. But > the fact > remains that releases aren't happening, and are very difficult to arrange > in this style of development. > > Unless the developers institute such practices as code freezes, > bug-fix-only periods, extensive testing, etc., there is never > likely to be > a "stable" version for use as a new release. This type of > development will > always have segments under active development (until the code becomes > obsolete and development stops). > > Unless you are planning some kind of active process to bring > about a stable > code package that can be a new release, the new code is really > all that is > available. > > > -- > Peter Curran Software Developer Casebank Technologies Inc. > pc...@ca... 905 792-0618 X535 > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > |
|
From: Peter C. <pc...@ca...> - 2001-01-04 17:47:25
|
At 09:14 AM 04/01/01 -0800, "Robert Rainwater" <rra...@ya...> wrote: ><snip> >I would be hesitant to post a link on the site, since most developers and >testers are subscribed to this list. Putting a link on the site would cause >people to download it and use it as final code. > >Robert Rainwater But what choice is there? The current "release" is nearly two months old. We know there have been a tremendous number of bug fixes, enhancements, and style changes since then. People really only have a choice of using a very old and substantially obsolete "release," or the current code. This is not meant as a criticism - obviously, this is free code, people are doing the best they can, following their own priorities, etc. But the fact remains that releases aren't happening, and are very difficult to arrange in this style of development. Unless the developers institute such practices as code freezes, bug-fix-only periods, extensive testing, etc., there is never likely to be a "stable" version for use as a new release. This type of development will always have segments under active development (until the code becomes obsolete and development stops). Unless you are planning some kind of active process to bring about a stable code package that can be a new release, the new code is really all that is available. -- Peter Curran Software Developer Casebank Technologies Inc. pc...@ca... 905 792-0618 X535 |
|
From: Mark H. <mha...@ha...> - 2001-01-04 17:12:22
|
DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogZHluYXBpLWRldi1hZG1p bkBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQNCj4gW21haWx0bzpkeW5hcGktZGV2LWFkbWluQGxpc3Rz LnNvdXJjZWZvcmdlLm5ldF1PbiBCZWhhbGYgT2YgUm9iZXJ0DQo+IFJhaW53YXRlcg0KPiBTZW50 OiBXZWRuZXNkYXksIEphbnVhcnkgMDMsIDIwMDEgNjo0NyBQTQ0KPiBUbzogZHluYXBpLWRldkBs aXN0cy5zb3VyY2Vmb3JnZS5uZXQNCj4gU3ViamVjdDogUmU6IFtEeW5hcGktRGV2XSBsb2FkcGFu ZWwgdHJvdWJsZXMuLi4NCj4gDQo+IA0KPiBXaHkgbm90IGp1c3QgY2FwdHVyZSB0aGUgb25sb2Fk IGV2ZW50LiAgVGhhdHMgd2h5IGl0IGlzIA0KPiBpbnZva2VkIHRoZXJlLiAgT3INCj4gYW0gSSBt aXNzaW5nIHNvbWV0aGluZyBoZXJlPw0KDQpObyAtIEkgdGhpbmsgdGhhdCBJIHdhcyBtaXNzaW5n IHNvbWV0aGluZyA6KS4gIEkgYWRkZWQgYW4gb25sb2FkIGV2ZW50IGxpc3RlbmVyIGZvciB0aGUg cGFuZWwgYW5kIHRoYXQgd29ya3MgbGlrZSBhIGNoYXJtLi4uZXhjZXB0IGluIElFICg1LjAwKSB0 aGUgZXZlbnQgZ2V0cyBjYWxsZWQgdHdpY2UgZm9yIHNvbWUgcmVhc29uLiAgSSBoYXZlbid0IGJl ZW4gYWJsZSB0byB0cmFjayBpdCBkb3duIHlldC4gIEl0IGRvZXNuJ3Qgc2VlbSB0byBiZSBhIGJp ZyBkZWFsIG90aGVyIHRoYW4gdmlld2luZyBteSB3aWRnZXQgcmVzaXplIHR3aWNlIGJlZm9yZSB0 aGUgY29udGVudCBpcyBkaXNwbGF5ZWQgaW4gdGhlIHBhbmVsLiAgSXQncyBzdHJhbmdlIGNhdXNl IHdoZW4gSSBjcmVhdGUgYSBwYW5lbCwgSSBpbml0YWxseSBoYXZlIHRvIHNldCB0aGUgc2l6ZSB0 byBteSBsYXllcidzIHd4aC4gIFRoZW4sIHdoZW4gdGhlIG9ubG9hZCBldmVudCBvY2N1cnMgSSBz ZWUgdGhlIHBhbmVsIGdldHRpbmcgcmVzaXplZCAoaW4gSUUpIHRvIG15IGxheWVyJ3Mgd3hoLCB0 aGVuIGFnYWluIHRvIHRoZSBjb250ZW50IGhlaWdodC4gIEkgYWRkZWQgYSBmaXggaW4gbXkgb25s b2FkIGZ1bmN0aW9uIGZvciBJRSB0aGF0IHNheXM6DQoNCmlmIChpcy5pZSAmJiAgZS5nZXRTb3Vy Y2UoKS5pc1JlbG9hZGluZyA9PSBudWxsKSByZXR1cm47DQoNCmJ1dCB0aGlzIHNlZW1zIGxpa2Ug a2luZGEgb2YgaGFjay4NCg0KT24gYSBzaWRlIG5vdGUsIHRoZSB3aWRnZXQgSSdtIGNyZWF0aW5n IGlzIGEgd2l6YXJkICh3aGljaCBJIG5lZWQgdG8gdXNlIGZvciBhIGN1cnJlbnQgcHJvamVjdCB0 aGF0IEknbSB3b3JraW5nIG9uKS4gIEknZCBldmVudHVhbGx5IGxpa2UgdG8gY29udHJpYnV0ZSB0 aGlzIHRvIHRoZSBkeWFucGkgcHJvamVjdC4gIEhvdyBjYW4gSSBnbyBhYm91dCB0aGlzID8/DQoN CnRoYW5rcywNCg0KDQotTWFyayBIYXZpbGFuZA0K |
|
From: Dan S. <dy...@fu...> - 2001-01-04 15:56:54
|
I had written some code that did the communication by layer src-ing. I haven't updated it for the latest dynapi2. It was a nice system except that it was extremely unstable, kept crashing Netscape. Although I am hopeful if I rewrite a portion of it I could probably get it to a more stable state. The inline creation system has helped stabilize Netscape by an enormous amount, and I think a layer communication scheme could work decently now. I called it ServerTask, and was thinking of putting together a package of code an releasing it separate from the DynAPI (a previous version was distributed with the dynapi2 before the move to SourceForge). I don't see the necessity to use XML because usually it's just simple strings that need to be passed back and forth, it's so easy to do a direct converstion into Perl or PHP variables that it seems unecessary to wrap it all in xml tags. I wrote a quick little piece of code to translate from JS data (including 1D arrays) to a URI encoded string - I called it a ServerTaskData object. Once you submit the information the serverside script can work with the information and return a JavaScript variable as it's result. To pass large amounts of information a frames based system is by far the most simplistic to implement because all the tools are built into the browser. As you mentioned the back button is toast when using frames, but that is a minor tradeoff for the added functionality. I have used this before and it worked consistantly. Dan On Wed, Jan 03, 2001 at 12:39:57PM -0500, Al Byers wrote: > Hello All, > > I have noticed some talk about using loadpanel in conjunction with > forms. This is an area of great interest to me. Automating the > generation of forms and their interaction with the host is the crux of > an integrated development environment (IDE). I see IDE as being the > biggest current open niche in the open source arena and DynAPI could > play a huge part if there were such an effort to develop one. > > I think the key to a successful IDE will be the incorporation of XML > technology - it will strike a responsive chord with the industry and it > solves some real problems (see below). Over the past couple of years > Local Square has developed a client/server environment in which XML is > passed to and from browser forms via XML (we also can send HTML). I > have developed a lightweight psuedo-XML parser in Javascript. We have > tools to generate the necessary forms and scripts from a database table > definition. The system is designed to be distributed - using Apache/HTTP > as the transport and Perl as the scripting language. It is highly > object-oriented - both in Perl and Javascript. > > DynApi is playing a key role in this system in two important ways: > 1) The use of DynApi widgets in conjunction with forms, can give the > processing of data a lot of the amenities that normally would be > associated with desktop or Java apps. Things like a responsive menu, > popup boxes for selections and help, etc. The fact that data is kept on > the client also improves the response time. > > 2) We are currently using DynApi(1) to implement a drag and drop > environment for laying out web pages. This is for e-commerce, but it > could have lots of other uses. Because of the varied nature of the data > structure for pages built this way (they would have special embedded > "objects"), XML is the best vehicle for transmitting and storing this > data. And it leaves us in a position to take advantage of the > forthcoming XSLT work to render the XML. > > There is also a third area - using loadpanel to transmit the data. We > have struggled with this problem - having used 1) a hidden frame to do > the transmission (it is fragile and messes up the expected operation of > the "Back" key), 2) the precursor to loadpanel (it is also fragile and > suffers from a limitation on the size of data that can be uploaded and > 3) urlPipe, a Java applet developed at www.kisai.com (they don't seem to > be there anymore?) (it seemed to work great except for some special > problems that only affected our work. But no source code). Note that the > folks at allaire.com seem to be interested in this use of XML (they have > a protocol called WDDX ) and I have seen urlPipe mentioned there. > > Our company has toyed with the idea of making our work open source. If > anyone is interested in this type of project, please respond here or to > me directly so that I have something to take to our management. The > beauty of such an endeavor is that when we are done, instead of being > able to share widgets with which we build apps, we will be able to share > complete and compatible applications - moving DynApi into the ASP arena. > > -Al > > -- > Al Byers > Local Square, Inc. > 826 N. Augusta St. > Staunton, VA 24401 > 540.213.0500 > www.localsquare.com > by...@lo... > > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
|
From: Pascal <pb...@oi...> - 2001-01-04 07:25:57
|
but why not just listen for the onload event which is being triggered at the end of the loading (when it's finished :) Pascal Bestebroer (pb...@oi...) Software ontwikkelaar Oberon Informatiesystemen b.v. http://www.oibv.com > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Mark Haviland > Verzonden: donderdag 4 januari 2001 0:38 > Aan: dyn...@li... > Onderwerp: RE: [Dynapi-Dev] loadpanel troubles... > > > > > > -----Original Message----- > > From: dyn...@li... > > [mailto:dyn...@li...]On Behalf Of Robert > > Rainwater > > Sent: Sunday, December 31, 2000 11:46 PM > > To: dyn...@li... > > Subject: Re: [Dynapi-Dev] loadpanel troubles... > > > > > > > > > > > I think in LoadQueue.prototype.loadNext, you can change: > > > > > > this.index++; > > > > > > -to- > > > > > > DynAPI.removeFromArray(this.queue,this.index++); > > > > > > > > oops. It should probaly say: > > > > DynAPI.removeFromArray(this.queue,this.index); > > Score! Thanks. > > Is there any way that the following can make it into CVS for > loadpanel ? > > In the constructor: > > this.loadHandlerOnFinish = null; > > then the loadHandler method would become: > > LoadPanel.prototype.loadHandler = function(url) { > this.url = url; > var w,h; > if (is.ns4 && this.isILayer) { > w = this.loadElement.document.width; > h = this.loadElement.document.height; > } > else { > w = this.getContentWidth(); > h = this.getContentHeight(); > } > if (this.autoW) this.setWidth(w,false); > if (this.autoH) this.setHeight(h,false); > this.isReloading = false; > this.invokeEvent('load'); > if (this.loadHandlerOnFinish != null && > typeof(this.loadHandlerOnFinish) == "function"){ > this.loadHandlerOnFinish(w,h); > } > }; > if (this.loadHandlerOnFinish != null && > typeof(this.loadHandlerOnFinish) == "function") { > this.loadHandlerOnFinish(w,h); > } > > I'm creating a widget where I keep an array of loadpanels for > URL's that have been added to my widget object. Adding the > above code the the loadpanel class was the only way I could > figure out how to 'safely' get the width & height of a panel. > > > -Mark Haviland > )Ú¦ Þ¾f¢)à+-)Ú¦ > Þ¾X¬¶Ë(º· ~àzwÛiÿùb²Û,¢êÜyú+éÞ·ùYùb²Ø§~ÝÊv©×¯ > |
|
From: Michael <mb...@st...> - 2001-01-04 00:57:56
|
I have an improvement to dragevent.js.
by adding two lines of code, IE does no longer select text while
dragging (which in my opinion is really annoying)
the trick is to use IE's document.body.onselectstart Event-Handler
the changes i made to dragevent.js are the following:
--------------------------------------------------------------
[ ... ]
DragEvent.lyrListener.onmousedown=function(e) {
[ ... ]
lyr.dragevent=new DragEvent("dragstart",lyr);
// disables text selection
if (is.ie) lyr.doc.body.onselectstart = function() { return false }
DynAPI.document.dragevent=lyr.dragevent;
DynAPI.document.dragobject=lyr;
[ ... ]
};
[ ... ]
DragEvent.docListener.onmouseup=function(e) {
[ ... ]
if (!lyr) return;
// re-enables text-selection
if (is.ie) lyr.doc.body.onselectstart = null
if (lyr.parent.DragDrop) lyr.parent.DragDrop(lyr);
[ ... ]
};
[ ... ]
--------------------------------------------------------------
maybe this should be better done by using the 'dragstart' and 'dragend'
Events!??
bye.
Michael Buerge
oh! i forgot:
there's a mini-bug in the list-example (dynapi.gui.list.html), the order
of the includes of the api-files is wrong:
it is
DynAPI.include('dynapi.api.dynlayer')
DynAPI.include('dynapi.api.browser')
..
which causes an error while parsing dynlayer.js, where of course the
is-object doesnt yet exist
reverse the order and it will rock again!
|
|
From: Robert R. <rra...@ya...> - 2001-01-04 00:46:38
|
Why not just capture the onload event. Thats why it is invoked there. O=
r
am I missing something here?
Robert Rainwater
----- Original Message -----
From: "Mark Haviland" <mha...@ha...>
To: <dyn...@li...>
Sent: Wednesday, January 03, 2001 6:37 PM
Subject: RE: [Dynapi-Dev] loadpanel troubles...
>
>
> > -----Original Message-----
> > From: dyn...@li...
> > [mailto:dyn...@li...]On Behalf Of Robert
> > Rainwater
> > Sent: Sunday, December 31, 2000 11:46 PM
> > To: dyn...@li...
> > Subject: Re: [Dynapi-Dev] loadpanel troubles...
> >
> >
> >
> >
> > > I think in LoadQueue.prototype.loadNext, you can change:
> > >
> > > this.index++;
> > >
> > > -to-
> > >
> > > DynAPI.removeFromArray(this.queue,this.index++);
> > >
> > >
> > oops. It should probaly say:
> >
> > DynAPI.removeFromArray(this.queue,this.index);
>
> Score! Thanks.
>
> Is there any way that the following can make it into CVS for loadpanel =
?
>
> In the constructor:
>
> this.loadHandlerOnFinish =3D null;
>
> then the loadHandler method would become:
>
> LoadPanel.prototype.loadHandler =3D function(url) {
> this.url =3D url;
> var w,h;
> if (is.ns4 && this.isILayer) {
> w =3D this.loadElement.document.width;
> h =3D this.loadElement.document.height;
> }
> else {
> w =3D this.getContentWidth();
> h =3D this.getContentHeight();
> }
> if (this.autoW) this.setWidth(w,false);
> if (this.autoH) this.setHeight(h,false);
> this.isReloading =3D false;
> this.invokeEvent('load');
> if (this.loadHandlerOnFinish !=3D null && typeof(this.loadHandlerOnFin=
ish)
=3D=3D "function"){
> this.loadHandlerOnFinish(w,h);
> }
> };
> if (this.loadHandlerOnFinish !=3D null && typeof(this.loadHandlerOnFin=
ish)
=3D=3D "function") {
> this.loadHandlerOnFinish(w,h);
> }
>
> I'm creating a widget where I keep an array of loadpanels for URL's tha=
t
have been added to my widget object. Adding the above code the the
loadpanel class was the only way I could figure out how to 'safely' get t=
he
width & height of a panel.
>
>
> -Mark Haviland
> =0F)=DA=A6 =DE=BEf=A2-)=E0-+-=0F)=DA=A6
=DE=BEX=AC=B6=CB(=BA=B7=1E~S=E0zw=AD?=DBi=FF=F9b=B2=DB,=A2=EA=DCy=FA+=81=E9=
=DE=B7=F9sSYsY=F9b=B2=D8=A7~=8F=DD=CAv=A9?=D7=AF
|
|
From: Mark H. <mha...@ha...> - 2001-01-03 23:26:05
|
DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogZHluYXBpLWRldi1hZG1p bkBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQNCj4gW21haWx0bzpkeW5hcGktZGV2LWFkbWluQGxpc3Rz LnNvdXJjZWZvcmdlLm5ldF1PbiBCZWhhbGYgT2YgUm9iZXJ0DQo+IFJhaW53YXRlcg0KPiBTZW50 OiBTdW5kYXksIERlY2VtYmVyIDMxLCAyMDAwIDExOjQ2IFBNDQo+IFRvOiBkeW5hcGktZGV2QGxp c3RzLnNvdXJjZWZvcmdlLm5ldA0KPiBTdWJqZWN0OiBSZTogW0R5bmFwaS1EZXZdIGxvYWRwYW5l bCB0cm91Ymxlcy4uLg0KPiANCj4gDQo+IA0KPiANCj4gPiBJIHRoaW5rIGluIExvYWRRdWV1ZS5w cm90b3R5cGUubG9hZE5leHQsIHlvdSBjYW4gY2hhbmdlOg0KPiA+DQo+ID4gdGhpcy5pbmRleCsr Ow0KPiA+DQo+ID4gLXRvLQ0KPiA+DQo+ID4gRHluQVBJLnJlbW92ZUZyb21BcnJheSh0aGlzLnF1 ZXVlLHRoaXMuaW5kZXgrKyk7DQo+ID4NCj4gPg0KPiBvb3BzLiAgSXQgc2hvdWxkIHByb2JhbHkg c2F5Og0KPiANCj4gRHluQVBJLnJlbW92ZUZyb21BcnJheSh0aGlzLnF1ZXVlLHRoaXMuaW5kZXgp Ow0KDQpTY29yZSEgIFRoYW5rcy4NCg0KSXMgdGhlcmUgYW55IHdheSB0aGF0IHRoZSBmb2xsb3dp bmcgY2FuIG1ha2UgaXQgaW50byBDVlMgZm9yIGxvYWRwYW5lbCA/DQoNCkluIHRoZSBjb25zdHJ1 Y3RvcjoNCg0KCXRoaXMubG9hZEhhbmRsZXJPbkZpbmlzaCA9IG51bGw7DQoNCnRoZW4gdGhlIGxv YWRIYW5kbGVyIG1ldGhvZCB3b3VsZCBiZWNvbWU6DQoNCkxvYWRQYW5lbC5wcm90b3R5cGUubG9h ZEhhbmRsZXIgPSBmdW5jdGlvbih1cmwpIHsNCgl0aGlzLnVybCA9IHVybDsNCgl2YXIgdyxoOw0K CWlmIChpcy5uczQgJiYgdGhpcy5pc0lMYXllcikgew0KCQl3ID0gdGhpcy5sb2FkRWxlbWVudC5k b2N1bWVudC53aWR0aDsNCgkJaCA9IHRoaXMubG9hZEVsZW1lbnQuZG9jdW1lbnQuaGVpZ2h0Ow0K CX0NCgllbHNlIHsNCgkJdyA9IHRoaXMuZ2V0Q29udGVudFdpZHRoKCk7DQoJCWggPSB0aGlzLmdl dENvbnRlbnRIZWlnaHQoKTsNCgl9DQoJaWYgKHRoaXMuYXV0b1cpIHRoaXMuc2V0V2lkdGgodyxm YWxzZSk7DQoJaWYgKHRoaXMuYXV0b0gpIHRoaXMuc2V0SGVpZ2h0KGgsZmFsc2UpOw0KCXRoaXMu aXNSZWxvYWRpbmcgPSBmYWxzZTsNCgl0aGlzLmludm9rZUV2ZW50KCdsb2FkJyk7DQoJaWYgKHRo aXMubG9hZEhhbmRsZXJPbkZpbmlzaCAhPSBudWxsICAmJiB0eXBlb2YodGhpcy5sb2FkSGFuZGxl ck9uRmluaXNoKSA9PSAiZnVuY3Rpb24iKXsNCgkJdGhpcy5sb2FkSGFuZGxlck9uRmluaXNoKHcs aCk7DQoJfQ0KfTsNCmlmICh0aGlzLmxvYWRIYW5kbGVyT25GaW5pc2ggIT0gbnVsbCAgJiYgdHlw ZW9mKHRoaXMubG9hZEhhbmRsZXJPbkZpbmlzaCkgPT0gImZ1bmN0aW9uIikgew0KCXRoaXMubG9h ZEhhbmRsZXJPbkZpbmlzaCh3LGgpOw0KfQ0KDQpJJ20gY3JlYXRpbmcgYSB3aWRnZXQgd2hlcmUg SSBrZWVwIGFuIGFycmF5IG9mIGxvYWRwYW5lbHMgZm9yIFVSTCdzIHRoYXQgaGF2ZSBiZWVuIGFk ZGVkIHRvIG15IHdpZGdldCBvYmplY3QuICBBZGRpbmcgdGhlIGFib3ZlIGNvZGUgdGhlIHRoZSBs b2FkcGFuZWwgY2xhc3Mgd2FzIHRoZSBvbmx5IHdheSBJIGNvdWxkIGZpZ3VyZSBvdXQgaG93IHRv ICdzYWZlbHknIGdldCB0aGUgd2lkdGggJiBoZWlnaHQgb2YgYSBwYW5lbC4NCg0KDQotTWFyayBI YXZpbGFuZA0K |
|
From: Robert R. <rra...@ya...> - 2001-01-03 20:18:32
|
I've updated my current version to do this for a while, but just haven't =
put
it in CVS. I will update CVS soon so that the include will work that way.
Robert
----- Original Message -----
From: "Michael B=FCrge" <mb...@st...>
To: <dyn...@li...>
Sent: Tuesday, January 02, 2001 6:58 PM
Subject: [Dynapi-Dev] DynAPI.include()
> hi there.
>
> this is my first post to this list, and i would like to use the
opportunity to thank you for the great work you're all doing. i just star=
ted
dealing with
> the dynapi after having spent a _lot_ of time putting together somethin=
g
similar on my own (i now finally gave up, mainly because it's just way to=
o
much
> work keeping everything up to date).
>
> now to the real issue of this post:
>
> the following is an excerpt from part 1 one of the tutorials written by
Pascal, describing the include() function:
>
> * DynAPI.include('myownfile.js','location/path')
> Include your own file not located in the [dynapi base path] location
> * DynAPI.include('myownfile.js','./')
> Include your own file located at the current file location.
>
> i like these features, so i tried to use them bu it didn't work. lookin=
g
at the code i realised that they weren't implemented at all. i don't know=
if
> somebody did already implement them, but both the current distro and th=
e
current CVS-version do not contain them.
> so here's my version:
>
> include : function(src,path) {
> if(src.substring(src.length-3)!=3D".js") src+=3D".js";
> if (!path) var path=3DDynAPI.librarypath;
> else {
> if (path=3D=3D"./") path =3D "";
> else if (path[path.length-1] !=3D "/") path +=3D "/";
> document.write('<script language=3D"Javascript1.2" src=3D"'+ path=
+ src
+ '"></script>');
> return;
> }
> ....some more stuff....
> }
>
> hope this is usefull, and sorry if i missed the version containing thos=
e
features. (BTW: is was pretty hard for me to find out where to get the
current
> files, so a few hints on the project-webpage would save a great deal of
time to people interested in looking at the current work going on)
>
> that all for now.
> greets.
> michael buerge
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
|
|
From: Robert R. <rra...@ya...> - 2001-01-03 20:16:41
|
----- Original Message ----- From: "Peter Curran" <pc...@ca...> To: <dyn...@li...> Sent: Wednesday, January 03, 2001 9:16 AM Subject: Re: [Dynapi-Dev] Snapshot broken > This "snapshot" appears to be the current version of the code, > pre-extracted from the CVS. Is that right? If so, it is just what I have > wanted on a number of occasions. I just want the current code, and don't > really want to get involved in the full CVS system, unless/until I'm in a > position to contribute something useful. Is this actually being maintained > as a reasonably current version of the code, or was this just a one-time > thing, or ...? It is done automatically on a daily basis. Although Sourceforges new server upgrade seems to have messed up the cron job, this should be fixed soon. > Secondly, I know my eyesight is going, but I can't find any link to this > snapshot on the home page, or any other page. Is there one, or was this > intended to be an insiders' secret that has now escaped? I would be hesitant to post a link on the site, since most developers and testers are subscribed to this list. Putting a link on the site would cause people to download it and use it as final code. Robert Rainwater |
|
From: Robert R. <rra...@ya...> - 2001-01-03 20:12:52
|
Sorry I forgot to say the list is called dyn...@li....
If anyone with cvs write access would like to update cvs to send updates to
the list (since I don't have access right now), you can edit the file:
/cvsroot/loginfo
Change this line:
DEFAULT $CVSROOT/CVSROOT/syncmail %{sVv} rra...@ya...
-to-
DEFAULT $CVSROOT/CVSROOT/syncmail %{sVv} dyn...@li...
Robert Rainwater
----- Original Message -----
From: "Robert Rainwater" <rra...@ya...>
To: <dyn...@li...>
Sent: Wednesday, January 03, 2001 3:05 PM
Subject: Re: [Dynapi-Dev] Snapshot broken
> I've already created such a list (). Currently, I do not have access to
CVS
> (I'm on vacation), but in about 3 or 4 days I will update CVS so all
updates
> will be emailed there. If you look at the changelog file in the snapshot,
> you will see basically the same information. All of the changes are
listed
> in that file. I should have the mailing list working soon, so you can
view
> the changes from the web or from your email.
>
> Robert Rainwater
> ----- Original Message -----
> From: "Xabi Ochotorena" <xoc...@ar...>
> To: "Robert Rainwater" <dyn...@li...>
> Sent: Tuesday, January 02, 2001 6:45 AM
> Subject: Re: [Dynapi-Dev] Snapshot broken
>
>
> > Hello Robert,
> >
> > RR> The snapshot at http://dynapi.sourceforge.net/snapshot/dynapi.zip
> appears to
> > RR> be broken. If you are downloading it, you will notice that its not
> > RR> up-to-date with the latest changes. When I get home Sunday, I will
> fix this
> > RR> so that it will be updating correctly.
> >
> > A list for sending diff's and fixes would be a cool christmas gift.
> >
> > --
> > Best regards,
> > Xabi xoc...@ar...
> >
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
|
|
From: Robert R. <rra...@ya...> - 2001-01-03 20:05:14
|
I've already created such a list (). Currently, I do not have access to CVS (I'm on vacation), but in about 3 or 4 days I will update CVS so all updates will be emailed there. If you look at the changelog file in the snapshot, you will see basically the same information. All of the changes are listed in that file. I should have the mailing list working soon, so you can view the changes from the web or from your email. Robert Rainwater ----- Original Message ----- From: "Xabi Ochotorena" <xoc...@ar...> To: "Robert Rainwater" <dyn...@li...> Sent: Tuesday, January 02, 2001 6:45 AM Subject: Re: [Dynapi-Dev] Snapshot broken > Hello Robert, > > RR> The snapshot at http://dynapi.sourceforge.net/snapshot/dynapi.zip appears to > RR> be broken. If you are downloading it, you will notice that its not > RR> up-to-date with the latest changes. When I get home Sunday, I will fix this > RR> so that it will be updating correctly. > > A list for sending diff's and fixes would be a cool christmas gift. > > -- > Best regards, > Xabi xoc...@ar... > > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |
|
From: Eytan H. <ey...@tr...> - 2001-01-03 18:43:36
|
Sorry but I just don't agree with what you are doing. I know that there will be ppl who disagree with me but still... XML is nothingbut a buzz word, if I have understood you correctly it looks as if(notice as if not really) that you are trying to start a new startup hi-tech company and throwing in all the buzz words. We are an open-source communinty. I don't look the idea of an IDE in the language of development (Forte SUX!!!). I perfer a more stable language (C,Delphi heck even VB). I do agree that we need to find a solution to load panel, and although I have used the Java approach (I told you guys there is an official applet form M$ that is great) I don't like the Java approach. Java is for java and JS is for JS, I don't like mixing. I think some serverside code could easily be written with a few tricks for taking care of the back button. Since it is so simple we could write it in different languages (ASP, Perl or any other serverside language) so that it will be compatible. But all this doesn't change the fact the we really need an IDE. I'm all for it. How about we start a SourceForge project in it there will be groups each one developing there own style(DynAPI Based, Compiled Windoze code based etc..) I'd like to hear responses, (pls doen't flame me ;-)) 8an |
|
From: Pascal B. <pa...@dy...> - 2001-01-03 18:09:14
|
Actually it was called servertasks (I was almost correct :), but again ask Dan about it seeing as he created it.. I can't find an "uptodate" version. it provided back and forth communication between javascript and server-side (php was used, but could also work with asp). It uses the loadpanel for communication. cya, Pascal Bestebroer pa...@dy... http://www.dynamic-core.net > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Doug Melvin > Verzonden: woensdag 3 januari 2001 21:20 > Aan: dyn...@li... > Onderwerp: Re: [Dynapi-Dev] 2001 areas of focus, DynAPI - New > "Thread"... > > > ServerSide widget? > Do tell! more! more! > > Doug > ----- Original Message ----- > From: "Pascal Bestebroer" <pa...@dy...> > To: <dyn...@li...> > Sent: Tuesday, January 02, 2001 11:00 AM > Subject: RE: [Dynapi-Dev] 2001 areas of focus, DynAPI - New "Thread"... > > > > Hmm, I think Dan had already done this in his ServerSide widget... > > > > It's actually funny to see alot of ideas popping on this > mailing list that > > some of the "older" dynapi users have already did or worked on :-) > > > > Another one is the idea about layout managing (something that was > mentioned > > a few months ago by Brandon, btw.. did you ever finish it?) and the IDE > > thing which I had already worked on a few months ago but dropped because > of > > to many changes being made.. > > > > well, lets just hope these ideas get 100% completed this year :-) > > > > greets, > > > > Pascal Bestebroer > > pa...@dy... > > http://www.dynamic-core.net > > > > > -----Oorspronkelijk bericht----- > > > Van: dyn...@li... > > > [mailto:dyn...@li...]Namens Brust, Corwin > > > Verzonden: dinsdag 2 januari 2001 19:17 > > > Aan: 'dyn...@li...' > > > Onderwerp: RE: [Dynapi-Dev] 2001 areas of focus, DynAPI - New > > > "Thread"... > > > > > > > > > > > > > (2) Most robust backend systems leave the client-side wearing > > > concrete > > > > shoes. I think we have a tremendous opportunity to be both > > > 'back-end > > > > powerful' and 'client-side dynamic' using MySQL, PHP and DynAPI as > > > an > > > > implementation system. This creates the potential for > > > self-animating > > > > polls/presentation information, robust user preference modules, etc. > > > > > > This also sounds interesting to me, particularly useful to me > would be a > > > mechanism, similar to LoadPanel, but which takes a form object > > > rather then a > > > url. The would be helpful in working around the limitation of > JavaScript > > > which prevents targeting of layers by forms. > > > > > > Corwin Brust > > > Software Engineer > > > Alliance Data Systems > > > formerly Harmonic Systems, Inc. > > > 701 Fourth Ave South, Suite-1600 > > > Minneapolis, Minnesota 55415 > > > Office: (612) 672-3584 > > > Mobil: (612) 239-8073 > > > Email: cb...@ha... > > > > > > _______________________________________________ > > > Dynapi-Dev mailing list > > > Dyn...@li... > > > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > > > > > > > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > |
175 messages has been excluded from this view by a project administrator.
