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

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 ?

DTEAM

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

@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 ?

Yes it is, It will be on both menu and it will do the same thing no matter where you go after (lr-MESS or MAME). So that way, you will continue to generate your command lines for systems like coleco or others for lr-Mess and MAME in one time.

Folly

@dteam

Could we do it a bit different ?

I would suggest to make it possible to install mame an lr-mess though our menu.
But the menu will use the official mame/lr-mess module-scripts.

Then we keep it separately, our module-script and the mame/lr-mess module-scripts.

What do you think ?

DTEAM

@folly

good idea , sounds good!
At the end, It must be simple for newbies . I think It should be the target

Folly

@dteam

Indeed, we should make/keep it simple.
Ok, tomorrow I have to go with the boat to an island.
Then I have some time to make a summarize.
Then we get back to @valerino if this is doable.

valerino

hi guys, sorry but today i've been very busy @ work !

i think @DTEAM 's idea to integrate with existing mame/mess script is the cleaner .... no ?

also in my fork i extended already present scripts with extra features when i needed, i.e. in some i added the option to install from source the most recent version from github instead of the branch officially supported by retropie, things like that.

imho this is the clearer way ....

v.

Folly

@valerino

Ok, if you think the @DTEAM is the cleaner way, we can do it like that.
I have only one concern.
When a generated module-script is generated, RetroPie-setup will not directly see it.
So normally I have to restart.
Does it have a way of refreshing ?
If there is no such option we could use retropie_packages.sh to install it directly after generation.

Folly

I copied generate-systems-lr-mess_mame-1v8-alpha.sh as generate-systems-lr-mess_mame-2v0-alpha.sh to my repository.

I did this so we can make changes to that script which are possibly necessary to make our idea work.

I already made some changes to the 2v0 script :

It will install the run_mess.sh script if not detected.
create extra platforms.cfg so we can run the script online with curl and also have a nice extra platforms.cfg
removed help / not necessary if used in the menu
date command removed / turn off generate all message shortened
generated files come in RetroPie-Setup/ext
- found that if there are already module-scripts, with the same name in the original directory, then these will be used (you get a warning). So old scripts have to be removed if they were already there.

This is how it will look like in the external repositiory directory :

valerino

@folly i will check asap, surely it's possible to refresh retropie's internal structures. look at what it does in its own startup: https://github.com/RetroPie/RetroPie-Setup/blob/master/retropie_packages.sh#L61

Folly

@valerino

That would be nice indeed !

Folly

@DTEAM @valerino

I have made some wonderful improvements !

We can now generate without even having the script on the computer and it will place the generated scripts in the directory for external repository's. 137
It will also install the run_mess.sh script if not detected.

Try this command :

curl "https://raw.githubusercontent.com/FollyMaddy/RetroPie-Share/main/00-scripts-00/generate-systems-lr-mess_mame-2v0-alpha.sh" | bash -s kgradius

ps.
We can use this now, but the normal way still works. So we can use it both ways.

Edit :
Updated quite a lot in the first post.

Folly

@dteam

Something to check I think :
https://retropie.org.uk/forum/topic/30155/lcd-handhelds-mame-0-229-dat

DTEAM

@folly
I don't know if he is aware of what we are doing.

Folly

@dteam

Indeed, but he is very busy.
He has to read quite some stuff, we already know.
I think he will get the jist.

Folly

@valerino

We are a bit curious, have you :

read the first post ?
read the commented parts in the script on how it's working ?
installed some handhelds ?
used the get script ?

valerino

@folly heya :) i've read the first post, yes. but i haven't tried anything, sorry but i've very few time to dedicate to my hobbies at the moment.

anyway, i have some suggestions:

forget the 1st post, have a github (being my repo, or a new one doesn't matter.... and list issues/ideas there)
decide if we want to use my fork or have another, merging mine+folly+dteam work. just, having a single repo imho is the way to go to avoid fragmentation.
push retropie admins to merge this stuff in the official repo :)

DTEAM

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

@dteam
Indeed, but he is very busy.
He has to read quite some stuff, we already know.
I think he will get the jist.

I was talking about the new thread you mentionned above. I had an answer from him. He is a Global Moderator on this site and he gave me his impression about what we are doing.

https://retropie.org.uk/forum/topic/30155/lcd-handhelds-mame-0-229-dat

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:
@dteam
Indeed, but he is very busy.
He has to read quite some stuff, we already know.
I think he will get the jist.
I was talking about the new thread you mentionned above. I had an answer from him. He is a Global Moderator on this site and he gave me his impression about what we are doing.

https://retropie.org.uk/forum/topic/30155/lcd-handhelds-mame-0-229-dat

Sorry , misunderstood, haha.
I wasn't aware of that because I didn't read the stuff.
Will do that.

Edit :
Read it, indeed, seems he isn't aware of specific things,
but strangely enough said that he was inspired by our threads.
Mmmm,......

I did an extra post on the thread !

Folly

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

@folly heya :) i've read the first post, yes. but i haven't tried anything, sorry but i've very few time to dedicate to my hobbies at the moment.

anyway, i have some suggestions:

forget the 1st post, have a github (being my repo, or a new one doesn't matter.... and list issues/ideas there)

decide if we want to use my fork or have another, merging mine+folly+dteam work. just, having a single repo imho is the way to go to avoid fragmentation.

push retropie admins to merge this stuff in the official repo :)

Ok, Seems a good plan.

Although you have to take into account, not everyone is that keen on github.
And also, not everyone has a github account.
For me, the syncing and pushing things is something that's still blurry for me too.
So that is why I keep everything here, so everyone can help to improve.

But indeed, with your way of doing, we all could learn quite a bit more.