Support for Lutris's scripts about scripts HOT 19 OPEN

I'm not sure if this is possible. I would assume that it's probably easier to simply write a Phoenicis script manually.

from scripts.

It should be possible if we make parser for it. I mean we should "unite" these app scripts for Linux (like Lutris), it would be great, if there was client which can work with many scripts / engines.

from scripts.

Ok, but still I doubt that it will work 100% automatically. So maybe it would be better to have a simple converter. Then you could fix possible issues manually after the conversion.

from scripts.

@plata I think the two ways can be done at the same time.
First we create an abstract script that can import any yaml file and that can be extended.
Then, if we have good result, we try to create a repository implementation

from scripts.

Afaik there are like 5 scripts that would be worth migrading on phoenicis and i'm currently working on two of those (Overwatch, League Of Legends)

Based on my experience the rest is semi~non-functonal..

Aldo i would like to see emulator support on phoenics 🤔

but i think that support for bash, json (YAML) installers might prove beneficial too

from scripts.

@qparis just to get you right: You're idea is to implement this in Javascript? So derive InstallerScript? I think that could work. We would probably need a generic YAML parser Bean.

from scripts.

Yes this is the idea.
I think Jackson could do that

from scripts.

Would you want to have a LutrisDTO or use the map directly?

from scripts.

As long as we just want to access the file in JS, a Map should be sufficient

from scripts.

Can you describe the steps which would be required to do this in a way that someone who doesn't know Phoenicis in detail could implement it?

from scripts.

Maybe you can also improve the scripting tutorial, with explanations like : "in Lutris script, it is that".

Also, a link for the documentation inside the main github bar would be is easier to find (instead of scrolling inside the readme).

from scripts.

Can you describe the steps which would be required to do this in a way that someone who doesn't know Phoenicis in detail could implement it?

1. [Phoenicis] Create a bean "Yaml parser" (maybe inside phoenicis-tools) with two publics methods:
- String serialize(Map objectToSerialize)
- Map unserialize(String yamlString)
- See https://github.com/FasterXML/jackson-dataformats-text

At this point, scripts can parse any YAML file to do whatever they want with it

In fact this step is not needed

3. [Scripts] Create a "Lutris Windows Script" Script. The template of "GoG Script" can be copied and pasted, because it is basically the same. Try to implement it from examples. Should not be too hard

• Two way of running a script:
  • From a raw yaml string
  • From a URL

At this point, scripts can quickly run YAML formated scripts.

4. [Phoenicis] [Optional, but would demonstrate the power of phoenicis architecture] Create a Repository Implementation that automatically sends yaml to this script.

from scripts.

@qparis I don't think step 3 will work.
When looking at the lutris scripts, they seem to be quite different compared to our scripts.

Basically we would require a converter, which converts a lutris script into a Phoenicis script.
If during this process something can't be converted, the resulting Phoenicis script is likely not usable.

To write such a converter the implementer requires very deep knowledge of both the Phoenicis scripts and the lutris scripts.

from scripts.

I think this would work for most of them. Any unsupported "verbs" will throw an exception and this can be improved later

from scripts.

For example, you can start with winesteam runner

from scripts.

A point we need to think about: what do we do about the Wine version? In general, the Lutris Wine version is not available (unless we include the Lutris Wine builds by default - which would work).

from scripts.

It depends. If we have similar build, better using it.
If we don't have similar build, the question is: do we need similar build? If so, we modify winebuild. If not, we provide an alternative and suitable build

from scripts.

How can you find out if we have a similar build automatically?

from scripts.

They have very few number of builds and they sems to be managed “by hand”. So I guess we jut have to map them. We can create some distributions if that helps

from scripts.