Milovana.com

LoRemen wrote: Sat Dec 21, 2019 8:02 pm at least tell me how you're retrieving text and images with only an EOS Tease link to go at.

You can retrieve the EOS script like this:
where xxxxx is the tease ID.

Trusfrated wrote: Tue Dec 24, 2019 4:39 am

LoRemen wrote: Sat Dec 21, 2019 8:02 pm at least tell me how you're retrieving text and images with only an EOS Tease link to go at.

You can retrieve the EOS script like this:

Code: Select all

https://milovana.com/webteases/geteosscript.php?id=xxxxx 

where xxxxx is the tease ID.

Swee-ee-t!

Now my approach is to translate this JSON into HTML and CSS, to store EOS and normal Teases in a common format (for anyone wondering, maybe you have a better idea).

How do you know about geteosscript.php?

LoRemen wrote: Tue Dec 24, 2019 12:43 pm How do you know about geteosscript.php?

I believe GodDragon was the one who pointed it out. You can learn more about what's going on by using the web developer tools in your browser. Do a search here for geteosscript and you'll see there's been some discussions about it.

Any update on the progress?

Trusfrated wrote: Tue Dec 24, 2019 4:39 am

LoRemen wrote: Sat Dec 21, 2019 8:02 pm at least tell me how you're retrieving text and images with only an EOS Tease link to go at.

You can retrieve the EOS script like this:

Code: Select all

https://milovana.com/webteases/geteosscript.php?id=xxxxx 

where xxxxx is the tease ID.

So, that gives a .JSON file, but how do you get the images?

if you remove the "tb_xl" part of the url you reach the original file (at least, that's my guess) and you can also do the same to get other file types (such as audio).

And yes, I'm starting to work on my own version of an offline viewer in Java

I am so sorry guys.
I saw your comments and I want to help you out a bit.
I will share my code which was written in Java. (Java11 + JavaFx and Gradle)

I didn't have any time to finish it, I barely touched the code since october.

But I remember, I got stuck somewhere near the 'eval' function.
I think a full JS interpreter have to be written to match the functionality of EOS.
So I wanted to change my original Java based idea.

To something like this:
make an Apache or NginX server (started by a Java process, if possible)
borrow the full eos player and embed it into this webserver
load only one tease at a time by placing files (downloaded scripts and media) somewhere inside the webserver
enjoy the offline tease sessions

Easy right?

Java11 (jdk11) is required to compile (build) the code.

If you are not familiar with gradle I recommend to use IntelliJ or Eclipse which have a decent support for it.

In IntelliJ:
This JVM options are required to start the application: --add-modules=javafx.controls,javafx.fxml
My run configuration has this main class: none.eosplayer.player.Starter
And for classpath I use eos-player.eosplayer.player.main
It is important to create a simple 'Application' run configuration instead of a Gradle one.

Downloaded teases and files will be stored inside the "workspace" directory.

Oh and the program can download all the media from the server.
I mean it will download everything, not just the used pictures/audios.

The download process is fully working for every tease (I think).

This tease is totally playable: https://milovana.com/webteases/showtease.php?id=41578
And this one is ... not: https://milovana.com/webteases/showtease.php?id=40134

With the second one you can check those functions which are completely non-functioning.

And again, sorry for my late response and everything.

Edit:
I forgot to tell: I use lombok plugin for model annotations like getters, setters, constructors etc.

Thanks for the program, can you please update the first post with the download in this topic. Thanks

Please take a look at gasm/gserver The same approach should also work for a EOS offline player. Handling the eval code and also the initialization code becomes almost trivial (see below).

In particular it should not be very difficult to convert EOS scripts to human readable gasm scripts that can also be modified. A Custom high level RTL that emulates the EOS look and feel or at least a library that implements EOS specific functions is required.

Only issue is the usage of global variables in EOS scripts.

Quick and dirty solution would be to insert the initialization section in global scope and write a wrapper for 'teaseStorage' that stores variables in/from scriptVars -- the tease storage of gasm. This emulates the EOS behavior and handling eval and initialization code becomes trivial.

But it breaks the gasm concept and thus makes it more complicated to modify the output. A better approach would be to parse the init section and store these variables in the scriptVars object. That makes 'teaseStorage' obsolete and allows re-entering teases. But that also requires that variable names in eval code snippets are replaced.

Sadly I can't contribute in any way, you smart people just know that your work is appreciated and I'm looking forward to it.