[REBOL] Re: REBOL Web Browser Plugin (Alpha) - Volker's suggestion
From: arolls::bigpond::net::au at: 9-Jun-2001 15:06
See notes below.
> On Fri, 8 Jun 2001 [sterling--rebol--com] wrote:
>
> > You go to:
> > somesite.com/files/index.html
> > it has a list of REBOL files you can run.
> > You click on one which causes the browser to move forward to that page
> > and launch REBOL on the file. Now you have to hit the back button to
> > get back to where you were in order to click another file.
>
> Yes, this is how it's supposed to work.
>
> > But if REBOL browses another page, or even the same page as before (if
> > we can get that information), then you do end up at the same page but
> > with one difference... if you hit back, you're back o nthe script page
> > and it launches again. You history would look like this:
> > 0. somesite.com/files/index.html (current page)
> > 1. somesite.com/files/script.r
> > 2. somesite.com/files/index.html
> > 3. somesite.com/index.html
> >
> > So it's not quite right. Thew back button gets you into really big
> > trouble. The current NS plugin kind of does this but it prints out a
> > page with Javascript that sends the browser back two pages so you end
> > up on the _actual_ page that you came from. We can't yet get this to
> > work with IE as it does not support the call to the browser to print
> > stuff out to a new page.
>
> I dont grasp any of this.. You go to a page A that has a link to a rebol
> script B, you click the script B and the browser uses the plugin
> to display
> the running view application inside the browser. You hit back and you're
> back to page A. What's problem? Are you confusing "back" with "up"?
Sterling is not confused.
Volker suggested using browse/only, which creates a
duplicate entry in the history as outlined above.
Your statement above should be amended to:
You go to page A that has a link to a rebol script B,
you click the script B and the browser uses the plugin
to display the running view application **inside
rebol/view**, and because of limitations in the plugin
api, also forces the browser to show another page
(blank in this case).
If, when started by the plugin, rebol/view uses
browse/only to go back to the original page,
THEN there are two instances of the same page
in the history.
Which is a problem.
Anton.
> Anyone tried with Opera btw? It supports netscape plugins so there should
> be no problem.
>
> Sidenote... how the heck to I get passed the "Failed to create binary file
> /home/kolla/.rebol/rebol" problem when running view for the fist time?
> I find myself unable to install rebol/view on linux these days..
> someone fix
> it please.
>
> Also, the amiga installation is kida lame, it assumes all files
> are located
> in RAM: when installing, what smart idea is that? Please, be smart and use
> PROGDIR:!
>
> -- kolla
You sound a bit annoyed. Why don't you document the
above problems and submit to feedback?
Regards,
Anton.
