ksylvan / zoom_opm Goto Github PK

Start a Zoom meeting and then share a window.

Starting the zoom_roster script then results in the following dialog:

This feature would work like this:

• Certain participants need to be renamed when they join the meeting. For example, a class of participants has to have a certain character (like #) prepended to their names.
• Using some sort of list, scan the participant list and see if any of those so named don't have the correct prefix character, and if that is the case, rename them.

zoom-manage sees if zoom is running and if not, starts it. The intent is for the interaction to be easy and intuitive:

If zoom is not running, start it.
If we are not in a meeting, display a dialog to the user, asking them to join a meeting.

% ./zoom-manage roster
./zoom-manage:26112:26117: execution error: Error: System Events got an error: Can’t get menu bar 2 of process "zoom.us". Invalid index. (-1719)

The # character is used to designate a line as a comment.

The breakout room format looks like this:

# You can commment your breakout text files
#
Virtual Cafe 1
Virtual Cafe 2
Virtual Cafe 3

So if you want to create a room called "# Leaders Room" you cannot do it.

Same with the rename mappings:

# Testing
Kirk->Admiral James T. Kirk
Kayvan Sylvan-># Kayvan Sylvan

Then if you wanted to rename "# Kayvan Sylvan", you could not.

Reproduce by:

./zoom-manage server
./zoom-manage dashboard
./zoom-manage roster

The frontend should show your meeting participants.

Then kill the server (control-c in the terminal window, and close the window), and restart it.

./zoom-manage server

Refresh the frontend dashboard window, and you'll see the lists are empty.

in the dashboard web browser window, use Developer Tools or Inspect to look at the javascript REST calls. You'll see messages like this:

Access to fetch at 'http://localhost:5000/waiting' from origin 'null' has been blocked by CORS policy:
No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response
serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

While this CORS denial is happening, you can go to the FastAPI Swagger page at http://localhost:5000/docs#/ and you'll see that the endpoints are working.

By quitting your browser (Brave in my case) and restarting it, everything works again.

Currently, all the backend endpoints are defined, like

@app.post("/cmd_hands")
def execute_hands():
    result = subprocess.run([zoom_manage, "hands"], capture_output=True)
    return result

Changing methods to async will require fixes to the frontend javascript code.

Read the note here: https://github.com/ksylvan/Zoom_OPM/blob/main/docs/Windows.md about some ideas.

The feature would be similar to the re-name feature enhancement.

Given a list, when the participant with that name show up in the meeting, grant them co-host privileges.

You start a large zoom meeting (100+ participants) with Waiting Room enabled.

Your participant has a connectivity problem and gets bumped off and comes back a few minutes later, ending up in the Waiting Room till you let them back in.

Modify zoom-manage with a connection to the backend so that a participant coming in after being dropped off is auto-admitted.

The Host/Co-Host/me roles can be tracked for each name, along with the display-name.

The idea being that '#Kayvan Sylvan (Host, me)' participant name would create a participant record:

name: 'Kayvan Sylvan'
roles: 'Host, me'
display: '#Kayvan Sylvan (Host, me)

and then a change to '#Kayvan Sylvan (Co-host, me)' would also create an event record:

event_id: 456
name: 'Kayvan Sylvan'
timestamp: '20231103-23:13:09'
note: 'Role changed from (Host, me) to (Co-host, me)'

Similarly, changing '#Kayvan Sylvan (Host, me)' to '@kayvan Sylvan (Host, me)' would result in an event:

event_id: 456
name: 'Kayvan Sylvan'
timestamp: '20231103-23:13:59'
note: 'Display name changed to "@Kayvan Sylvan (Host, me)"'

Make sure to only create the terminal when the server is not already running.

Also, if the terminal app is already running, create a new window and run the server there.

Instead of:

./zoom-manage server

and then having to kill the server manually.

do this:

./zoom-manage server start

and then

./zoom-manage server stop

Fix the zoom-manage breakout get command so it also generates lists of participants inside breakout rooms.

The idea is to have a text file with the breakout rom names.

The script should then read that file and set up the breakout rooms and rename them.

For Example:

With a file containing:

Virtual Cafe 1
Virtual Cafe 2
Virtual Cafe 3
Virtual Cafe 4
Virtual Cafe 5
Leader Room

The script should create and rename 6 breakout rooms.

Instead of the dialog box asking to start a meeting, here's what happens now:

./zoom-manage 
./zoom-manage:19535:19540: execution error: Error: System Events got an error: Can’t make missing value into type UI element. (-1700)

When running a breakout create command, when user is not host/co-host:

./zoom-manage breakout create breakout/WSO-groups.txt
./zoom-manage:26124:26129: execution error: Error: System Events got an error: Can’t make missing value into type UI element. (-1700)

This is due to the lack of "breakout" status menu. Notice this and exit gracefully.

Without Zoom running, run the script:

./zoom_roster.applescript

When the dialog showing "Please join the Zoom Meeting and press OK." shows up, join a meeting and press OK.

You'll get the Quit dialog showing: "Can’t get every text item of missing value. (-1728)"

If a participant name has annotations like (Co-host) or (Host) or (Co-host, me) or (Host, me) we should
strip that off and store the information as attributes.

This will also allow us in the backend to compare the attributes and log events related to hosting and co-hosting
changes in a privilege table.

To recreate:

Set up a meeting with some pre-created breakout rooms.

Now, running the create script shows this error:

./zoom-manage breakout create breakout/WSO-groups.txt
./zoom-manage:25968:25973: execution error: Error: System Events got an error: Can’t get window "All existing rooms will be replaced." of process "zoom.us". (-1728)

Because hitting the "Recreate" button now brings up this menu:

The /joined_list and /waiting_list endpoints get a json list of names and input them into the database.

Enhance zoom_manage with the option of doing updates in batches. So, for a 1000-person meeting, we might send batches of 50 names to the endpoints, instead ofattempting to send all of them at once.

The issue is that the code is looking for a "Manage Participants" submenu of the ZOOM status menu in the menu bar.

When you are not a host or co-host, that menu item is called "Participants".