Project Context about subethaedit HOT 4 OPEN

👍 and +1. With the open source release of SubEthaEdit 5, I went to check it out. (The last time I checked it out was a long time ago.) This ticket was my immediate thought upon trying to use SEE5 in my daily workflow.

from subethaedit.

I wonder how to implement this obeying the App Sandbox constraints. Here are some options (and objections) that came to my mind

• Ask the user to select a project root (not a great UX)
• Create a privileged helper (not AppStore compliant (?) )
• Drop App Sandbox (not AppStore compliant (!) )
• Only use a project context if the user selects a folder (too implicit?)

I wonder whats your preferred way @monkeydom

from subethaedit.

I wonder how to implement this obeying the App Sandbox constraints. Here are some options (and objections) that came to my mind

• Ask the user to select a project root (not a great UX)
• Create a privileged helper (not AppStore compliant (?) )
• Drop App Sandbox (not AppStore compliant (!) )
• Only use a project context if the user selects a folder (too implicit?)

I wonder whats your preferred way @monkeydom

I want us to stay AppStore and Sandbox compliant. Currently I see 2 ways for us:
a) make the user open the root of the workspace/project context
b) make the user give us full disk access privileges (like e.g. Alfred does)
c) make the user give us disk access by an open dialog (like e.g. BBEdit does it)

This is probably an ongoing discussion as use of local tools/language servers, plugin infrastructure, etc. is important as well for follow up features.

from subethaedit.

Textmate in the interaction with it's mate shell integration utility implements it by opening a a folder as a project, and opening single files as single files. I quite like the simplicity and predictability of this and would advise to go a similar route.

from subethaedit.