YARMan Web (BETA)

daeks

@pjft As I am not fixed on that as well, I will revert the path to be a common config parameter. I will move that to the fields definition itself on the next change with default pointing to emulationstation/downloaded_images.

Then its up to the installation later on which path will be used for uploading new media objects (common name I used for that).
Currently it is "static" in the defaults/config.json for all media objects (later on for each field with type "upload" in defaults/fields.json).

daeks

@pjft That would be my proposal for it: PR #21 Commit Diff

daeks

Anyhow, as the project progresses, I have applied some "standards" to it. The master branch is now protected and changes can only be applied by pull request if they are reviewed and checked against a modified version of the PSR2 coding standard.

Beside contributors, I think it would be nice to have some persons in place for testing changes and reviewing pull requests beside me before merging them.

J.Beau

Just reinstalled YARMan. Looking good! It doesn't display any emulators/roms at the moment. Is that correct?

daeks

@J.Beau yes you are right... I am testing with apache started with default "pi", but retropie starts the integrated server as root - sorry didnt know that :( - I updated the install script. Please retry it.

J.Beau

@daeks Worked! Just tested it with some Atari 2600 games. Started with an empty gamelist.xml. I was able to change one name, it doesn't seem to save any other changes after that. Uploading images doesn't work btw. Also, it doesn't use the gamelist.xml/images in the roms directory. They are also listed as roms. Not a problem, because I can move things over easily. I was doing everything manually anyway :) This looks very promising!

daeks

@J.Beau have you tested it only with safari? is it possible to try the upload in another browser?

I will test it with an empty gamelist :) haven't tried that. my fault.

gamelist.xml can be in the rom directory as well or have you changed anything? I am only aware of /home/pi/.emulationstation/gamelists as location. Interesting to see that images from the rom folder are listed as there is some extension white listing.

J.Beau

@daeks Tried it only with Safari. Emulationstation also reads gamelist.xml from the roms folder (/home/pi/RetroPie/roms/atari2600/gamelist.xml for example). I use this directory more because it is easier to move over romsets and their images and gamelist files :)

daeks

@J.Beau I believe the JQuery fileupload plugin has an issue with supporting safari. I will try to handle that and properly check compability.

Beside that, I have uploaded a fix for the empty gamelist issue. I missed the "new entry" method in the save call :)

Thanks for the clarification for the gamelist location. Currently it is "hardcoded" in a config file to emulationstation/gamelists. It can be modified later on.

herb_fargus

@daeks

So just to clarify this whole gamelist thing:

ES looks for gamelists in:

[SYSTEM_PATH]/gamelist.xml

~/.emulationstation/gamelists/[SYSTEM_NAME]/gamelist.xml

/etc/emulationstation/gamelists/[SYSTEM_NAME]/gamelist.xml

Image/video/marquee paths can be anywhere as long as they are specified in the XML

I'd have too look again at the scrapers to see where they default to

daeks

@herb_fargus thx. where exactly is system_path? in the rom folder?

herb_fargus

@daeks I'm pretty sure it's just the ROM path/home/pi/retropie/roms/system

J.Beau

@daeks said in Rebranded: YARMan Web (former RetroPie WebGUI) + Metadata Editor (BETA):

Beside that, I have uploaded a fix for the empty gamelist issue. I missed the "new entry" method in the save call :)

Works now! Awesome! I'll test uploading with another browser tomorrow :)

Arcuza

@daeks If you need free LAMP hosting (from a Azure Stack licensed data center) for a cloud service, maybe I can help. I would love to see community interaction and game recommendations based on rom set and ratings.

daeks

@Arcuza I dont think so. It is a local installation with some connections to the internet (reading retropie news, scraping, etc.).

@pjft / @herb_fargus For the time being I have changed the gamelist.xml search mechanism. I looks in the rom folder first and after that in the emulationstation/gamelists folder.

Nevertheless with the implementation of SQLite, I will change the whole gamelist/rom behavior:

Romlist will be parsed to internal SQLite database on first startup
Gamelist will be parsed to internal SQLite database on first emulator select
Changes will be saved into internal SQLite database instead of the gamelist file directly
New button "Sync" will update/import the gamelist.xml/roms to the database (in case of any external changes)
New button "Export to" will trigger a save to the gamelist.xml with some kind of dialog to be able to select which fields should be exported

Beside increasing the performance for large romsets, another example would be that users are able to maintain all metadata fields like image AND video at the same time, but can choose time by time if they want to include for video tag in the gamelist.xml or not.

Arcuza

@daeks In your web front, people would be able to set game rating and emulator compability. If we would be able to collect that information from all users into one single location together with background data like times played, time spent, days since last played, emulator used we would have a super great database were we could find issues and make game recommendations to users.

I love data mining and I have already written a recommendation algorithm that could be used for that purpose.

And it would be perfect to use the same authentication (login) as for this forum.

I just cannot see why we're not capitalizing on this opportunity.

daeks

@Arcuza Personally I am no friend of data mining but I understand your purpose and the idea itself. It is an interesting approach to get features ready like "proofed to be compatible with...", "recommended / rated by community" but that should be discussed also with @herb_fargus and @BuZz. From my opinion there are enough places out there collecting such information already on a base level.

From my point of view talking about YARMan, the source code is open source and contributions are welcome. So if someone (you?) find some time for it, go ahead and prepare a pull request for it. Currently I am concentrating on the basic features listed here.

daeks

New modules added:

Configuration Editor
- Support of general config
- Support of Emulator's config (was a wish on github)
- Each save results in a .bak file
Log Viewer
- System logs
- Support of viewing RetroPie-Setup's gz archives

grenade44

@daeks said in Rebranded: YARMan Web (former RetroPie WebGUI) + Metadata Editor (BETA):

New modules added:

Configuration Editor

Support of general config

Support of Emulator's config (was a wish on github)

Each save results in a .bak file

Log Viewer

System logs

Support of viewing RetroPie-Setup's gz archives

Thanks for the emulator config. 😀
I love all the hard work you are putting into this. Can't wait to get scrapper support and game management. Wish I could code and help.

meleu

@daeks said in Rebranded: YARMan Web (former RetroPie WebGUI) + Metadata Editor (BETA):

I am not very familiar with the integrated webserver. If it supports all the stuff like apache does, we can also implement that. Currently I am more focusing on the application itself instead of the setup in retropie. I will try to figure out how the integrated one could be used but would really appreciate any help on that.

Great tool man! Thanks for sharing.

I didn't delve into the yarman apache settings, but I'm curious about what features would you need to see in the webserver?