Development of module-script generator for lr-mess, lr-mame and mame standalone

valerino

@folly i'm looking just now in the retropie sources if there's some readymade api to make something like a menu with sort-of-checkboxes (i would need it also for my hdmi/crt thing). that would be the ideal solution for your script too. anyway, if it's not there, we can make it.

about mame/mess.... afaik mess is discontinued and all is merged into mame (beware, i refer to mame/mess, without considering the retroarch core). so if mess have it, mame should too in the first place. maybe im wrong ?

v.

Folly

@valerino said in Development of module-script generator for lr-mess and mame standalone:

@folly i'm looking just now in the retropie sources if there's some readymade api to make something like a menu with sort-of-checkboxes (i would need it also for my hdmi/crt thing). that would be the ideal solution for your script too. anyway, if it's not there, we can make it.

Nice, keep me posted.

about mame/mess.... afaik mess is discontinued and all is merged into mame (beware, i refer to mame/mess, without considering the retroarch core). so if mess have it, mame should too in the first place. maybe im wrong ?

I know it can be confusing, but I think it is still :

standalone mame does both arcade/console and regular
arcade/console and regular are splitted into lr-mame and lr-mess

We can do a test.
If lr-mame will do what lr-mess does, then we can drop lr-mess.
Edit :
How do we load, for example, a -cartfor Atari Jaguar with lr-mame, if we want to test ?

valerino

@folly never used mame/lr-mame for anything else than arcades, sincerely (since the non-arcade drivers are not comparable to standalone dedicated emulator or lr-cores). anyway, since mame and mess should be essentially the same thing, nothing should change in the command line interface, should be exactly the same.

Folly

@valerino

Ok, I did the test.
Normally I use your run_mess.sh script for running lr-mess and I have a cmd line that runs directly for, for example handhelds.

So I installed lr-mame from the exp packages.
Renamed it like lr-mess and placed it in that directory.
Tried it just like lr-mess but that didn't work.
Also tried with one of the handhelds directly, it said it can't find the driver.

So I presume lr-mame has only arcade drivers.

valerino

@folly so you're right. weird. but i'm pretty sure for the standalone version is like i said, only mame is mantained.

George Spiggott

It would be a boon to Jaguar gamers to only have to install lr-mame to act as an additional emulator choice and also to use the same core for arcade.

Folly

@valerino

Sure you are correct about that.

Edit:
I Looked it up in the scripts :
The main branch in github is : https://github.com/mamedev/mame .
Above branch is forked in the libretro github : https://github.com/libretro/mame
Both branches are mainained.

lr-mame and lr-mess maintained in the libretro/mame source and mame from the mamedev source.

So these three are maintained

standalone mame ( containing basically mame / mess , compiled from mamedev)
lr-mame ( containing basically mame(arcade) , compiled from libretro/mame)
lr-mess ( containing basically mess(non-arcade) , compiled from libretro/mame)

Folly

@george-spiggott said in Development of module-script generator for lr-mess and mame standalone:

It would be a boon to Jaguar gamers to only have to install lr-mame to act as an additional emulator choice and also to use the same core for arcade.

Yes, it would be.
But I think there is a reason that these packages are still splitted.

DTEAM

@folly said in Development of module-script generator for lr-mess and mame standalone:

I know it can be confusing, but I think it is still :

standalone mame does both arcade/console and regular
arcade/console and regular are splitted into lr-mame and lr-mess

Exactly what It is. MAME standalone is the most « up to date » one.... suppose to be ...

We should keep both. Separately or not in the official Retropie package menu?.. I don’t know. If you do It separately, the user could install only one of those 2 emulators. It could be interesting.

valerino

ok, the menu thing can be implemented using the dialog api (its builtin in the shell, used throughout retropie menu but not with the checkboxes afaik).

dialog --title "title" \
--checklist "choose options" 0 0 4 \
1 option1 off \
2 option2 on \
3 option3 off \
4 option4 off

then after clicking a button you have the result in $INPUT.

i imagine the checklist could be populated with an array from built from mame output.

DTEAM

@valerino

Very nice!

Maybe it could be something like this :

I forgot + systems from my tutorial 😉

Or we could do 3 categories, Handheld, keyboardless (consoles) and computer? With a,b,c, d, ... classification?

Folly

@dteam said in Development of module-script generator for lr-mess and mame standalone:

@folly said in Development of module-script generator for lr-mess and mame standalone:

I know it can be confusing, but I think it is still :

standalone mame does both arcade/console and regular
arcade/console and regular are splitted into lr-mame and lr-mess

Exactly what It is. MAME standalone is the most « up to date » one.... suppose to be ...

We should keep both. Separately or not in the official Retropie package menu?.. I don’t know. If you do It separately, the user could install only one of those 2 emulators. It could be interesting.

I want to keep them both in, I assume they both will be maintained.
If something isn't maintained anymore in the future, we can just rename or remove easily.
If I split it up, more scripts can be generated, I think, that is not what we want.
Also, you have to go through the menu twice to install mame and lr-mess for 1 system, don't know if that is ideal.

Agree ?

An other solution can be, for example.
Select mame and/or lr-mess first and then select the system we want to install.
Perhaps we can use this idea.

BTW, Nice drawing 👍

Folly

@dteam said in Development of module-script generator for lr-mess and mame standalone:

I forgot + systems from my tutorial 😉

Or we could do 3 categories, Handheld, keyboardless (consoles) and computer? With a,b,c, d, ... classification?

If we want this, we have to extract more information somewhere.
At the moment we have only 1 row(array) to use for the menu.
I suggest we try that first.

Agree ?

Folly

I have updated the first post.
Adding also the menu idea and adding some more points :
👉 open : By @valerino / participants @DTEAM , @folly :
Create a front-end module-script in RetroPie-setup for our scripts.

structure/plan ?
dependencies check
download the repository in /home/pi/RetroPie-Setup/ext/RetroPie-Share or try to run the scripts online ?
add a menu in RetroPie-setup using the dialog api 120
try to keep multiple emulator/lr-cores in 1 generated script module 125
try to use 1 existing array for the menu 125
push the generated scripts in /home/pi/RetroPie-Setup/ext/RetroPie-Share/scriptmodules/ ?

I have tried to structure the information.
We should decide/discuss if we want to add/change things.

DTEAM

@folly said in Development of module-script generator for lr-mess and mame standalone:

I want to keep them both in, I assume they both will be maintained.
If something isn't maintained anymore in the future, we can just rename or remove easily.
If I split it up, more scripts can be generated, I think, that is not what we want.
Also, you have to go through the menu twice to install mame and lr-mess for 1 system, don't know if that is ideal.
Agree ?

Good point. I agree with you

@dteam said in Development of module-script generator for lr-mess and mame standalone:

I forgot + systems from my tutorial 😉

Or we could do 3 categories, Handheld, keyboardless (consoles) and computer? With >a,b,c, d, ... classification?

If we want this, we have to extract more information somewhere.
At the moment we have only 1 row(array) to use for the menu.
I suggest we try that first.

Agree ?

I also agree

Folly

@dteam

Thanks for letting me know.

I put it in our plan structure

We can always change the plan if something better comes up.

DTEAM

@folly
Nice what you did with the symbols in your first post . It's easy to follow

Folly

@dteam said in Development of module-script generator for lr-mess and mame standalone:

@folly
Nice what you did with the symbols in your first post . It's easy to follow

Thanks !
I think this will help a lot to see what is done and what we want to do.

I copy and paste from :
https://fsymbols.com/emoticons/
or
https://en.wikipedia.org/wiki/List_of_emoticons

I am trying also to get different colored text.
This is done with placeholder :
https://placeholder.com/

Test with diff :

- highlighted red
+ highlighted green

DTEAM

@folly said in Development of module-script generator for lr-mess and mame standalone:

structure/plan ?

For this point, the user could install lr-mess and MAME like it is right now in Retropie. When the user will come back in the package list for Mame or lr-Mess, it could be the same options, but.

re-install (from binary)
Install from source
Remove
install new systems <------(our new thing)
Package help
Package version information

No mather if you select "install new systems" in MAME or Lr-mess, the systems selected by the user (like coleco, Jaguar, etc.) will be intall for both (lr-mess and MAME).

It could be managed like what we see on my sketch for the other steps.

Are you agree? Other suggestions?

Folly

@dteam

I have to read it a few times to get the aha.
I will get back to you.

I think I understand what you mean.
Your idea is to integrate what we want to do into the mame module-script and in the lr-mess module-script.
Afterwards when you have installed you get the option to install our generated module-scripts.
Did I understand correctly ?