MVDL - EOS Tease Downloader

[atemplic]

Given that our fearless leader seems to be MIA, I got a little worried about this site disappearing. I've got a lot of the good flash teases downloaded but I didn't see anything for EOS teases. So I made one!

MVDL works on mac/windows/linux - just download the right file from the releases page. All it does is download the script and related files though. It'd be a lot more work to either hack together the web player into work offline or write one from scratch. The idea is I could always do that work later, but I couldn't replace the content if it disappears.

There's some caveats in the project's README but everything should be pretty straightforward. In the interest of not taking down this site accidentally, I've limited it to download one file per second maximum.

[vanCoochee]

I once wrote a small script for that express purpose;
but during testing realized the real problem would be a player (which i wanted to implement in HTML+CSS but dropped it thinking it was not worth the effort (i mean how many times do you play the same tease (and you would need to have played it before downloading to know it's even worth archiving...))(and there are A LOT of EOS features to implement )).

So ...
Nice to see someone trudging through the same waters

Source Code

Spoiler: show

Looking over your source (and this is completely non-personal; maybe you can sympathize ) , it's like a lot of projects these days:
A LOT

Jim Carrey in "Dumb and Dumber": "a lot"

1.jpg (28.01 KiB) Viewed 5231 times

of tiny files with
A LOT

Jim Carrey in "Dumb and Dumber": "a lot"

1.jpg (28.01 KiB) Viewed 5231 times

of library references and mainly just declarations

Where's the actual work being done?:
Eventually i got to /src/app/home/home.component.ts: loadTease() calls parseTeaseId() and passes its result to ipcRenderer (so something is being done, but now i have to backtrace ipcRenderer (and i bet even that's not the actual HTTP call ))

If the management (libraries and frameworks and config) are clogging your actual intent in the code ...
... it's no fun for the developer nor maintainer
... and the project will never be fully understood from anyone but you and soon started from scratch

[atemplic]

Source Code

Spoiler: show

Looking over your source (and this is completely non-personal; maybe you can sympathize ) , it's like a lot of projects these days:
A LOT1.jpg
of tiny files with
A LOT1.jpg
of library references and mainly just declarations

Where's the actual work being done?:
Eventually i got to /src/app/home/home.component.ts: loadTease() calls parseTeaseId() and passes its result to ipcRenderer (so something is being done, but now i have to backtrace ipcRenderer (and i bet even that's not the actual HTTP call ))

If the management (libraries and frameworks and config) are clogging your actual intent in the code ...
... it's no fun for the developer nor maintainer
... and the project will never be fully understood from anyone but you and soon started from scratch

That's a perennial problem in software dev. There's a lot of little things a desktop app should do and you can either work from scratch and discover them one by one or you can spend time setting up a huge framework and get everything for free. Whichever you choose, the grass is always greener. I've done both before - this time I used the project as an excuse to try out Electron. I get one command to build decent-looking cross-platform binaries that use native file pickers and other niceties like that. But the binaries are enormous and there's a lot of boilerplate configuration. Can't win em all.

It's not like I set everything up myself, the angular-electron project lays out a "minimal" (heavy on the sarcasm quotes, :P) framework to copy. There's really two codebases, an angular web app for the interface and the electron desktop part that hosts it and has the actual logic. Most of the cruft is from angular (everything in src/). I probably would have picked something else there but angular is what I already know. The *.ts files in the root are the electron part - main.ts sets stuff up and tease.ts has the downloading.

It could certainly be organized and documented better, but I have an actual job for doing that. And honestly...I had a lot of fun working on this! Which is good because as you said it's a little useless on its own. I spent most of the time working on the actually important parts. The js/node community gets some well-deserved shit for having a million pointless libraries and my do they like reinventing module systems every year but once everything was going this was one of the nicest dev environments I've ever used.

[Electro]

.... All it does is download the script and related files though. It'd be a lot more work to either hack together the web player into work offline or write one from scratch. The idea is I could always do that work later, but I couldn't replace the content if it disappears.

If it's based on java, perhaps it can run on gasm/gserver? There have been a few EOS teases ported to GuideMe and this tool can play teases that GuideMe can as long as the volume control component isn't implemented(or is removed from the code). Not sure if it covers the bases but here's the thread.
viewtopic.php?f=26&t=22725

[vanCoochee]

There's really two codebases [...] tease.ts has the downloading.

Ah ok, so tease.ts was what i was looking for, found it!!!

So i ran the AppImage on my arch, which successfully downloaded a fairly simple tease, Easy But Difficult 6 - Confusion.
Slowly working on a simple static HTML generator now...

[atemplic]

If it's based on java, perhaps it can run on gasm/gserver? There have been a few EOS teases ported to GuideMe and this tool can play teases that GuideMe can as long as the volume control component isn't implemented(or is removed from the code). Not sure if it covers the bases but here's the thread.
viewtopic.php?f=26&t=22725

I don't really see much that could be shared tbh. It'd be possible to write a converter to their format, but that'd be fraught with incompatibility because EOS allows for arbitrary javascript afaict. Also not sure if this was confusing you, but java and javascript are entirely different. One of my favorite programming jokes: java is to javascript as car is to carpet.

Ah ok, so tease.ts was what i was looking for, found it!!!

So i ran the AppImage on my arch, which successfully downloaded a fairly simple tease, Easy But Difficult 6 - Confusion.
Slowly working on a simple static HTML generator now...

Good to know that the AppImage worked. I hadn't heard of it before but it was the default and seemed reasonable. Godspeed...

[Electro]

ok, not sure if it was Java or JavaScript, probably JavaScript actually

[mantrid]

gasm and gserver are written in Java.

gasm (=guide assembler) translates guides/teases/... defined by a simple script language into JavaScript which runs in web browser.

gserver is just a web server with some extra functionality like internal gasm and estim sound generation.

There is a third component, the RTL (=run time library) which defines the JavaScript engine.

There is documentation (e.g. there and there) including a complex example and a documentation of internals which is mostly intended for developers.

In order to re-use the JavaScript engine you can either write a converter to the script language of gasm (also supports inline Javascript) or you replace the gasm front end by your own one. The first option would also allow to edit converted teases.