ProxymanApp / ProxymanApp/Proxyman

Scripting Tool Folders feedback

Open
#1,263 3 comments 0 reactions 1 assignee View on GitHub

@NghiaTranUIT is already working on this.

Since Jun 24, 2022.

enhancement
Dominant language
No language data
Stars
7k
Forks
237
PR merge metrics
No merged PRs in 30d

Description

Some various feedback regarding the Scripting folders implementation (I've only looked at Scripting, not the other areas where this is changed). Let me know if anything isn't clear, or if you would like anything broken out into a separate issue.

  • My initial reaction to Script Editor being a separate window is that it feels like I have too many windows to manage. That said, the choice makes sense, and being able to see multiple scripts at the same time (e.g. separating tabs out into separate windows) has obvious benefits, so I think it's an overall improvement. I wouldn't complain about an option to keep it all in a single window, but I'm not sure it would be worth the time to implement as an option.

  • Clicking "Save & Activate" on a script doesn't update the checkbox for that script in the Scripting window until the Script Editor window is closed.

  • I wonder if the "Save & Activate" button on scripts should be changed to just "Save"? Now that scripts won't run unless both the folder and individual script are enabled, and currently, the activation only applies to the script, not the folder. This makes sense, since enabling the folder would turn on all enabled scripts in the folder, which may not be intended by the user. This would also affect the "Saved and Active" indicator above the script editor. Maybe it should only show green if both folder and selected script are active?

  • Related, I think the individual scripts within a folder should use the disabled-and-checked state (like when the Scripting Tool is disabled, checked checkboxes are grey) if the folder isn't checked.

  • The Script Editor should remember my editor/console sizes when opening new scripts.

  • I would like to be able to edit scripts even if the Scripting Tool is disabled. (This isn't a change with the new Scripting UI, but I can't recall if I've mentioned it before.)

I continue to be delighted with how Proxyman keeps improving. Great job @NghiaTranUIT!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.