dynapi-dev

RE: Re[2]: [Dynapi-Dev] Dynamic Loading.

[Matthew A. S. <ms...@sh...>]

Are you talking about a serverside Java component?  I think one of the
main problems is the Macintosh client side java support.  JS has no way
to talk to a Java Applet on the Mac IEs.  I'll have to take a look at my
Remote Scripting stuff but I am pretty sure that's the conclusion that I
came to.

M.

-----Original Message-----
From: Robert Rainwater [mailto:rra...@ya...]
Sent: Sunday, February 18, 2001 11:35 AM
To: DynAPI Development List
Subject: Re[2]: [Dynapi-Dev] Dynamic Loading.



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.

--=20
// 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 -----=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



----------------------
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

Re[4]: [Dynapi-Dev] Dynamic Loading.

[Robert R. <rra...@ya...>]

You can do it in any language (JSP, asp, php, etc).  I think if we set
up a standard way of creating the server-side components, they can be
ported from language to language.  Then each component would have the
same functionality no matter what server-side language you use.

-- 
// Robert Rainwater

On 2/18/2001, 2:38:04 PM EST, Matthew wrote about "[Dynapi-Dev] Dynamic Loading.":

> Are you talking about a serverside Java component?  I think one of the
> main problems is the Macintosh client side java support.  JS has no way
> to talk to a Java Applet on the Mac IEs.  I'll have to take a look at my
> Remote Scripting stuff but I am pretty sure that's the conclusion that I
> came to.

> M.

> -----Original Message-----
> From: Robert Rainwater [mailto:rra...@ya...]
> Sent: Sunday, February 18, 2001 11:35 AM
> To: DynAPI Development List
> Subject: Re[2]: [Dynapi-Dev] Dynamic Loading.



> 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.



----------------------
DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/
DynAPI Homepage: http://dynapi.sourceforge.net/

Re: Re[4]: [Dynapi-Dev] Dynamic Loading.

[Raymond S. <dst...@or...>]

JSP is slow, ASP has a stench I don't like (not sure what causes it, scares
the .net right out of me).

PHP is fast and the launguage is pretty easy to get up to speed on.
Additionally, it's pretty easy for developers to install it if required.
Also there are alot of nice Open Source PHP apps on Source Forge that would
be nice back-end testbeds.  Maybe we should do prototype modeling in PHP to
start with?

WebOS is using XML for legacy support and multiple platforms integration
reasons and would be overkill for the base DynAPI.  If somebody needs it
they can build it in themselves.

----- Original Message -----
From: "Robert Rainwater" <rra...@ya...>
To: "DynAPI Development List" <dyn...@li...>
Sent: Sunday, February 18, 2001 12:49 PM
Subject: Re[4]: [Dynapi-Dev] Dynamic Loading.


>
> You can do it in any language (JSP, asp, php, etc).  I think if we set
> up a standard way of creating the server-side components, they can be
> ported from language to language.  Then each component would have the
> same functionality no matter what server-side language you use.
>
> --
> // Robert Rainwater
>
> On 2/18/2001, 2:38:04 PM EST, Matthew wrote about "[Dynapi-Dev] Dynamic
Loading.":
>
> > Are you talking about a serverside Java component?  I think one of the
> > main problems is the Macintosh client side java support.  JS has no way
> > to talk to a Java Applet on the Mac IEs.  I'll have to take a look at my
> > Remote Scripting stuff but I am pretty sure that's the conclusion that I
> > came to.
>
> > M.
>
> > -----Original Message-----
> > From: Robert Rainwater [mailto:rra...@ya...]
> > Sent: Sunday, February 18, 2001 11:35 AM
> > To: DynAPI Development List
> > Subject: Re[2]: [Dynapi-Dev] Dynamic Loading.
>
>
>
> > 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.
>
>
>
> ----------------------
> 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
>

Re: [Dynapi-Dev] Dynamic Loading.

[Dan S. <dy...@fu...>]

Somewhere along the line someone got confused.  In respect to WebOS we're doing dynamic loading of the libraries with layer-sourcing for Netscape, and Iframe/content downloading for IE4 and 5 respectively.  Library loading differs from server-side communication.  For that we're using static frames and IFrames for Netscape/IE respectively.  Not that it couldn't be done with a Java applet though, that's also a perfectly valid way to do the communication bridge also.

My ServerTask was very simple really, I think the version supplied by Pascal was the latest version that I was working with.  However I was having some browser crashes in Netscape when using it.  I couldn't figure out why it was happening at the time, but it may be more stable with the latest DynAPI.

Dan


On Sun, Feb 18, 2001 at 03:49:59PM -0500, Robert Rainwater wrote:
> 
> You can do it in any language (JSP, asp, php, etc).  I think if we set
> up a standard way of creating the server-side components, they can be
> ported from language to language.  Then each component would have the
> same functionality no matter what server-side language you use.
> 
> -- 
> // Robert Rainwater
> 
> On 2/18/2001, 2:38:04 PM EST, Matthew wrote about "[Dynapi-Dev] Dynamic Loading.":
> 
> > Are you talking about a serverside Java component?  I think one of the
> > main problems is the Macintosh client side java support.  JS has no way
> > to talk to a Java Applet on the Mac IEs.  I'll have to take a look at my
> > Remote Scripting stuff but I am pretty sure that's the conclusion that I
> > came to.
> 
> > M.
> 
> > -----Original Message-----
> > From: Robert Rainwater [mailto:rra...@ya...]
> > Sent: Sunday, February 18, 2001 11:35 AM
> > To: DynAPI Development List
> > Subject: Re[2]: [Dynapi-Dev] Dynamic Loading.
> 
> 
> 
> > 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.
> 
> 
> 
> ----------------------
> 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

Re: [Dynapi-Dev] Dynamic Loading.

[Michael P. <mp...@ph...>]

I already have dymanic library loading working in IE and am in the process of working out the bugs with the NS code.

It can be seen in action here .

It loads the core code required to use the api and then loads the library that extends the internal String object.
The fiorst alert is the code as it was downloads and the second is the newly created method of the string object created by executing the downloaded code.

All of the code execution is handled automatically by the URL IO handler.

Dan Steinman wrote:

> Somewhere along the line someone got confused.  In respect to WebOS we're doing dynamic loading of the libraries with layer-sourcing for Netscape, and Iframe/content downloading for IE4 and 5 respectively.  Library loading differs from server-side communication.  For that we're using static frames and IFrames for Netscape/IE respectively.  Not that it couldn't be done with a Java applet though, that's also a perfectly valid way to do the communication bridge also.
>
> My ServerTask was very simple really, I think the version supplied by Pascal was the latest version that I was working with.  However I was having some browser crashes in Netscape when using it.  I couldn't figure out why it was happening at the time, but it may be more stable with the latest DynAPI.
>
> Dan
>
> On Sun, Feb 18, 2001 at 03:49:59PM -0500, Robert Rainwater wrote:
> >
> > You can do it in any language (JSP, asp, php, etc).  I think if we set
> > up a standard way of creating the server-side components, they can be
> > ported from language to language.  Then each component would have the
> > same functionality no matter what server-side language you use.
> >
> > --
> > // Robert Rainwater
> >
> > On 2/18/2001, 2:38:04 PM EST, Matthew wrote about "[Dynapi-Dev] Dynamic Loading.":
> >
> > > Are you talking about a serverside Java component?  I think one of the
> > > main problems is the Macintosh client side java support.  JS has no way
> > > to talk to a Java Applet on the Mac IEs.  I'll have to take a look at my
> > > Remote Scripting stuff but I am pretty sure that's the conclusion that I
> > > came to.
> >
> > > M.
> >
> > > -----Original Message-----
> > > From: Robert Rainwater [mailto:rra...@ya...]
> > > Sent: Sunday, February 18, 2001 11:35 AM
> > > To: DynAPI Development List
> > > Subject: Re[2]: [Dynapi-Dev] Dynamic Loading.
> >
> >
> >
> > > 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.
> >
> >
> >
> > ----------------------
> > 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

--
Michael Pemberton
mp...@ph...
ICQ: 12107010