It's probably better to include a dropdown object in the main GUI providing the choices to apply script on "selected lines" or "all lines".
It's also a good idea to have a checkbox object in the GUI corresponding to the python script as "Apply script on line(s) corresponding to the same:" with a following dropdown containing these options: "Style", "Actor", "Effect" and also provide a dropdown for each one of these.

the lua script doesn't respect lines' order. it reverses it.
in addition to the mentioned issue, because we don't take into account lines added, I think if multiple selected lines exist, new lines for lines other than the first one will be added in a wrong position.

As we want to have separate macro for each automation, we need to have these options on parameters' gui

To navigate easily through the [possibly] many scripts in the list we can add an edit control object to the main GUI and search through the names of the scripts in the list containing the text in that edit control object.

Also, in order to distinguish between karaoke effects and typesetting scripts we can:

• either recommend the developers to name the folder of their script (which is also currently the name that's shown in the script list) with a [KFX] at the end of the folder name (e.g.: sakura [KFX]) and name the typesetting script with a [TS] at the end
• or recommend the developers to add a variable to the parameters file of their scripts for karaoke effects (e.g.: kfx: Boolean) and we use that variable to name the scripts in the main GUI list properly.

This way we can search for [KFX] and [TS] in the edit control object to list all the karaoke effects and all the typesetting scripts respectively.

It is almost self explanatory. But at this point we just provide the option for multiple buttons showing on the python script input GUI. We should manage the functions for these extra buttons in the lua script.

User can call scripts separately from automation tab

For avoiding utf issues, lua's regex must be avoided. Regex from re is the best alternative. It's a real Regex too.

As silly as it seems I have been so lazy to take care of this :)

Due to difficulty with loading all the features needed from lua YAML libraries into Aegisub, it might be better to modify the script to use JSON libraries instead of YAML.

per need of having multiple guis and back button, we should use a state machine to transit between states

For now include three JSON files for parameters:

1. A file to construct the GUI related to the python script named "gui_params.json".
2. A file to store the user's selection so that the python script can read from named "gui_returned_values.json".
3. A file to store the default values named "gui_params_default.json" (initially the "gui_params.json" is the same as "gui_params_default.json").

User can save settings as profile for the script and load them and choose default between them

settings.json should refactor to this format too:

{
    "Default Profile": "Ali Fav",
    "Profiles": [
        {
            "Name": "Default",
            "Line Filter": {
                "Line Type": "Selected"
            },
            "Controls": [
                {
                    "name": "label1",
                    "x": 0,
                    "label": "Direction:",
                    "y": 0,
                    "class": "label",
                    "height": 1,
                    "width": 1
                },
                {
                    "x": 1,
                    "y": 0,
                    "class": "dropdown",
                    "items": [
                        "Horizontal",
                        "Vertical",
                        "Slant",
                        "Oval"
                    ],
                    "hint": "",
                    "value": "Horizontal",
                    "width": 1,
                    "name": "dropdown1",
                    "height": 1
                },
                {
                    "max": 1000000,
                    "x": 2,
                    "y": 0,
                    "class": "floatedit",
                    "min": -1000000,
                    "hint": "The angle:\n in case you are selecting Slant",
                    "value": 45,
                    "step": 0.01,
                    "width": 1,
                    "name": "floatedit1",
                    "height": 1
                }
            ]
        },
        {
            "Name": "Ali Fav",
            "Line Filter": {
                "Line Type": "Selected",
                "Filter Type": "Style",
                "Filter Term": "Mohsen"
            },
            "Controls": [
                {
                    "name": "label1",
                    "x": 0,
                    "label": "Direction:",
                    "y": 0,
                    "class": "label",
                    "height": 1,
                    "width": 1
                },
                {
                    "x": 1,
                    "y": 0,
                    "class": "dropdown",
                    "items": [
                        "Horizontal",
                        "Vertical",
                        "Slant",
                        "Oval"
                    ],
                    "hint": "",
                    "value": "Horizontal",
                    "width": 1,
                    "name": "dropdown1",
                    "height": 1
                },
                {
                    "max": 1000000,
                    "x": 2,
                    "y": 0,
                    "class": "floatedit",
                    "min": -1000000,
                    "hint": "The angle:\n in case you are selecting Slant",
                    "value": 45,
                    "step": 0.01,
                    "width": 1,
                    "name": "floatedit1",
                    "height": 1
                }
            ]
        }
    ]
}

We must implement an update feed like dependency control that allows user to install new scripts and update the existing ones. we should install dependencies from requirements.txt if exists

Windows' sizes need to be calculated based on screen resolution.

We should have some already implemented useful samples from the beginning. We have 2 now. but a few more is better

I don't know a good solution to develop and test it on aegisub concurrently. I use vscode myself and I'm ok with it. Whole project folder is under my control and i can easily change and edit files. I have lua linting and... but the problem is after each change, I should copy project's files to aegisub's folder. It's frustrating. for just a one file is ok. for example I have both pyegi.lua opened in my editor and copy contents between them. but sometimes changes are multiple files. It increases the probability of human errors too.
I think we should have a simple automated task to handle the synchronization.