> It's nearly a month already I
> haven't given any news.
Not a problem! I'm up to my ears in stuff myself
>> So Christophe(r?), let me put
>> this question to you: Would a
>> solution that only deals with
>> button clicks be acceptable?
> Yes, it would be enough for the
> application I'm working on now
In that case it's probably not all that difficult. I can't remember exactly,
but I think I was thinking of an application that would ask you to identify
which buttons would be clickable and generate a page that would transmit
their coordinates to the server. The rest of the html is basically a picture
sent by the server. I don't know how to overlay buttons on a picture, but
I'm sure it can probably be done.
It's pretty easy to limit access to one person at a time.
>>(Look at my web site and imagine a
>> two-way Snap Remote. Get it?)
> What's your website address?
http://www.oswegosw.com/vrf_archive
Check out Spy On Shawn. You click a window handle and you get a picture of
that window (if it has anything to show anyway). The idea for this VEE thing
is pretty much the same - snap a picture of VEE and send it to the client.
When you click a button on the client, it transmits the coordinates to the
server and the server clicks the button at those coordinates. Not that bad.
It's a simple idea that's suitable for simple scenarios. I.e., the VEE
application is full screen and a single panel, or the VEE screen never moves
and all panels are locked in position.
-SHAWN-
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
> haven't given any news.
Not a problem! I'm up to my ears in stuff myself
>> So Christophe(r?), let me put
>> this question to you: Would a
>> solution that only deals with
>> button clicks be acceptable?
> Yes, it would be enough for the
> application I'm working on now
In that case it's probably not all that difficult. I can't remember exactly,
but I think I was thinking of an application that would ask you to identify
which buttons would be clickable and generate a page that would transmit
their coordinates to the server. The rest of the html is basically a picture
sent by the server. I don't know how to overlay buttons on a picture, but
I'm sure it can probably be done.
It's pretty easy to limit access to one person at a time.
>>(Look at my web site and imagine a
>> two-way Snap Remote. Get it?)
> What's your website address?
http://www.oswegosw.com/vrf_archive
Check out Spy On Shawn. You click a window handle and you get a picture of
that window (if it has anything to show anyway). The idea for this VEE thing
is pretty much the same - snap a picture of VEE and send it to the client.
When you click a button on the client, it transmits the coordinates to the
server and the server clicks the button at those coordinates. Not that bad.
It's a simple idea that's suitable for simple scenarios. I.e., the VEE
application is full screen and a single panel, or the VEE screen never moves
and all panels are locked in position.
-SHAWN-
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
It's nearly a month already I haven't given any news.
I feel very sorry for not even answering a subject I have
initiated...but I had so much work to do from then. Well, after "an
unslept" night, I managed to finish my report and there I am answering
to my 1-month-old e-mails
Thank you all for answering my question, especially you Shawn for
getting so involved!
It's very late, but let me answer to your mail :
> The way I see it, Chris is looking for a simple way to do VEE remote
> control
> with nothing available on the client but a standard w3c Eudora
(ideally) or
> IE4+ (probably more realistically).
Yes indeed.
> So Christophe(r?), let me put this question to you: Would a solution that
> only deals with button clicks be acceptable?
Yes, it would be enough for the application I'm working on now, but I
would like to create some sort of 'reference program' for future
programs that might need a text input or whatever
> There are further caveats though: Imagine you've got 30 or 40 people all
> trying to control your VEE application at the same time. Total chaos.
> Either
> you would have to be willing to limit access to one person at a time
Yes. I think the *one-master* vision is the safest one. However, I want
to let it free.
>(Look at my web site and imagine a
> two-way Snap Remote. Get it?)
What's your website address?
---
The way I see the solution is some kind of mixed Java/html program
interacting with VEE using either text files(!) or DDE (sorry don't even
know what I'm talking about
program from the beginning though and the part would be different for
each program...
Christophe CHEVALLIER.
christophe.chevallier@ensmp.fr
Shawn Fessenden a crit :
>> VEE supports calling remote functions, on another machine.
>> Couldn't this be used, perhaps in combination with the
>> built in web server, to create a remotely controlled
>> system (it would be fairly involved, I'm sure)?
>
>
> Well, if the VEE runtime were installed on the client *and* the application
> was constructed as a client/server *and* the client VXE could be
> downloaded - then yes that probably is the best way to go.
>
> The problem is you're still stuck with client software. VEE in this case.
> And even then, the application has to be client/server in order to work.
>
> The way I see it, Chris is looking for a simple way to do VEE remote
> control
> with nothing available on the client but a standard w3c Eudora (ideally) or
> IE4+ (probably more realistically). There are certain givens:
>
> 1. There will be an active client side that will be
> able to transmit cursor position, clicks & key-
> strokes to the server. Keystrokes are the hard
> part here.
>
> 2. There will be some gateway interface on the
> server that will be able to receive these
> data and interact with VEE appropriately.
>
> 3. Ideally communication should be kept within the
> HTTP standard. If that's not possible (and I
> really don't see how it is):
>
> 4. The client must initiate a connection to the
> gateway or a component after it so that firewalls
> or proxies can be easily traversed.
>
> If it were nothing but buttons, I'd say it would be doable with a
> minimum of
> fuss & muss. But that's not possible. One has to make allowance for input
> fields and that is where all the trouble comes from.
>
> In order to accommodate input fields (or any kind of click & type idea)
> remaining in the HTTP standard becomes impossible without a mapping layer.
> Sure, HTTP can do all kinds of input fields but it has to be told how to do
> so. I think that trying to analyze a VEE program or a picture of a VEE
> display to generate the HTTP would be nearly impossible. The idea is that
> this method does not require any extra effort on the part of the VEE
> programmer at all. You start the server and that's it.
>
> [Later] You know actually I guess maybe it's not that hard after all. The
> information one would need is for any given panel, what's the x, y
> location,
> size and type of any input object. I still wouldn't know how to translate
> that into HTML to overlay on the VEE display picture, but it's a start.
>
> So Christophe(r?), let me put this question to you: Would a solution that
> only deals with button clicks be acceptable? Left button clicks in
> particular. I *do* see a clear path to that solution. Almost any web server
> could do it. At the moment, I don't know how individual authentication
> would
> be handled without generating separate pages (I know how to auth a page,
> but
> multi-auth I don't know how to do). IOW there would be a different page for
> each user you wish to authenticate.
>
> There are further caveats though: Imagine you've got 30 or 40 people all
> trying to control your VEE application at the same time. Total chaos.
> Either
> you would have to be willing to limit access to one person at a time or
> you'd have to be willing to allow the web server to start up multiple
> copies
> of VEE - and that's not such a good idea. It will quickly be swamped.
>
> There are other possible solutions to that dilemma, but they involve
> multiple VEE servers and lots of RPC (Look at my web site and imagine a
> two-way Snap Remote. Get it?). They're also much more involved.
> -SHAWN-
>
>
>
> ---
> You are currently subscribed to vrf as: christophe.chevallier@ensmp.fr
> To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
> To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list, email "vrf@agilent.com". If you
> need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".