Forums

There have been no news for quite a time now. Is there any development going on (especially POL 5)? If not, is it neccessary to transfer responsibility to someone else/the community?

Hi,

I'm still trying to devote some time to enhance the program as I can. However, I don't have a lot of time and contributions are very welcome, as usual :-)

Regards,

Hi Quentin,

I was reading the news on winehq about WineConf. They say that they would appreciate more contact with PoL (developers). I personally believe that it might make sense to streamline PoL and Wine a bit more. Future developments (e.g. Android) might impact PoL as well (with PoL 5 on Java this could work quite nicely). Maybe we could bring the communities together and gain some synergy effects. For example, I'm currently posting how-to's on winehq and playonlinux.com in parallel.

As for contributions: I have tried to build PoL 5 on Kubuntu 16.04 and couldn't get it to compile.

Am I right in assuming that development efforts should go into PoL 5 and that PoL 5 should be the next and maintained PoL release?

I would appreciate if you could describe a roadmap of what needs to be done for PoL 5 and provide build/installation instructions at least for the most common distributions (Ubuntu 16.04, openSuse 42) on GitHub. It will then be much easier to break this into small work packages which can be easily distributed.

How do you plan to handle pull requests in the future? Do we have enough people who are allowed to pull?

Moreover, I suggest to move the PoL scripts to GitHub as well. This will make reviews and maintainance a lot easier.

Best regards

Plata

Edité par plata

I was reading the news on winehq about WineConf. They say that they would appreciate more contact with PoL (developers). I personally believe that it might make sense to streamline PoL and Wine a bit more. Future developments (e.g. Android) might impact PoL as well (with PoL 5 on Java this could work quite nicely). Maybe we could bring the communities together and gain some synergy effects. For example, I'm currently posting how-to's on winehq and playonlinux.com in parallel.

Hi ! I really think so. To be honest, POL 5 was a proof of concept. The result is unfinished but I think it looks quite good. However, I would make few different choices now that I've had time to take hindsight about it :

• Use more native and android compatible scripting engines
• Give up legacy script support and start rewriting them

As for contributions: I have tried to build PoL 5 on Kubuntu 16.04 and couldn't get it to compile.

Am I right in assuming that development efforts should go into PoL 5 and that PoL 5 should be the next and maintained PoL release?

Yes you are right, but part of the work should be simplified and rewritten.

I would appreciate if you could describe a roadmap of what needs to be done for PoL 5 and provide build/installation instructions at least for the most common distributions (Ubuntu 16.04, openSuse 42) on GitHub. It will then be much easier to break this into small work packages which can be easily distributed.

First, we should simplify compilation process and ensure that it is easy to run. Then, we need to write some samples scripts. The shortcut support is also very limited and need to be developed.

How do you plan to handle pull requests in the future? Do we have enough people who are allowed to pull?

Pull request are handled, jenkins and sonar are installed (Some configuration might need to be reworked though).

Moreover, I suggest to move the PoL scripts to GitHub as well. This will make reviews and maintainance a lot easier.

Good idea, definitly.

Best regards

Plata

 

Quote from plata

I created two wiki pages on GitHub for the roadmap and building (I hope that's ok).

Would be great if you could fill the description how to build on Ubuntu 16.04. I don't know enough about maven to get this working.

About keeping the scripts in GitHub: As they do not directly belong to the code, I propose to create a separate repository for them. It should contain one directoy for each application. The directory would then contain the scripts (old and new), required images and a readme if necessary.

The general approach shall be that there is only one directory per application. If a game X can be installed via UPlay and via Steam, the directory shall be named X and the script shall handle both installation ways. This will help to avoid maintaining multiple scripts per application.

Could you create this repository if you agree with the proposal?

Could you create this repository if you agree with the proposal?

Quote from plata

Also, puting scripts on a git repository as some problem regarding the gpg signature system...

In my opinion it would be sufficient to use GitHub to replace the proposals/maintainance on playonlinux.com. The scripts should then be bundled to an rpm/deb and provided in the same place as PoL itself. That part could be done e.g. by Jenkins.

Edité par plata

 

In my opinion it would be sufficient to use GitHub to replace the proposals/maintainance on playonlinux.com. The scripts should then be bundled to an rpm/deb and provided in the same place as PoL itself. That part could be done e.g. by Jenkins.

 

Quote from plata

I see. In this case, Jenkins could take the scripts from GitHub, update the gpg and upload it on the server. As long as we can assume that only reliable people are allowed to pull and GitHub itself is not corrupted, this should be ok.

How do I apply to be able to submit POL profile scripts? I've been sitting on my hands for a while since I thought you disappeared!

Please advise :)

What is POL profile scripts?

Regarding the github repository, please checkout this: https://github.com/PlayOnLinux/scripts.

I will commit a compatible client very soon. Stay tuned

Uh, the scripts in the "Supported Software" section. I want to submit better/new game setup scripts to the library.

Regarding the github repository, please checkout this: https://github.com/PlayOnLinux/scripts.

I will commit a compatible client very soon. Stay tuned

 

Quote from Tinou

Great! Could you add a short description how to add a script to the README (which files to place in which folders etc.)? I will then create pull request for the scripts I have created.

Edité par plata

I will yes

 

Uh, the scripts in the "Supported Software" section. I want to submit better/new game setup scripts to the library.

 

Quote from BloodyIron

lol I'm silly! I just now noticed the "add a program" button, I thought I had to get approved to submit! ;P sorry about that

 

Uh, the scripts in the "Supported Software" section. I want to submit better/new game setup scripts to the library.

 

Quote from BloodyIron

Just use the "Supported software" section

 

Quote from Tinou

 

lol I'm silly! I just now noticed the "add a program" button, I thought I had to get approved to submit! ;P sorry about that

 

 

Uh, the scripts in the "Supported Software" section. I want to submit better/new game setup scripts to the library.

 

Quote from BloodyIron

Just use the "Supported software" section

 

Quote from Tinou

 

Quote from BloodyIron

How about calling PoL 5 "Phoenicis"? We have Play on Linux, Play on Mac, in the future maybe Play on Android, Play on Windows... In the end, it's all the same software and now would be a good chance for a change like this.

Yeah, I agree with this idea but the transition needs to be smooth :-)