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: nobody <no...@so...> - 2001-02-25 10:40:51
|
Artifact #404007, was updated on 2001-02-24 16:07 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=105757&aid=404007&group_id=5757 Category: Core API Group: None Status: Open Priority: 6 Submitted By: Robert Rainwater Assigned to: Pascal Bestebroer Summary: Events in Images (IE 5.5) Initial Comment: Using the dynapi_2001_02_24 snapshot, events in layers in IE 5.5 do not appear to be fired. For example, in the dynapi.gui.button.html example, the onmousedown events fail to fire when doing a mousedown on the image part of a button. ---------------------------------------------------------------------- Comment By: Pascal Bestebroer Date: 2001-02-25 02:42 Message: Logged In: YES user_id=38844 fixed the problem ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=105757&aid=404007&group_id=5757 |
|
From: Pascal B. <pa...@dy...> - 2001-02-25 10:32:26
|
extra code (size is also an issue with javascript) to be rude: these things have all been discussed many times in the last year.. and we (including Dan back then) decided that this was just the most straight forward way of doing the inheriting (and widgets SHOULD inherit from dynlayer for should be obvious reasons) The way you want to do this is just adding work arounds for something that can be done using build in Javascript ideas. There was one WidgetObject once that did it in the same way as you'r suggesting (all widgets inherited from this object and it had a set of functions that simple call the correct dynlayer function) but this is alot of overhead and extra code, making things slower, use more memory, and bigger... Pascal Bestebroer pa...@dy... http://www.dynamic-core.net > A wrapper function would be added to myWidget that would look like this: > myWidget.prototype.moveTo = function(x,y){ > this.dynlayer.moveto(x,y); > } > > 8an |
|
From: Eytan H. <ey...@tr...> - 2001-02-25 10:24:25
|
A wrapper function would be added to myWidget that would look like this:
myWidget.prototype.moveTo = function(x,y){
this.dynlayer.moveto(x,y);
}
8an
|
|
From: Pascal B. <pa...@dy...> - 2001-02-25 10:23:17
|
Yes I still want to implement it, but it does require some time to split up the needed code, and didn't find the time for it yesterday. I do believe it should be done before any new release, because we already have a heavily changed code now which might cause bugs so adding this potential-bug-trap change to it would be great (uhm..that doesn't sound right :) Maybe get around to it next weekend. Pascal Bestebroer pa...@dy... http://www.dynamic-core.net > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Robert Rainwater > Verzonden: zaterdag 24 februari 2001 23:16 > Aan: DynAPI Development List > Onderwerp: Re[2]: [Dynapi-Dev] setContent > > > > By the way are you still planning on putting in the dynobject? It > shouldn't be very hard to implement since you have already done it in > the DynaCore. But it will require that everybody includes in their > pages though. > > -- > // Robert Rainwater > > On 2/24/2001, 4:56:31 PM EST, Pascal wrote about "[Dynapi-Dev] > setContent": > > > oops! :) > > > Pascal Bestebroer > > pa...@dy... > > http://www.dynamic-core.net > > >> -----Oorspronkelijk bericht----- > >> Van: dyn...@li... > >> [mailto:dyn...@li...]Namens Robert Rainwater > >> Verzonden: zaterdag 24 februari 2001 22:49 > >> Aan: DynAPI Development List > >> Onderwerp: Re: [Dynapi-Dev] setContent > >> > >> > >> > >> I was wrong. It was the new code after all. I updated cvs to fix the > >> calls to createElement. They now use the dynlayer method, not the > >> static method. > >> > >> -- > >> // Robert Rainwater > >> > >> On 2/24/2001, 2:54:36 PM EST, Robert wrote about "[Dynapi-Dev] > >> setContent": > >> > >> > >> > I havent tested much yet, but all of the examples that use setContent > >> > with labels seem to be broken (atleast in IE 55). For instance > >> the pushpanel and > >> > scrollpane examples are broken. I don't think this is new though, > >> > because it seems like I've noticed it before. > >> > >> > >> > >> ---------------------- > >> DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/ > >> DynAPI Homepage: http://dynapi.sourceforge.net/ > >> > >> > >> > >> _______________________________________________ > >> Dynapi-Dev mailing list > >> Dyn...@li... > >> http://lists.sourceforge.net/lists/listinfo/dynapi-dev > >> > > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > http://lists.sourceforge.net/lists/listinfo/dynapi-dev > > > ---------------------- > DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/ > DynAPI Homepage: http://dynapi.sourceforge.net/ > > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev > |
|
From: Pascal B. <pa...@dy...> - 2001-02-25 10:20:11
|
uhm.. just in case: sorry :) Not sure if I broke anything, but that's why people should now test the CVS code as much as possible I did alot of if statement changes, and other optimisations so these might have caused problems. Pascal Bestebroer pa...@dy... http://www.dynamic-core.net > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Robert Rainwater > Verzonden: zondag 25 februari 2001 10:28 > Aan: DynAPI Development List > Onderwerp: Re[2]: [Dynapi-Dev] [ dynapi-Bugs-404007 ] Events in Images > (IE 5.5) > > > > Try any of the button examples or the scrollpane example. No events > are fired when directly over an image. I'm using the latest code from > CVS. > > I thought this had been fixed before? > > -- > // Robert Rainwater > > On 2/24/2001, 11:37:55 PM EST, Doug wrote about "[Dynapi-Dev] > dynapi-Bugs-404007 ] Events in Images (IE 5.5)": > > > I've just updated my JS and found no such problem. > > Win98 > > IE 5.5 > > ----- Original Message ----- > > From: "nobody" <no...@so...> > > To: <no...@so...> > > Sent: Saturday, February 24, 2001 4:07 PM > > Subject: [Dynapi-Dev] [ dynapi-Bugs-404007 ] Events in Images (IE 5.5) > > > >> Artifact #404007, was updated on 2001-02-24 16:07 > >> You can respond by visiting: > >> > > http://sourceforge.net/tracker/?func=detail&atid=105757&aid=404007&group_id= > 5757 >> >> Category: Core API >> Group: None >> Status: Open >> Priority: 6 >> Submitted By: Robert Rainwater >> Assigned to: Nobody/Anonymous >> Summary: Events in Images (IE 5.5) >> >> Initial Comment: >> Using the dynapi_2001_02_24 snapshot, events in layers >> in IE 5.5 do not appear to be fired. >> >> For example, in the dynapi.gui.button.html example, >> the onmousedown events fail to fire when doing a >> mousedown on the image part of a button. >> >> ---------------------------------------------------------------------- >> >> You can respond by visiting: >> > http://sourceforge.net/tracker/?func=detail&atid=105757&aid=404007&group_id= > 5757 >> >> _______________________________________________ >> Dynapi-Dev mailing list >> Dyn...@li... >> http://lists.sourceforge.net/lists/listinfo/dynapi-dev > --- > Outgoing mail is certified Virus Free by AVG Free Edition > Download at: http://www.grisoft.com/html/us_index.cfm > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.231 / Virus Database: 112 - Release Date: 2/12/01 > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev ---------------------- DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/ DynAPI Homepage: http://dynapi.sourceforge.net/ _______________________________________________ Dynapi-Dev mailing list Dyn...@li... http://lists.sourceforge.net/lists/listinfo/dynapi-dev |
|
From: Pascal B. <pa...@dy...> - 2001-02-25 10:16:25
|
And see the API part, this means not just for making things work cross-browser, but also make the underlying code transparent and as easy to use as possible. So the difference: myWidget.moveTo(50,50) or myWidget.DynLayer.moveTo(50,50) would 1. add more code in general 2. not as transparent as wanted. A DynLayer and Widget can now be controlled in exactly the same way, but if every widget needs to be accessed thru it's dynlayer object, a dynlayer and widget won't be controlled in the same way. The only thing you gain with this is the fact that any deletion code we might create (a single function probably) would be easier, yet all other code created by users would be larger and more "difficult to understand" for users. Pascal Bestebroer pa...@dy... http://www.dynamic-core.net > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Eytan Heidingsfeld > Verzonden: zondag 25 februari 2001 9:54 > Aan: dyn...@li... > Onderwerp: Re: [Dynapi-Dev] a few hours for only 2 lines of code.. damn! > > > It HURTS! > My My The Rocks fell like rain!! > (And Feb 24th is even my birthday ;-) > There will be no difference in memory if you place it as an > object but it is > just better programming. Straight out! The problem is that you think of > DynLayer as a widget instead of an interface remember it is Dyn - API > (Interface is the I) > 8an > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev > |
|
From: Robert R. <rra...@ya...> - 2001-02-25 09:28:47
|
Try any of the button examples or the scrollpane example. No events are fired when directly over an image. I'm using the latest code from CVS. I thought this had been fixed before? -- // Robert Rainwater On 2/24/2001, 11:37:55 PM EST, Doug wrote about "[Dynapi-Dev] [ dynapi-Bugs-404007 ] Events in Images (IE 5.5)": > I've just updated my JS and found no such problem. > Win98 > IE 5.5 > ----- Original Message ----- > From: "nobody" <no...@so...> > To: <no...@so...> > Sent: Saturday, February 24, 2001 4:07 PM > Subject: [Dynapi-Dev] [ dynapi-Bugs-404007 ] Events in Images (IE 5.5) >> Artifact #404007, was updated on 2001-02-24 16:07 >> You can respond by visiting: >> > http://sourceforge.net/tracker/?func=detail&atid=105757&aid=404007&group_id= > 5757 >> >> Category: Core API >> Group: None >> Status: Open >> Priority: 6 >> Submitted By: Robert Rainwater >> Assigned to: Nobody/Anonymous >> Summary: Events in Images (IE 5.5) >> >> Initial Comment: >> Using the dynapi_2001_02_24 snapshot, events in layers >> in IE 5.5 do not appear to be fired. >> >> For example, in the dynapi.gui.button.html example, >> the onmousedown events fail to fire when doing a >> mousedown on the image part of a button. >> >> ---------------------------------------------------------------------- >> >> You can respond by visiting: >> > http://sourceforge.net/tracker/?func=detail&atid=105757&aid=404007&group_id= > 5757 >> >> _______________________________________________ >> Dynapi-Dev mailing list >> Dyn...@li... >> http://lists.sourceforge.net/lists/listinfo/dynapi-dev > --- > Outgoing mail is certified Virus Free by AVG Free Edition > Download at: http://www.grisoft.com/html/us_index.cfm > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.231 / Virus Database: 112 - Release Date: 2/12/01 > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev ---------------------- DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/ DynAPI Homepage: http://dynapi.sourceforge.net/ |
|
From: Eytan H. <ey...@tr...> - 2001-02-25 09:22:34
|
I decided to tackle the more DHTML side of it. I have also decided that all tests should be per browser since they are = all different. IE 5.0 great news. Creating 1500 layers raises mem usg to 10 MB(From 8+-) Deletion down to 9 MB! 8an |
|
From: Robert R. <rra...@ya...> - 2001-02-25 09:16:19
|
I removed the addChildID from dynlayer.js. The document.all[] id's are now set in assignChildren. It seems that assignChildren was stepping through the children right after addChildID did the same, so I just put the code in assignChildren and removed addChildID. May not be much of an improvement, but every little bit helps. -- // Robert Rainwater ---------------------- DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/ DynAPI Homepage: http://dynapi.sourceforge.net/ |
|
From: Robert R. <rra...@ya...> - 2001-02-25 09:09:33
|
As much as I liked DynAPI 1, I don't want to go back to those days :) I think the widget model as it is now, is much more extensible than by not using any type of inheriting. -- // Robert Rainwater On 2/25/2001, 3:48:41 AM EST, Pascal wrote about "[Dynapi-Dev] a few hours for only 2 lines of code.. damn!": > man, now your gonna get it :) > leave the inheriting model alone! > serious though, currently widgets really inherit from the dynlayer, so that > all dynlayer methods are available without any extra code (or memory) > if you make it a property of the widget, all these things are gone and you > would need to call the dynlayer property to access dynlayer functionality > (sizing,moveto) which should be simple widget methods. > I think there has been already ALOT of discussion about this (see archives > :) and I for one am against any widget model changes (always have been, > always will :) > Pascal Bestebroer > pa...@dy... > http://www.dynamic-core.net >> -----Oorspronkelijk bericht----- >> Van: dyn...@li... >> [mailto:dyn...@li...]Namens Eytan Heidingsfeld >> Verzonden: zaterdag 24 februari 2001 23:02 >> Aan: dyn...@li... >> Onderwerp: RE: [Dynapi-Dev] a few hours for only 2 lines of code.. damn! >> >> >> The only thing I still want to change is the way that all widgets inherit >> from DynLayer. Why don't we just make them have a dynlayer object >> then it is >> easier to free mem. (Taking care of DynLayer is a hassle but the object >> isn't). >> 8an >> >> >> _______________________________________________ >> Dynapi-Dev mailing list >> Dyn...@li... >> http://lists.sourceforge.net/lists/listinfo/dynapi-dev >> > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev ---------------------- DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/ DynAPI Homepage: http://dynapi.sourceforge.net/ |
|
From: Eytan H. <ey...@tr...> - 2001-02-25 08:53:46
|
It HURTS! My My The Rocks fell like rain!! (And Feb 24th is even my birthday ;-) There will be no difference in memory if you place it as an object but it is just better programming. Straight out! The problem is that you think of DynLayer as a widget instead of an interface remember it is Dyn - API (Interface is the I) 8an |
|
From: Pascal B. <pa...@dy...> - 2001-02-25 08:47:54
|
man, now your gonna get it :) leave the inheriting model alone! serious though, currently widgets really inherit from the dynlayer, so that all dynlayer methods are available without any extra code (or memory) if you make it a property of the widget, all these things are gone and you would need to call the dynlayer property to access dynlayer functionality (sizing,moveto) which should be simple widget methods. I think there has been already ALOT of discussion about this (see archives :) and I for one am against any widget model changes (always have been, always will :) Pascal Bestebroer pa...@dy... http://www.dynamic-core.net > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Eytan Heidingsfeld > Verzonden: zaterdag 24 februari 2001 23:02 > Aan: dyn...@li... > Onderwerp: RE: [Dynapi-Dev] a few hours for only 2 lines of code.. damn! > > > The only thing I still want to change is the way that all widgets inherit > from DynLayer. Why don't we just make them have a dynlayer object > then it is > easier to free mem. (Taking care of DynLayer is a hassle but the object > isn't). > 8an > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev > |
|
From: Eytan H. <ey...@tr...> - 2001-02-25 08:42:32
|
Which makes it slightly slower (but I'm not compaining) 8an |
|
From: Eytan H. <ey...@tr...> - 2001-02-25 08:41:49
|
As I have mentioned (more then once) the delete operator works but only tested it on actual objects. Not DHTML components(layers,divs,nodes) for those you have a whole new set of rules. So we need to find out how to = free actual elements. 8an |
|
From: Jeff <jef...@ea...> - 2001-02-25 07:49:23
|
Whew! Go away for a day and the messages pile up! Raides J. - I was under the impression that this (JIT) was essentially the case for both browsers, but I could be mistaken. The following is from the Netscape JavaScript 1.3 reference, describing a function as opposed to a function object created explicitly: ------------------ Function objects created with the Function constructor are evaluated each time they are used. This is less efficient than declaring a function and calling it within your code, because declared functions are compiled. ------------------- Eytan - 1) Yes, I think I will be accepting tests, although I have not yet set up the site to do so (but feel free to send them to me and they will be among the first that I put up). 2) Duff's Device - What browser were you using? Because IE does much better at either compiling or optimizing its code, using something like Duff's Device in that case might actually slow it down, though usually only by a slight amount (as you experienced) due to the overhead of the added code. But I believe that this is, in most cases, a small price to pay for more predictable cross browser performance (i.e., should be MUCH faster in Netscape). If it was Netscape you were using, which version? I would assume that all the 4.x broswers behave essentially the same, but I haven't had a chance to test it on NS6. This is an area that I am still looking into and I just have not had the time to do thorough investigations yet. 3) Yes, I think it is clear that some sort of separation between fundamental optimization and DHTML performance is needed, but I'm not even half way done with the fundamentals yet!! :-) 4) I'd love to make it a serious site. Right now, however, it's just on my personal web space at Earthlink, which is is quite limited in terms of what I am allowed to do with it. I could probably move it to an NT box at work which would also give me access to MS SQL Server and ColdFusion, both of which I have used for many projects. Jeff Greenberg je...@we... |
|
From: Doug M. <do...@cr...> - 2001-02-25 01:40:30
|
Sounds good to me... ----- Original Message ----- From: "Raymond Smith" <dst...@or...> To: <dyn...@li...> Sent: Saturday, February 24, 2001 5:13 PM Subject: [Dynapi-Dev] nameology > Since DynAPI3 stuck the fear of God into some individuals unnessarily, how > about adopting the naming syntax used by Linux. > > 1) Stable releases are "even" numbered. 2.0, 2.2, 2.4, etc... > 2) Working releases are "odd" numbered. 2.1, 2.3, 2.5, etc... > > Updates can happen to both, development can be concurrent. Odd's are more > experimental in nature, and not meant for "public consumption". And this is > pretty easy to understand and add to the DynAPI F.A.Q. so new users > understand. > > Thoughts? > > Ray > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev --- Outgoing mail is certified Virus Free by AVG Free Edition Download at: http://www.grisoft.com/html/us_index.cfm Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.231 / Virus Database: 112 - Release Date: 2/12/01 |
|
From: Doug M. <do...@cr...> - 2001-02-25 01:39:13
|
I've just updated my JS and found no such problem. Win98 IE 5.5 ----- Original Message ----- From: "nobody" <no...@so...> To: <no...@so...> Sent: Saturday, February 24, 2001 4:07 PM Subject: [Dynapi-Dev] [ dynapi-Bugs-404007 ] Events in Images (IE 5.5) > Artifact #404007, was updated on 2001-02-24 16:07 > You can respond by visiting: > http://sourceforge.net/tracker/?func=detail&atid=105757&aid=404007&group_id= 5757 > > Category: Core API > Group: None > Status: Open > Priority: 6 > Submitted By: Robert Rainwater > Assigned to: Nobody/Anonymous > Summary: Events in Images (IE 5.5) > > Initial Comment: > Using the dynapi_2001_02_24 snapshot, events in layers > in IE 5.5 do not appear to be fired. > > For example, in the dynapi.gui.button.html example, > the onmousedown events fail to fire when doing a > mousedown on the image part of a button. > > ---------------------------------------------------------------------- > > You can respond by visiting: > http://sourceforge.net/tracker/?func=detail&atid=105757&aid=404007&group_id= 5757 > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev --- Outgoing mail is certified Virus Free by AVG Free Edition Download at: http://www.grisoft.com/html/us_index.cfm Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.231 / Virus Database: 112 - Release Date: 2/12/01 |
|
From: Monica K. <mo...@ko...> - 2001-02-25 01:18:39
|
Hi all,
Is createElement still unsupported in NS4.x? I haven't seen the error
message
mentioned below ("createElement is not a function"), but I have run into one
problem:
When resizing netscape 4.7x, the first resize doesn't recreate the layers in
resizeHandler(), but if you resize again (without reloading), the layers are
created. The layers are definitely deleted the first time, but not
recreated.
Seems like the first time you resize is the only time there is a problem.
Anyone know why this happens or what the workaround is?
Thanks,
Monica
-----Original Message-----
From: Michael Pemberton [mailto:mp...@ph...]
Sent: Wednesday, February 07, 2001 8:48 PM
To: dyn...@li...
Subject: Re: [Dynapi-Dev] Q: from HTML3.
> Dear Dynapi experts,
> after much ignorance I managed to make up something which works as I like.
> It is compliant with the DOM level 2 (http://www.w3.org/TR/DOM-Level-2/).
>
> I was wondering what should I do to "convert" this code so that it use
DynApi.
> Infact, currently this code does not run with Netscape 4.7X as Netscape
reports that
> "createElement is not a function"
>
This currently an unsupported feature in NS4.x
>
> <HTML>
> <HEAD>
> <TITLE>Untitled</TITLE>
> </HEAD>
> <BODY ID="oBody" >
> <h1>Product level</h1>
> <FORM name="formName" method="POST" action="/cgi-bin/submit.cgi"">
> <SELECT ID="oSelect" SIZE="3" ></SELECT>
> <INPUT type="TEXT" ID="oData" >
> <INPUT TYPE="button"
> VALUE="add to list"
> onclick="var oOption = document.createElement('OPTION');
> oOption.text=oData.value;
> oSelect.add(oOption);">
I think this could be replaced with:
onclick="oSelect.options[oSelect.options.length] = new
Option(oData.value,oData.value);"
I'm just going off the NS JS1.3 Docs. I haven't tried this myself so I'm not
sure how it
will work in IE.
> <INPUT TYPE="button" VALUE="Submit">
> </FORM>
>
> </BODY>
> </HTML>
--
Michael Pemberton
mp...@ph...
ICQ: 12107010
_______________________________________________
Dynapi-Dev mailing list
Dyn...@li...
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
|
|
From: Raymond S. <dst...@or...> - 2001-02-25 01:15:30
|
Since DynAPI3 stuck the fear of God into some individuals unnessarily, how about adopting the naming syntax used by Linux. 1) Stable releases are "even" numbered. 2.0, 2.2, 2.4, etc... 2) Working releases are "odd" numbered. 2.1, 2.3, 2.5, etc... Updates can happen to both, development can be concurrent. Odd's are more experimental in nature, and not meant for "public consumption". And this is pretty easy to understand and add to the DynAPI F.A.Q. so new users understand. Thoughts? Ray |
|
From: nobody <no...@so...> - 2001-02-25 00:05:53
|
Artifact #404007, was updated on 2001-02-24 16:07 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=105757&aid=404007&group_id=5757 Category: Core API Group: None Status: Open Priority: 6 Submitted By: Robert Rainwater Assigned to: Nobody/Anonymous Summary: Events in Images (IE 5.5) Initial Comment: Using the dynapi_2001_02_24 snapshot, events in layers in IE 5.5 do not appear to be fired. For example, in the dynapi.gui.button.html example, the onmousedown events fail to fire when doing a mousedown on the image part of a button. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=105757&aid=404007&group_id=5757 |
|
From: Robert R. <rra...@ya...> - 2001-02-24 22:14:47
|
By the way are you still planning on putting in the dynobject? It shouldn't be very hard to implement since you have already done it in the DynaCore. But it will require that everybody includes in their pages though. -- // Robert Rainwater On 2/24/2001, 4:56:31 PM EST, Pascal wrote about "[Dynapi-Dev] setContent": > oops! :) > Pascal Bestebroer > pa...@dy... > http://www.dynamic-core.net >> -----Oorspronkelijk bericht----- >> Van: dyn...@li... >> [mailto:dyn...@li...]Namens Robert Rainwater >> Verzonden: zaterdag 24 februari 2001 22:49 >> Aan: DynAPI Development List >> Onderwerp: Re: [Dynapi-Dev] setContent >> >> >> >> I was wrong. It was the new code after all. I updated cvs to fix the >> calls to createElement. They now use the dynlayer method, not the >> static method. >> >> -- >> // Robert Rainwater >> >> On 2/24/2001, 2:54:36 PM EST, Robert wrote about "[Dynapi-Dev] >> setContent": >> >> >> > I havent tested much yet, but all of the examples that use setContent >> > with labels seem to be broken (atleast in IE 55). For instance >> the pushpanel and >> > scrollpane examples are broken. I don't think this is new though, >> > because it seems like I've noticed it before. >> >> >> >> ---------------------- >> DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/ >> DynAPI Homepage: http://dynapi.sourceforge.net/ >> >> >> >> _______________________________________________ >> Dynapi-Dev mailing list >> Dyn...@li... >> http://lists.sourceforge.net/lists/listinfo/dynapi-dev >> > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev ---------------------- DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/ DynAPI Homepage: http://dynapi.sourceforge.net/ |
|
From: Eytan H. <ey...@tr...> - 2001-02-24 22:02:48
|
I think we(you) should divide the test in to two parts: * Good programming * DHTML performance What about making this a serious page with serverside scripts to submit tests and results. (I would do it but I am only fluent in ASP and ISAPI and rusty in PERL if you have a WinBox I could do it) 8an |
|
From: Eytan H. <ey...@tr...> - 2001-02-24 22:00:02
|
The only thing I still want to change is the way that all widgets inherit from DynLayer. Why don't we just make them have a dynlayer object then it is easier to free mem. (Taking care of DynLayer is a hassle but the object isn't). 8an |
|
From: Eytan H. <ey...@tr...> - 2001-02-24 21:57:20
|
First of all I wanted to know if you are accepting tests! Another thing is that your great Duff dude was slower on my PIII by 1 ms. No biggie but why? 8an |
|
From: Pascal B. <pa...@dy...> - 2001-02-24 21:55:40
|
oops! :) Pascal Bestebroer pa...@dy... http://www.dynamic-core.net > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Robert Rainwater > Verzonden: zaterdag 24 februari 2001 22:49 > Aan: DynAPI Development List > Onderwerp: Re: [Dynapi-Dev] setContent > > > > I was wrong. It was the new code after all. I updated cvs to fix the > calls to createElement. They now use the dynlayer method, not the > static method. > > -- > // Robert Rainwater > > On 2/24/2001, 2:54:36 PM EST, Robert wrote about "[Dynapi-Dev] > setContent": > > > > I havent tested much yet, but all of the examples that use setContent > > with labels seem to be broken (atleast in IE 55). For instance > the pushpanel and > > scrollpane examples are broken. I don't think this is new though, > > because it seems like I've noticed it before. > > > > ---------------------- > DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/ > DynAPI Homepage: http://dynapi.sourceforge.net/ > > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev > |
175 messages has been excluded from this view by a project administrator.
