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 |