Yes. There is a post that explains all about accessing another document outside of another. Every document comes with a global variable that can be accessed outside of it. For example, if my document is called "test" and I exported it. I would be able to access it by using
This way the Hype document will check for a hash and then go to the scene with the value after it. In this case “myscene”.
The info is in the link above on how to implement this.
I know @MarkHunte came up with a way to go to different parts / serve the document in different languages using a .htaccess file. That could also work perhaps in this case, maybe. Not 100% sure on that one. Perhaps Mark has some info on whether that would work. If so, it could be added to the linked post?
@DBear, I think they are trying to use the smartphone page as a remote to control the page on a desktop.
Also since they talk about same network I suspect they are not talking about a server.
On the desktop version you can move using the keyboard keys, but the smartphone html should be able to trigger specific scenes locations (hypeDocument.showSceneNamed)
This MAY not answer your question, but heres goes nothing:
The computer so far lacks wifi hardware, but its accesible via ethernet from any wifi device since its connected directly to the router, both devices, the smartphone and the computer are connected to the same network and each other can be accessed.
As I mentioned … the hash example is the way to go. I just mentioned Mark as he did something in the past using a .htaccess file. Couldn’t remember why you used it, Mark. Just thought it might be something here. I understand what Davirus [he] is trying to do and of course the hash technique is probably the way to go.
I’m assuming it’s a setup on the same network as he mentions local above. A .htaccess file would work but I wasn’t sure what you were doing with it before i think it was serving a specific doc based on language? something like that.
Just to re-iterate @Davirus … use the hash technique in the link above.
[waves his hands] “These are not the droids you’re looking for!”
That’s probably a better way if you’re running it on the “controlled” machine. Then you can use “sockets” to converse with the server to make changes. It’s gonna be a bit of a beast.
Another possible way is to use a “synchronised” database of sorts that updates in realtime and then you’re “slave” machine can then listen for changes and based on any change it can react accordingly.
Think of it this way:
Cloud (Firebase or something) receives message and stores it. Updates in realtime.
/ \
/ \
Desktop Phone (sends message)
(listening for change)
updates when change made
did not try it, but as you don’t need bidirectional functions this seems to enable easy setup …
ok, i did a short read up
possible workflow:
1.) in the pointer.html create a function that writes some data (say scenename) to a file
2.) the php should read the provided info and echo -> flush()
2.) in the client.html setup the EventSource and onmessage react …