clarification requested: apparent termination of xrx project due to deletion of lbx from xorg

[Luke Kenneth Casson Leighton]

On Tue, Mar 17, 2009 at 4:02 PM,  <david.hagood at gmail.com> wrote:
>> On Tue, Mar 17, 2009 at 1:20 PM, Jim Gettys <jg at freedesktop.org> wrote:
>>
>> it's the npapi plugin capability that i want - the ability to plug in
>> an arbitrary XWindows application into a web browser - not the X
>> compression.  it looks like LBX was utilised in rxr because it was not
>> just a channel for x-window events but also for x-window
>> authentication.
>
> It sounds like what you want is WeirdX - http://www.jcraft.com/weirdx/ -
> which is a Java based X server that will run in a browser under any
> platform supporting Java - including Microsoft Windows.
>
> This will do what you want: allow an X Windowing System client application
> to use a browser as an X Windowing System server.

 david thanks for mentioning this - but no - that's not what i want.

 i don't want to host an entire x server running under an
NPAPI-compliant java plugin, just so as to be able to run one local
application.

 i really _really_ want to fire up _specific_ locally-hosted
applications, to run locally, as controlled by and specified by some
javascript application running in web browser, to run _in_ the
existing x server.

order of events:

1) user fires up X-windows, and runs _one_ application: a web browser.
 full screen.  no menus.  nothing but total exclusive domination of
the screen.  no window manager.  nothing.

2) web browser runs _one_ web page - a window manager, written in javascript.

3) window manager, written in javascript, gets a "click" on an "icon"
which says "run xclock".

4) javascript code dynamically creates a node (something like this)
    < embed type="x-application/embedded-xapp"
                   params="/usr/bin/xclock" width="100" height="100" />

   and adds that node to the browser DOM model (location is chosen by
the javascript-implemented window manager)

5) NPAPI-compliant plugin (it can't be rxr because that's borked)
fires up xclock as the sole, exclusive, _only_ application to run
*inside* the web browser.

if i used x-weird, step 5) would be replaced by something very very
strange, and i'm not actually sure it would be technically possible to
communicate with the java-hosted web server in order to get it to run
one single app, as "demanded" by the javascript application...

although... that having been said, although i'm not (at this time) in
the slightest bit interested in non-x-server-based operating systems,
the possibility of cooperating with a target (unix) system to fire up
the one single app inside the dedicated java-based x-windows server...

l.