re-work multi --styles-file

[w-e-w]

Description

• an alternative implementation to Ensure default styles file is loaded (#7) #14700
• for resolving [Bug]: Style file defaults to ".csv" when "*.csv" is used to load multiple style files. #14681

---

users can specify multiple style file path by using wildcards and multiple entries of --styles-file

• possible to specify styles files from different directory
• the default styles file can be explicitly set by the user

Changes

cmd arg --styles-file change action to append str whitch forms a list internally same as --gradio-allowed-path
if no --styles-file is set by the user is then defaults to ['styles.csv']
--styles-file accepts paths or paths with wildcard *
also alow ? to be used to match a single character (previously only * can be used), https://docs.python.org/3/library/fnmatch.html#module-fnmatch

Default styles file path behavior

1. the first --styles-file entry is use as the default styles file path
2. if thers a * or ? in the path, it is used as wildcard pattern, the first matching file is used as default sytyles
3. if no match is found, create a new styles.csv in the same dir as the first path

other changes

• when saving a new style it will be save in the default styles file
• when saving a existing style, it will be saved to file it belongs to
• the order of the styles files in the styles dropdown can be controlled by the order of --styles-file

---

cmd arg example

use multiple --styles-file all at once

--styles-file "B:\\styles_dir_1\main_styles_file.csv"
--styles-file "B:\\styles_dir_1\sub_styles_file.csv"
--styles-file "B:\\styles_dir_1\prfix_*.csv"
--styles-file "B:\\styles_dir_2\*_suffix.csv"
--styles-file "B:\\styles_dir_3\*.csv"

this example would load
B:\\styles_dir_1\main_styles_file.csv and use as default
B:\\styles_dir_1\sub_styles_file.csv
load every file in styles_dir_1 matching prefix_ and suffix .csv
load every file in styles_dir_2 matching suffix _suffix.csv
loda every .csv in styles_dir_3

---

@cjj1977 can you check if this satisfies your requirements

Checklist:

• I have read contributing wiki page
• I have performed a self-review of my own code
• My code follows the style guidelines
• My code passes tests

[MisterSeajay]

@w-e-w I will have a look & test. Gotta remind myself how to fetch an upstream branch into my fork.

[w-e-w]

@w-e-w I will have a look & test. Gotta remind myself how to fetch an upstream branch into my fork.

github desktop is quite handy

[MisterSeajay]

@w-e-w This looks good to me. Ran through my own use-cases and all seems fine.