Re: [Dynapi-Dev] External loading trick - advanced -

[Jordi - I. - M. <jmi...@or...>]

I found out that having these document.write happen in one frame while
having something happening in the main frame ( a slide, for example )
turned NS unstable sometimes. So far this is the only issue I found with
the idea. Not a small one :( however

Pascal wrote:

> and it works crossbrowser? (have to ask >:)
>
> Pascal Bestebroer (pb...@oi...)
> Software ontwikkelaar
> Oberon Informatiesystemen b.v.
> http://www.oibv.com
>
> > -----Oorspronkelijk bericht-----
> > Van: dyn...@li...
> > [mailto:dyn...@li...]Namens Jordi -
> > IlMaestro
> > - Ministral
> > Verzonden: maandag 26 februari 2001 14:33
> > Aan: dyn...@li...
> > Onderwerp: [Dynapi-Dev] External loading trick - advanced -
> >
> >
> > Here's something I came up with while working on the project
> > that almost killed
> > me last week. I needed ( or wanted ) to load external
> > contents inside of my
> > layers, but didn't want to use the loadpanel.
> >
> > My personal opinion is that the future of loading external
> > contents does not go
> > through the loadpanel. Not because of the panel itself but
> > because of the very
> > nature of the browsers and all the problems of
> > synchronization that involve.
> > I'd like to use setHTMLs (with or without Java would be
> > another discussion).
> >
> > My main concern was to have an external page that could be browsed as
> > standalone and yet loaded into a dynlayer. Even edited with
> > dreamweaver. Here's
> > the solution. I thought I'd share.
> >
> > <script>
> > if(parent.content.DynAPI)    // Insert your condition here
> > {
> > window.onload = function() {
> >     parent.content.scroll.setHTML(document.form1.txt.value)
> >     }
> > document.write("<form name=form1><textarea name=txt>")
> > }
> > </script>
> >
> >
> > This is the page
> >
> >
> > <script>
> > if(parent.content.DynAPI)    // Insert your condition here
> > {
> > document.write("</textarea></form>")
> > }
> > </script>
> >
> >
> >
> > ----
> >
> > This worked fine. Pages can be seen as stand-alone and can be
> > loaded inside my
> > application. It is a bit dirty but back in the old Dyn1 days
> > we needed to have
> > a parent.scroll.activate() call anyway. If you have links
> > inside you will need
> > the scroll object to parse them and change them to
> > 'javascript:scroll.load(.....)'
> >
> > Hope this helps anyone
> >
> >
> > _______________________________________________
> > 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