Menu
▾
▴
dynapi-dev
|
From: C K. <cki...@ne...> - 2003-10-22 20:43:34
|
I first started using DynAPI because I needed a cross-browser solution = for consistency across DOM/non-DOM browsers in ecommerce web apps. This = seemed to have been the original focus with CBScript and DynAPI2, but lately = the focus seems to have changed to more of an advanced app factory (still a = good thing). =20 I am still busy trying to port DynAPI3 Oct. 4, 2003 snapshot for = backwards compatibility with NN4.03 and IE4, which when it is finished will = probably serve me well into the distant future as a browser paleontologist. =20 I would like to see a poll of current users and developers for = determining the primary focus: advanced functionality vs. wider cross-browser = support. With the DOM, anything is possible, so the need for a JS wrapper API = becomes less imperative. DynAPI has been great for both so far, but I see people wanting to move forward and drop support. I can't do that, but I'm sure DynAPI will still be great either way. =20 Thanks! =20 Christopher Kissinger=20 Web Development Consultant =20 |
|
From: Doug M. <do...@cr...> - 2003-10-22 21:06:58
|
MessageI understood we where still supporting NS 4 and IE 4 Although it is true that not many people actually test in these = browsers. When I am finished my current contract (assuming I don't sign another) I = will devote some time to a complete end-to-end testing of DynAPI.. What was that tentative release date? ----- Original Message -----=20 From: C Kissinger=20 To: dyn...@li...=20 Sent: Wednesday, October 22, 2003 1:41 PM Subject: [Dynapi-Dev] Old Browser Support I first started using DynAPI because I needed a cross-browser solution = for consistency across DOM/non-DOM browsers in ecommerce web apps. This = seemed to have been the original focus with CBScript and DynAPI2, but = lately the focus seems to have changed to more of an advanced app = factory (still a good thing). I am still busy trying to port DynAPI3 Oct. 4, 2003 snapshot for = backwards compatibility with NN4.03 and IE4, which when it is finished = will probably serve me well into the distant future as a browser = paleontologist. I would like to see a poll of current users and developers for = determining the primary focus: advanced functionality vs. wider = cross-browser support. With the DOM, anything is possible, so the need = for a JS wrapper API becomes less imperative. DynAPI has been great for = both so far, but I see people wanting to move forward and drop support. = I can't do that, but I'm sure DynAPI will still be great either way. Thanks! Christopher Kissinger=20 Web Development Consultant --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.529 / Virus Database: 324 - Release Date: 10/16/03 |
|
From: Raymond I. <xw...@ya...> - 2003-10-22 21:40:18
|
We should have a release early next year. -- Raymond Irving --- Doug Melvin <do...@cr...> wrote: > MessageI understood we where still supporting NS 4 > and IE 4 > Although it is true that not many people actually > test in these browsers. > > When I am finished my current contract (assuming I > don't sign another) I will devote some time > to a complete end-to-end testing of DynAPI.. > > What was that tentative release date? > ----- Original Message ----- > From: C Kissinger > To: dyn...@li... > Sent: Wednesday, October 22, 2003 1:41 PM > Subject: [Dynapi-Dev] Old Browser Support > > > I first started using DynAPI because I needed a > cross-browser solution for consistency across > DOM/non-DOM browsers in ecommerce web apps. This > seemed to have been the original focus with CBScript > and DynAPI2, but lately the focus seems to have > changed to more of an advanced app factory (still a > good thing). > > I am still busy trying to port DynAPI3 Oct. 4, > 2003 snapshot for backwards compatibility with > NN4.03 and IE4, which when it is finished will > probably serve me well into the distant future as a > browser paleontologist. > > I would like to see a poll of current users and > developers for determining the primary focus: > advanced functionality vs. wider cross-browser > support. With the DOM, anything is possible, so the > need for a JS wrapper API becomes less imperative. > DynAPI has been great for both so far, but I see > people wanting to move forward and drop support. I > can't do that, but I'm sure DynAPI will still be > great either way. > > Thanks! > > Christopher Kissinger > Web Development Consultant > > > > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system > (http://www.grisoft.com). > Version: 6.0.529 / Virus Database: 324 - Release > Date: 10/16/03 > __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com |
|
From: Raymond I. <xw...@ya...> - 2003-10-22 21:15:15
|
I say we also try and include NN 4.03 but it's just that NN4.03 has a major problem with functions not return a value. "With the DOM, anything is possible, so the need for a JS wrapper API becomes less imperative." I don't think so! I thought that DOM-Browsers would make DynAPI go away but I was wrong. Over the past few months I've had nightmares trying to get apps to display and work the same in all three of the major browsers. -- Raymond Irving --- C Kissinger <cki...@ne...> wrote: > I first started using DynAPI because I needed a > cross-browser solution for > consistency across DOM/non-DOM browsers in ecommerce > web apps. This seemed > to have been the original focus with CBScript and > DynAPI2, but lately the > focus seems to have changed to more of an advanced > app factory (still a good > thing). > > I am still busy trying to port DynAPI3 Oct. 4, 2003 > snapshot for backwards > compatibility with NN4.03 and IE4, which when it is > finished will probably > serve me well into the distant future as a browser > paleontologist. > > I would like to see a poll of current users and > developers for determining > the primary focus: advanced functionality vs. wider > cross-browser support. > With the DOM, anything is possible, so the need for > a JS wrapper API becomes > less imperative. DynAPI has been great for both so > far, but I see people > wanting to move forward and drop support. I can't do > that, but I'm sure > DynAPI will still be great either way. > > Thanks! > > > Christopher Kissinger > Web Development Consultant > > > > > __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com |
|
From: C K. <cki...@ne...> - 2003-10-23 07:07:36
|
Well I got the examples from Create Layer to Hover Animation in that snapshot to work in old browsers now (except TabManager because my = laptop doesn't have a separate numeric keypad with arrows), but one major = stumbling block which maybe someone can answer. In NN4.03 almost all examples = shoot a "JavaScript Error: too much recursion" onmousedown and onmouseup in = document areas of the page. Two of the same error for every click. Any ideas? Christopher Kissinger=20 Web Development Consultant >>> -----Original Message----- >>> From: dyn...@li...=20 >>> [mailto:dyn...@li...] On Behalf=20 >>> Of Raymond Irving >>> Sent: Wednesday, October 22, 2003 4:09 PM >>> To: dyn...@li... >>> Subject: Re: [Dynapi-Dev] Old Browser Support >>> =20 >>> =20 >>> =20 >>> I say we also try and include NN 4.03 but it's just >>> that NN4.03 has a major problem with functions not >>> return a value. >>> =20 >>> "With the DOM, anything is possible, so the need for a >>> JS wrapper API becomes less imperative." >>> =20 >>> I don't think so! I thought that DOM-Browsers would >>> make DynAPI go away but I was wrong. Over the past few >>> months I've had nightmares trying to get apps to >>> display and work the same in all three of the major >>> browsers. >>> =20 >>> -- >>> Raymond Irving >>> =20 >>> --- C Kissinger <cki...@ne...> wrote: >>> > I first started using DynAPI because I needed a >>> > cross-browser solution for >>> > consistency across DOM/non-DOM browsers in ecommerce >>> > web apps. This seemed >>> > to have been the original focus with CBScript and >>> > DynAPI2, but lately the >>> > focus seems to have changed to more of an advanced >>> > app factory (still a good >>> > thing). >>> > =20 >>> > I am still busy trying to port DynAPI3 Oct. 4, 2003 >>> > snapshot for backwards >>> > compatibility with NN4.03 and IE4, which when it is >>> > finished will probably >>> > serve me well into the distant future as a browser >>> > paleontologist. >>> > =20 >>> > I would like to see a poll of current users and >>> > developers for determining >>> > the primary focus: advanced functionality vs. wider >>> > cross-browser support. >>> > With the DOM, anything is possible, so the need for >>> > a JS wrapper API becomes >>> > less imperative. DynAPI has been great for both so >>> > far, but I see people >>> > wanting to move forward and drop support. I can't do >>> > that, but I'm sure >>> > DynAPI will still be great either way. >>> > =20 >>> > Thanks! >>> > =20 >>> >=20 >>> > Christopher Kissinger=20 >>> > Web Development Consultant >>> >=20 >>> >=20 >>> > =20 >>> >=20 >>> >=20 >>> =20 >>> =20 >>> __________________________________ >>> Do you Yahoo!? >>> The New Yahoo! Shopping - with improved product search >>> http://shopping.yahoo.com >>> =20 >>> =20 |
|
From: Doug M. <do...@cr...> - 2003-10-24 08:02:21
|
"JavaScript Error: too much recursion" does not nessesarily mean just recursion. It can also be triggered by a very large loop. Generally though, it will be tiggered by a recursive loop, just as one that manipulates children. I found in previous version I got the error in my tree widget. and sometimes saw the error when using methods such as DynAPI.Document.all(). Other potential areas are any method which tries to access all children of a layer. so deleteallchildren and the such. You best bet is to find each recursive function and add a debuggin message so that you will know which function is genreating the error. ----- Original Message ----- From: "C Kissinger" <cki...@ne...> To: <dyn...@li...> Sent: Thursday, October 23, 2003 3:06 AM Subject: RE: [Dynapi-Dev] Old Browser Support > Well I got the examples from Create Layer to Hover Animation in that > snapshot to work in old browsers now (except TabManager because my laptop > doesn't have a separate numeric keypad with arrows), but one major stumbling > block which maybe someone can answer. In NN4.03 almost all examples shoot a > c onmousedown and onmouseup in document > areas of the page. Two of the same error for every click. Any ideas? > > Christopher Kissinger > Web Development Consultant > > > >>> -----Original Message----- > >>> From: dyn...@li... > >>> [mailto:dyn...@li...] On Behalf > >>> Of Raymond Irving > >>> Sent: Wednesday, October 22, 2003 4:09 PM > >>> To: dyn...@li... > >>> Subject: Re: [Dynapi-Dev] Old Browser Support > >>> > >>> > >>> > >>> I say we also try and include NN 4.03 but it's just > >>> that NN4.03 has a major problem with functions not > >>> return a value. > >>> > >>> "With the DOM, anything is possible, so the need for a > >>> JS wrapper API becomes less imperative." > >>> > >>> I don't think so! I thought that DOM-Browsers would > >>> make DynAPI go away but I was wrong. Over the past few > >>> months I've had nightmares trying to get apps to > >>> display and work the same in all three of the major > >>> browsers. > >>> > >>> -- > >>> Raymond Irving > >>> > >>> --- C Kissinger <cki...@ne...> wrote: > >>> > I first started using DynAPI because I needed a > >>> > cross-browser solution for > >>> > consistency across DOM/non-DOM browsers in ecommerce > >>> > web apps. This seemed > >>> > to have been the original focus with CBScript and > >>> > DynAPI2, but lately the > >>> > focus seems to have changed to more of an advanced > >>> > app factory (still a good > >>> > thing). > >>> > > >>> > I am still busy trying to port DynAPI3 Oct. 4, 2003 > >>> > snapshot for backwards > >>> > compatibility with NN4.03 and IE4, which when it is > >>> > finished will probably > >>> > serve me well into the distant future as a browser > >>> > paleontologist. > >>> > > >>> > I would like to see a poll of current users and > >>> > developers for determining > >>> > the primary focus: advanced functionality vs. wider > >>> > cross-browser support. > >>> > With the DOM, anything is possible, so the need for > >>> > a JS wrapper API becomes > >>> > less imperative. DynAPI has been great for both so > >>> > far, but I see people > >>> > wanting to move forward and drop support. I can't do > >>> > that, but I'm sure > >>> > DynAPI will still be great either way. > >>> > > >>> > Thanks! > >>> > > >>> > > >>> > Christopher Kissinger > >>> > Web Development Consultant > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > >>> > >>> __________________________________ > >>> Do you Yahoo!? > >>> The New Yahoo! Shopping - with improved product search > >>> http://shopping.yahoo.com > >>> > >>> > > > > ------------------------------------------------------- > This SF.net email is sponsored by OSDN developer relations > Here's your chance to show off your extensive product knowledge > We want to know what you know. Tell us and you have a chance to win $100 > http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://www.mail-archive.com/dyn...@li.../ > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.529 / Virus Database: 324 - Release Date: 10/16/03 |
|
From: Daniel T. <de...@ti...> - 2003-10-24 15:48:47
|
Hi! I was thinking of a way to keep the widget and object documentation up to date better, that is that I could set up a database and make a webadmin to that so we could update the docs smoothly and have a better overview of what objects/widgets that needs to be documented, and what is missing and so on. Then for release we just make html of all the info stored in the db and add it to cvs. What do you all think of this? What type of data we need (fill in on this) Object Name or Widget Name Constructor with comments Properties with comments Functions with comments Private/public Methods with comments Examples We could also make a comment to each file so we all know what that file does. What do you think? Regards Daniel |
|
From: Daniel T. <de...@ti...> - 2003-10-25 19:05:42
|
Hi! I was thinking of a way to keep the widget and object documentation up to date better, that is that I could set up a database and make a webadmin to that so we could update the docs smoothly and have a better overview of what objects/widgets that needs to be documented, and what is missing and so on. Then for release we just make html of all the info stored in the db and add it to cvs. What do you all think of this? What type of data we need (fill in on this) Object Name or Widget Name Constructor with comments Properties with comments Functions with comments Private/public Methods with comments Examples We could also make a comment to each file so we all know what that file does. What do you think? Regards Daniel |
|
From: Leif W <war...@us...> - 2003-10-27 05:17:45
|
Think this sounds like a good idea. As a milestone marker, we could keep a percentage of documentation completed on the main page. Could have some color code, red - no docs, yellow, partially documented, green, fully documented. Could have something like a treview of the API, showing each node in the color based on it's children. You look at the top node (it's yellow most of the time), so you know something somewhere needs to be documented. Expanding the node, you see one (or more) nodes in green and yellow or red states. Expanding a yellow node, you find a list of items all green except one item is yellow, so you finish documenting that and make it green, then its parent becomes green, and you have done some work. :-) Leif ----- Original Message ----- From: "Daniel Tiru" <de...@ti...> To: <dyn...@li...> Sent: Friday, October 24, 2003 8:48 AM Subject: [Dynapi-Dev] Object / Widget documentation > Hi! > > I was thinking of a way to keep the widget and object documentation up > to date better, that is that I could set up a database and make a > webadmin to that so we could update the docs smoothly and have a better > overview of what objects/widgets that needs to be documented, and what > is missing and so on. > > Then for release we just make html of all the info stored in the db and > add it to cvs. What do you all think of this? > > What type of data we need (fill in on this) > Object Name or Widget Name > Constructor with comments > Properties with comments > Functions with comments > Private/public Methods with comments > Examples > > We could also make a comment to each file so we all know what that file > does. > > What do you think? > > Regards > Daniel > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: The SF.net Donation Program. > Do you like what SourceForge.net is doing for the Open > Source Community? Make a contribution, and help us add new > features and functionality. Click here: http://sourceforge.net/donate/ > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://www.mail-archive.com/dyn...@li.../ > > |
|
From: Raymond I. <xw...@ya...> - 2003-10-24 11:08:54
|
This might have something to do with NN4.03 and mouse_ns4.js. Something to do with the event listeners for the document object. -- Raymond Irving --- C Kissinger <cki...@ne...> wrote: > Well I got the examples from Create Layer to Hover > Animation in that > snapshot to work in old browsers now (except > TabManager because my laptop > doesn't have a separate numeric keypad with arrows), > but one major stumbling > block which maybe someone can answer. In NN4.03 > almost all examples shoot a > "JavaScript Error: too much recursion" onmousedown > and onmouseup in document > areas of the page. Two of the same error for every > click. Any ideas? > > Christopher Kissinger > Web Development Consultant > > > >>> -----Original Message----- > >>> From: dyn...@li... > >>> [mailto:dyn...@li...] > On Behalf > >>> Of Raymond Irving > >>> Sent: Wednesday, October 22, 2003 4:09 PM > >>> To: dyn...@li... > >>> Subject: Re: [Dynapi-Dev] Old Browser Support > >>> > >>> > >>> > >>> I say we also try and include NN 4.03 but it's > just > >>> that NN4.03 has a major problem with functions > not > >>> return a value. > >>> > >>> "With the DOM, anything is possible, so the > need for a > >>> JS wrapper API becomes less imperative." > >>> > >>> I don't think so! I thought that DOM-Browsers > would > >>> make DynAPI go away but I was wrong. Over the > past few > >>> months I've had nightmares trying to get apps > to > >>> display and work the same in all three of the > major > >>> browsers. > >>> > >>> -- > >>> Raymond Irving > >>> > >>> --- C Kissinger <cki...@ne...> > wrote: > >>> > I first started using DynAPI because I needed > a > >>> > cross-browser solution for > >>> > consistency across DOM/non-DOM browsers in > ecommerce > >>> > web apps. This seemed > >>> > to have been the original focus with CBScript > and > >>> > DynAPI2, but lately the > >>> > focus seems to have changed to more of an > advanced > >>> > app factory (still a good > >>> > thing). > >>> > > >>> > I am still busy trying to port DynAPI3 Oct. > 4, 2003 > >>> > snapshot for backwards > >>> > compatibility with NN4.03 and IE4, which when > it is > >>> > finished will probably > >>> > serve me well into the distant future as a > browser > >>> > paleontologist. > >>> > > >>> > I would like to see a poll of current users > and > >>> > developers for determining > >>> > the primary focus: advanced functionality vs. > wider > >>> > cross-browser support. > >>> > With the DOM, anything is possible, so the > need for > >>> > a JS wrapper API becomes > >>> > less imperative. DynAPI has been great for > both so > >>> > far, but I see people > >>> > wanting to move forward and drop support. I > can't do > >>> > that, but I'm sure > >>> > DynAPI will still be great either way. > >>> > > >>> > Thanks! > >>> > > >>> > > >>> > Christopher Kissinger > >>> > Web Development Consultant > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > >>> > >>> __________________________________ > >>> Do you Yahoo!? > >>> The New Yahoo! Shopping - with improved product > search > >>> http://shopping.yahoo.com > >>> > >>> > > > > ------------------------------------------------------- > This SF.net email is sponsored by OSDN developer > relations > Here's your chance to show off your extensive > product knowledge > We want to know what you know. Tell us and you have > a chance to win $100 > http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://www.mail-archive.com/dyn...@li.../ __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com |
|
From: Kevin <ke...@ke...> - 2003-10-22 21:23:19
|
MessageThe focus should include NS4 & IE4 as IMO that is what makes = Dynapi3. DOM only APIs are out there but do we want another one? - Kevin =20 ----- Original Message -----=20 From: C Kissinger=20 To: dyn...@li...=20 Sent: Wednesday, October 22, 2003 6:41 PM Subject: [Dynapi-Dev] Old Browser Support I first started using DynAPI because I needed a cross-browser solution = for consistency across DOM/non-DOM browsers in ecommerce web apps. This = seemed to have been the original focus with CBScript and DynAPI2, but = lately the focus seems to have changed to more of an advanced app = factory (still a good thing). I am still busy trying to port DynAPI3 Oct. 4, 2003 snapshot for = backwards compatibility with NN4.03 and IE4, which when it is finished = will probably serve me well into the distant future as a browser = paleontologist. I would like to see a poll of current users and developers for = determining the primary focus: advanced functionality vs. wider = cross-browser support. With the DOM, anything is possible, so the need = for a JS wrapper API becomes less imperative. DynAPI has been great for = both so far, but I see people wanting to move forward and drop support. = I can't do that, but I'm sure DynAPI will still be great either way. Thanks! Christopher Kissinger=20 Web Development Consultant |
|
From: Leif W <war...@us...> - 2003-10-23 15:25:32
|
MessageRegarding old browsers or new browsers... if you need some = support for a browser, knock yourself out and write it. :-) Hopefully = the support for all browsers can coexist within the API? Or does the = backward compatibility (adding all the return values, etc, for NN 4.03) = break the newer browsers? If so, maybe there's a need to split support = into two flavors? DynAPI for current / modern browsers, and err, how = about DynoAPI for the Dinosaurs. ;-) Leif ----- Original Message -----=20 From: C Kissinger=20 To: dyn...@li...=20 Sent: Wednesday, October 22, 2003 1:41 PM Subject: [Dynapi-Dev] Old Browser Support I first started using DynAPI because I needed a cross-browser solution = for consistency across DOM/non-DOM browsers in ecommerce web apps. This = seemed to have been the original focus with CBScript and DynAPI2, but = lately the focus seems to have changed to more of an advanced app = factory (still a good thing). I am still busy trying to port DynAPI3 Oct. 4, 2003 snapshot for = backwards compatibility with NN4.03 and IE4, which when it is finished = will probably serve me well into the distant future as a browser = paleontologist. I would like to see a poll of current users and developers for = determining the primary focus: advanced functionality vs. wider = cross-browser support. With the DOM, anything is possible, so the need = for a JS wrapper API becomes less imperative. DynAPI has been great for = both so far, but I see people wanting to move forward and drop support. = I can't do that, but I'm sure DynAPI will still be great either way. Thanks! Christopher Kissinger=20 Web Development Consultant |
|
From: Michael B. <mi...@mi...> - 2003-10-25 16:59:36
|
>> I would like to see a poll of current users and developers for determining >> the primary focus: My personal feeling is that everything up to ns4.7 type browsers is dead and to develop for these browsers I feel is pointless. I have no plans for the IOS library or VDE to have backward compatibility to older browsers. A project like VDE (I believe) will never work in NS4.7 or MacIE5, and I/we should not spend trying to make it sorta work. There is just some things that those browsers where not meant to do and if you push them to hard they will totally slow down they system, freeze or you guest it... crash. Leaving the user with a bad DynAPI taste in their mouth. Other then that I'm in total agreement with Leif. DynoAPI funny :) Stay healthy :) Michael Den 03-10-23 16.08, skrev "Leif W" <war...@us...>: > Regarding old browsers or new browsers... if you need some support for a > browser, knock yourself out and write it. :-) Hopefully the support for all > browsers can coexist within the API? Or does the backward compatibility > (adding all the return values, etc, for NN 4.03) break the newer browsers? If > so, maybe there's a need to split support into two flavors? DynAPI for > current / modern browsers, and err, how about DynoAPI for the Dinosaurs. ;-) > > Leif > ----- Original Message ----- >> From: C Kissinger <mailto:cki...@ne...> >> To: dyn...@li... >> Sent: Wednesday, October 22, 2003 1:41 PM >> Subject: [Dynapi-Dev] Old Browser Support >> >> I first started using DynAPI because I needed a cross-browser solution for >> consistency across DOM/non-DOM browsers in ecommerce web apps. This seemed to >> have been the original focus with CBScript and DynAPI2, but lately the focus >> seems to have changed to more of an advanced app factory (still a good >> thing). >> >> I am still busy trying to port DynAPI3 Oct. 4, 2003 snapshot for backwards >> compatibility with NN4.03 and IE4, which when it is finished will probably >> serve me well into the distant future as a browser paleontologist. >> >> I would like to see a poll of current users and developers for determining >> the primary focus: advanced functionality vs. wider cross-browser support. >> With the DOM, anything is possible, so the need for a JS wrapper API becomes >> less imperative. DynAPI has been great for both so far, but I see people >> wanting to move forward and drop support. I can't do that, but I'm sure >> DynAPI will still be great either way. >> >> Thanks! >> >> Christopher Kissinger >> Web Development Consultant >> >> >> |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X