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: [EMAIL PROTECTED]
> 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
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> --
> Michael Pemberton
> [EMAIL PROTECTED]
> 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/
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
