From: Jeff <jef...@ea...> - 2001-02-18 01:11:48
|
Excellent. I think it's a great idea. Jeff Greenberg je...@we... Robert Rainwater wrote: > I put a demo site at http://dynapi.sourceforge.net/dynapi/ of the type > > of site we could use for the main page. This would allow the site to > be a bit more dynamic and up to date. > > So what do ya think? > > -- > // Robert Rainwater > ---------------------- > 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: Raymond S. <dst...@or...> - 2001-02-18 02:42:03
|
While I agree that the WebOS solution is overkill for the DynAPI. The Loadpanel approach is not the most solid bridge to deliver dynamic (dynamic being defined as 'dynamic server/client interaction') content. I think we need to explore alternatives/improvements to the glue between the DynAPI and the wealth of server-side power that exists out there. JS is client. It performs best in that world. The server-side unlocks a whole new world of "dynamics" that currently tend to funnel into very "dead" client interfaces. That's what peaked my interest in the DynAPI in the first place. I loath the limited realm that FLASH delivers along with its pathetic CPU chewing rendering engine. I like the fact that the DynAPI leaves options 100% open for me to pick and choose front-to-back delivery platforms. Currently loadpanel is probably the weakest link supporting the DynAPI platform. But it is the "only" link we currently have to bridge between two very different worlds. Fix and optimize it...., then you will see magic... The "art" of client side interface will meet the "fandango dance" of the server-side apps and really enhance the overall forumla for developing and delivering the web experiences of tomorrow. Ray |
From: Michael P. <mp...@ph...> - 2001-02-18 13:08:11
|
The loadpanel is not the only method of downloading content from a server. I'm in the process of finishing off a method of downloading content without the need to create a lot of new objects and it will be more powerful than the loadpanel. At the moment, it is still a WIP but is close to completion. It can be seen in action here. You'll see that it executed JS and also extracts the various parts of the downloaded page. The main "bug" at the moment is that the MAC versions of java do not include the required classes for downloading the content. there is no easy way of fixing this unless you write the code to work with the java plugin and force all your clients to download the java plugin. Raymond Smith wrote: > While I agree that the WebOS solution is overkill for the DynAPI. The > Loadpanel approach is not the most solid bridge to deliver dynamic (dynamic > being defined as 'dynamic server/client interaction') content. I think we > need to explore alternatives/improvements to the glue between the DynAPI and > the wealth of server-side power that exists out there. > > JS is client. It performs best in that world. The server-side unlocks a > whole new world of "dynamics" that currently tend to funnel into very "dead" > client interfaces. That's what peaked my interest in the DynAPI in the > first place. I loath the limited realm that FLASH delivers along with its > pathetic CPU chewing rendering engine. I like the fact that the DynAPI > leaves options 100% open for me to pick and choose front-to-back delivery > platforms. > > Currently loadpanel is probably the weakest link supporting the DynAPI > platform. But it is the "only" link we currently have to bridge between two > very different worlds. Fix and optimize it...., > > then you will see magic... > > The "art" of client side interface will meet the "fandango dance" of the > server-side apps and really enhance the overall forumla for developing and > delivering the web experiences of tomorrow. > > Ray > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev -- Michael Pemberton mp...@ph... ICQ: 12107010 |
From: Doug M. <do...@cr...> - 2001-02-18 19:29:20
|
Very nice! How far back is it compatable? NS 4.what IE? ----- Original Message -----=20 From: Michael Pemberton=20 To: dyn...@li...=20 Sent: Sunday, February 18, 2001 5:05 AM Subject: Re: [Dynapi-Dev] Dynamic Loading. The loadpanel is not the only method of downloading content from a = server.=20 I'm in the process of finishing off a method of downloading content = without the need to create a lot of new objects and it will be more = powerful than the loadpanel.=20 At the moment, it is still a WIP but is close to completion. It can = be seen in action here.=20 You'll see that it executed JS and also extracts the various parts of = the downloaded page.=20 The main "bug" at the moment is that the MAC versions of java do not = include the required classes for downloading the content. there is no = easy way of fixing this unless you write the code to work with the java = plugin and force all your clients to download the java plugin.=20 Raymond Smith wrote:=20 While I agree that the WebOS solution is overkill for the DynAPI. = The=20 Loadpanel approach is not the most solid bridge to deliver dynamic = (dynamic=20 being defined as 'dynamic server/client interaction') content. I = think we=20 need to explore alternatives/improvements to the glue between the = DynAPI and=20 the wealth of server-side power that exists out there.=20 JS is client. It performs best in that world. The server-side = unlocks a=20 whole new world of "dynamics" that currently tend to funnel into = very "dead"=20 client interfaces. That's what peaked my interest in the DynAPI in = the=20 first place. I loath the limited realm that FLASH delivers along = with its=20 pathetic CPU chewing rendering engine. I like the fact that the = DynAPI=20 leaves options 100% open for me to pick and choose front-to-back = delivery=20 platforms.=20 Currently loadpanel is probably the weakest link supporting the = DynAPI=20 platform. But it is the "only" link we currently have to bridge = between two=20 very different worlds. Fix and optimize it....,=20 then you will see magic...=20 The "art" of client side interface will meet the "fandango dance" of = the=20 server-side apps and really enhance the overall forumla for = developing and=20 delivering the web experiences of tomorrow.=20 Ray=20 _______________________________________________=20 Dynapi-Dev mailing list=20 Dyn...@li...=20 http://lists.sourceforge.net/lists/listinfo/dynapi-dev --=20 Michael Pemberton=20 mp...@ph...=20 ICQ: 12107010=20 =20 --- Outgoing mail is certified Virus Free by AVG Free Edition 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: Michael P. <mp...@ph...> - 2001-02-18 23:18:40
|
I haven't got any other browser than 4.75 / Mozilla 0.8 / NS 6 / IE5.5 If anyone out there want's to test it, please do. Doug Melvin wrote: > Very nice!How far back is it compatable?NS 4.whatIE? > > ----- Original Message ----- > From: Michael Pemberton > To: dyn...@li... > Sent: Sunday, February 18, 2001 5:05 AM > Subject: Re: [Dynapi-Dev] Dynamic Loading. > The loadpanel is not the only method of downloading content > from a server. > > I'm in the process of finishing off a method of downloading > content without the need to create a lot of new objects and > it will be more powerful than the loadpanel. > > At the moment, it is still a WIP but is close to > completion. It can be seen in action here. > > You'll see that it executed JS and also extracts the various > parts of the downloaded page. > > The main "bug" at the moment is that the MAC versions of > java do not include the required classes for downloading the > content. there is no easy way of fixing this unless you > write the code to work with the java plugin and force all > your clients to download the java plugin. > > Raymond Smith wrote: > > > While I agree that the WebOS solution is overkill for the > > DynAPI. The > > Loadpanel approach is not the most solid bridge to deliver > > dynamic (dynamic > > being defined as 'dynamic server/client interaction') > > content. I think we > > need to explore alternatives/improvements to the glue > > between the DynAPI and > > the wealth of server-side power that exists out there. > > > > JS is client. It performs best in that world. The > > server-side unlocks a > > whole new world of "dynamics" that currently tend to > > funnel into very "dead" > > client interfaces. That's what peaked my interest in the > > DynAPI in the > > first place. I loath the limited realm that FLASH > > delivers along with its > > pathetic CPU chewing rendering engine. I like the fact > > that the DynAPI > > leaves options 100% open for me to pick and choose > > front-to-back delivery > > platforms. > > > > Currently loadpanel is probably the weakest link > > supporting the DynAPI > > platform. But it is the "only" link we currently have to > > bridge between two > > very different worlds. Fix and optimize it...., > > > > then you will see magic... > > > > The "art" of client side interface will meet the "fandango > > dance" of the > > server-side apps and really enhance the overall forumla > > for developing and > > delivering the web experiences of tomorrow. > > > > Ray > > > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > http://lists.sourceforge.net/lists/listinfo/dynapi-dev > > -- > Michael Pemberton > mp...@ph... > ICQ: 12107010 > > > > --- > Outgoing mail is certified Virus Free by AVG Free Edition > 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 > -- Michael Pemberton mp...@ph... ICQ: 12107010 |
From: Liam C. <met...@ma...> - 2001-02-19 13:40:35
|
I can confirm that this example does not currently work with IE5 Mac. The applet loads but creates this error as both a alert and a IE error panel: Line number: 43 Message: Object doesn=B9t support this property or method I'm not sure about the state of Java on the Mac but the same error occurs i= n IE5 Mac OSX pb, even though that has Java 2. Seems to be M$ method of talking to the Mac Java environment as I have seen this method work as a pure Java application on Mac OS 9 and OS X. NN4.7 Mac does not produce an error - but I am not sure I am getting what you expect. I get 3 alerts: '------Body------'=20 '------Source----' '------Title-----' But no other text or change to the page, is this right? Example s/shot attached of this. Liam --=20 "Everything in moderation ... including moderation" pgp on request |
From: Michael P. <mp...@ph...> - 2001-02-19 13:58:45
|
the problem with NS is a Cross OS problem. It is something i am working on. It seems that NS is too quick (yes I said TOO quick) and returns the content before it has actually downloaded it. Liam Clancy wrote: > I can confirm that this example does not currently work with IE5 Mac. > > The applet loads but creates this error as both a alert and a IE error > panel: > > Line number: 43 > Message: Object doesn¹t support this property or method > > I'm not sure about the state of Java on the Mac but the same error occurs in > IE5 Mac OSX pb, even though that has Java 2. Seems to be M$ method of > talking to the Mac Java environment as I have seen this method work as a > pure Java application on Mac OS 9 and OS X. > > NN4.7 Mac does not produce an error - but I am not sure I am getting what > you expect. > I get 3 alerts: > '------Body------' > '------Source----' > '------Title-----' > > But no other text or change to the page, is this right? > Example s/shot attached of this. > > Liam > > -- > "Everything in moderation ... including moderation" > > pgp on request > > ------------------------------------------------------------------------ > Name: DynLoading-nn47mac.gif > DynLoading-nn47mac.gif Type: GIF Image (image/gif) > Encoding: base64 -- Michael Pemberton mp...@ph... ICQ: 12107010 |
From: Nuno F. <nun...@wi...> - 2001-02-20 11:23:26
|
>I loath the limited realm that FLASH delivers along with its >pathetic CPU chewing rendering engine. I like the fact that the DynAPI >leaves options 100% open for me to pick and choose front-to-back delivery >platforms. I agree, though as it stands, DynAPI chews more CPU time than the average flash movie, let alone IE memory leaks. >Currently loadpanel is probably the weakest link supporting the DynAPI >platform. But it is the "only" link we currently have to bridge between two >very different worlds. Fix and optimize it...., Hmmm, I think that setHTML is the way to go, not loadpanel. Using PHP, for instance, you can load a PHP file in a hidden frame, that accesses a database and builds a script on that hidden page that alters the layer content on the main page via setHTML. In practice, if you organize things thouroughly, you won't have to reload the main page ever. best, NunoF |
From: Michael P. <mp...@ph...> - 2001-02-20 12:54:32
|
this is basically what I have done with my url applet. it loads the raw source and then evaluates what needs to be done. I think it is better than writing a lot of repetative JS in a separate frame. Nuno Ferreira wrote: > >I loath the limited realm that FLASH delivers along with its > >pathetic CPU chewing rendering engine. I like the fact that the DynAPI > >leaves options 100% open for me to pick and choose front-to-back delivery > >platforms. > > I agree, though as it stands, DynAPI chews more CPU time than the average > flash > movie, let alone IE memory leaks. > > >Currently loadpanel is probably the weakest link supporting the DynAPI > >platform. But it is the "only" link we currently have to bridge between > two > >very different worlds. Fix and optimize it...., > > Hmmm, I think that setHTML is the way to go, not loadpanel. > Using PHP, for instance, you can load a PHP file in a hidden frame, that > accesses > a database and builds a script on that hidden page that alters the layer > content > on the main page via setHTML. In practice, if you organize things > thouroughly, you > won't have to reload the main page ever. > > best, > > NunoF > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev -- Michael Pemberton mp...@ph... ICQ: 12107010 |
From: Nuno F. <nun...@wi...> - 2001-02-20 15:29:53
|
How does it run? Do you call it from Javascript? Or it's a normal Java Applet? -----Original Message----- From: dyn...@li... [mailto:dyn...@li...]On Behalf Of Michael Pemberton Sent: terca-feira, 20 de Fevereiro de 2001 12:52 To: dyn...@li... Subject: Re: [Dynapi-Dev] Dynamic Loading. this is basically what I have done with my url applet. it loads the raw source and then evaluates what needs to be done. I think it is better than writing a lot of repetative JS in a separate frame. Nuno Ferreira wrote: > >I loath the limited realm that FLASH delivers along with its > >pathetic CPU chewing rendering engine. I like the fact that the DynAPI > >leaves options 100% open for me to pick and choose front-to-back delivery > >platforms. > > I agree, though as it stands, DynAPI chews more CPU time than the average > flash > movie, let alone IE memory leaks. > > >Currently loadpanel is probably the weakest link supporting the DynAPI > >platform. But it is the "only" link we currently have to bridge between > two > >very different worlds. Fix and optimize it...., > > Hmmm, I think that setHTML is the way to go, not loadpanel. > Using PHP, for instance, you can load a PHP file in a hidden frame, that > accesses > a database and builds a script on that hidden page that alters the layer > content > on the main page via setHTML. In practice, if you organize things > thouroughly, you > won't have to reload the main page ever. > > best, > > NunoF > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev -- Michael Pemberton mp...@ph... ICQ: 12107010 |
From: Michael P. <mp...@ph...> - 2001-02-21 00:26:17
|
it is a 1k applet that can be seen in action here: AfroAPI Examples - File Handling : URL As I've sid previously, there are still a few glitches in NS. IE works fine. It uses and applet to download the content and then uses JS to parse the data and extract the relevant details and evaluate any JS that is contained. If you want, I can send you the WIP code. Nuno Ferreira wrote: > How does it run? > Do you call it from Javascript? Or it's a normal Java Applet? > > -----Original Message----- > From: dyn...@li... > [mailto:dyn...@li...]On Behalf Of Michael > Pemberton > Sent: terca-feira, 20 de Fevereiro de 2001 12:52 > To: dyn...@li... > Subject: Re: [Dynapi-Dev] Dynamic Loading. > > this is basically what I have done with my url applet. it loads the raw > source and > then evaluates what needs to be done. I think it is better than writing a > lot of > repetative JS in a separate frame. > > Nuno Ferreira wrote: > > > >I loath the limited realm that FLASH delivers along with its > > >pathetic CPU chewing rendering engine. I like the fact that the > DynAPI > > >leaves options 100% open for me to pick and choose front-to-back > delivery > > >platforms. > > > > I agree, though as it stands, DynAPI chews more CPU time than the average > > flash > > movie, let alone IE memory leaks. > > > > >Currently loadpanel is probably the weakest link supporting the > DynAPI > > >platform. But it is the "only" link we currently have to bridge > between > > two > > >very different worlds. Fix and optimize it...., > > > > Hmmm, I think that setHTML is the way to go, not loadpanel. > > Using PHP, for instance, you can load a PHP file in a hidden frame, that > > accesses > > a database and builds a script on that hidden page that alters the layer > > content > > on the main page via setHTML. In practice, if you organize things > > thouroughly, you > > won't have to reload the main page ever. > > > > best, > > > > NunoF > > > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > http://lists.sourceforge.net/lists/listinfo/dynapi-dev > > -- > Michael Pemberton > mp...@ph... > ICQ: 12107010 > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev -- Michael Pemberton mp...@ph... ICQ: 12107010 |
From: francesco A. <fa...@we...> - 2001-02-20 12:55:04
|
HI, see this site for alterative loading dynamic data work only for IE5+,NS6,Mozzilla, not IE mac, not NS4 ----- Original Message ----- From: "Nuno Ferreira" <nun...@wi...> To: <dyn...@li...> Sent: Tuesday, February 20, 2001 12:20 PM Subject: RE: [Dynapi-Dev] Dynamic Loading. > > >I loath the limited realm that FLASH delivers along with its > >pathetic CPU chewing rendering engine. I like the fact that the DynAPI > >leaves options 100% open for me to pick and choose front-to-back delivery > >platforms. > > I agree, though as it stands, DynAPI chews more CPU time than the average > flash > movie, let alone IE memory leaks. > > >Currently loadpanel is probably the weakest link supporting the DynAPI > >platform. But it is the "only" link we currently have to bridge between > two > >very different worlds. Fix and optimize it...., > > Hmmm, I think that setHTML is the way to go, not loadpanel. > Using PHP, for instance, you can load a PHP file in a hidden frame, that > accesses > a database and builds a script on that hidden page that alters the layer > content > on the main page via setHTML. In practice, if you organize things > thouroughly, you > won't have to reload the main page ever. > > best, > > NunoF > > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev |
From: Michael P. <mp...@ph...> - 2001-02-20 13:08:02
|
url? francesco AGATI wrote: > see this site for alterative loading dynamic data > work only for IE5+,NS6,Mozzilla, not IE mac, not NS4 -- Michael Pemberton mp...@ph... ICQ: 12107010 |
From: francesco A. <fa...@we...> - 2001-02-20 13:30:06
|
see this site for alterative loading dynamic data work only for IE5+,NS6,Mozzilla, not IE mac, not NS4 http://www.xs4all.nl/~ppk/js/importxml.html ----- Original Message ----- From: "Michael Pemberton" <mp...@ph...> To: <dyn...@li...> Sent: Tuesday, February 20, 2001 2:05 PM Subject: Re: [Dynapi-Dev] Dynamic Loading. > url? > > francesco AGATI wrote: > > > see this site for alterative loading dynamic data > > work only for IE5+,NS6,Mozzilla, not IE mac, not NS4 > > -- > Michael Pemberton > mp...@ph... > ICQ: 12107010 > > > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev |
From: Doug M. <do...@cr...> - 2001-02-20 19:02:15
|
and what site would that be? ----- Original Message ----- From: "francesco AGATI" <fa...@we...> To: <dyn...@li...> Sent: Tuesday, February 20, 2001 4:55 AM Subject: Re: [Dynapi-Dev] Dynamic Loading. > HI, > > see this site for alterative loading dynamic data > > work only for IE5+,NS6,Mozzilla, not IE mac, not NS4 > > ----- Original Message ----- > From: "Nuno Ferreira" <nun...@wi...> > To: <dyn...@li...> > Sent: Tuesday, February 20, 2001 12:20 PM > Subject: RE: [Dynapi-Dev] Dynamic Loading. > > > > > > >I loath the limited realm that FLASH delivers along with its > > >pathetic CPU chewing rendering engine. I like the fact that the DynAPI > > >leaves options 100% open for me to pick and choose front-to-back delivery > > >platforms. > > > > I agree, though as it stands, DynAPI chews more CPU time than the average > > flash > > movie, let alone IE memory leaks. > > > > >Currently loadpanel is probably the weakest link supporting the DynAPI > > >platform. But it is the "only" link we currently have to bridge between > > two > > >very different worlds. Fix and optimize it...., > > > > Hmmm, I think that setHTML is the way to go, not loadpanel. > > Using PHP, for instance, you can load a PHP file in a hidden frame, that > > accesses > > a database and builds a script on that hidden page that alters the layer > > content > > on the main page via setHTML. In practice, if you organize things > > thouroughly, you > > won't have to reload the main page ever. > > > > best, > > > > NunoF > > > > > > > > _______________________________________________ > > 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 > --- 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: Robert R. <rra...@ya...> - 2001-02-18 19:33:21
|
Does anyone have Dan's old servertasks objects (Pascal? Dan?). I think that creating server side components is the only way to create truly cross-browser loading. -- // Robert Rainwater On 2/18/2001, 5:27:54 PM EST, Doug wrote about "[Dynapi-Dev] Dynamic Loading.": > Very nice! > How far back is it compatable? > NS 4.what > IE? > ----- Original Message ----- > From: Michael Pemberton > To: dyn...@li... > Sent: Sunday, February 18, 2001 5:05 AM > Subject: Re: [Dynapi-Dev] Dynamic Loading. > The loadpanel is not the only method of downloading content from a server. > I'm in the process of finishing off a method of downloading content without the need to create a lot of new objects and it will be more powerful than the loadpanel. > At the moment, it is still a WIP but is close to completion. It can be seen in action here. > You'll see that it executed JS and also extracts the various parts of the downloaded page. > The main "bug" at the moment is that the MAC versions of java do not include the required classes for downloading the content. there is no easy way of fixing this unless you write the code to > work with the java plugin and force all your clients to download the java plugin. > Raymond Smith wrote: > While I agree that the WebOS solution is overkill for the DynAPI. The > Loadpanel approach is not the most solid bridge to deliver dynamic (dynamic > being defined as 'dynamic server/client interaction') content. I think we > need to explore alternatives/improvements to the glue between the DynAPI and > the wealth of server-side power that exists out there. > JS is client. It performs best in that world. The server-side unlocks a > whole new world of "dynamics" that currently tend to funnel into very "dead" > client interfaces. That's what peaked my interest in the DynAPI in the > first place. I loath the limited realm that FLASH delivers along with its > pathetic CPU chewing rendering engine. I like the fact that the DynAPI > leaves options 100% open for me to pick and choose front-to-back delivery > platforms. > Currently loadpanel is probably the weakest link supporting the DynAPI > platform. But it is the "only" link we currently have to bridge between two > very different worlds. Fix and optimize it...., > then you will see magic... > The "art" of client side interface will meet the "fandango dance" of the > server-side apps and really enhance the overall forumla for developing and > delivering the web experiences of tomorrow. > Ray > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev > -- > Michael Pemberton > mp...@ph... > ICQ: 12107010 > --- > Outgoing mail is certified Virus Free by AVG Free Edition > 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 Snapshots: http://dynapi.sourceforge.net/snapshot/ DynAPI Homepage: http://dynapi.sourceforge.net/ |