Thanks for your reply. I definitely understand and appreciate the richness afforded by oXygen's Project-centric system. My request was somewhat open-ended: to find "some way" to achieve the following 2 goals: (1) to allow users to interact with a folder in the same basic way as the Project pane allows, while relieving users of the "overhead" of having to save a new project file to disk in the process, and ideally (2) to empower the user (and external applications like GitHub Desktop) to "open a folder" in oXygen via the command line.
I have, in fact, started using a "scratch project file" (I called mine "dummy.xpr"), and this does relieve me of the burden of creating a new project every time I want to open a folder in oXygen. This does largely take care of #1, which is great, although it does strike me as somewhat inelegant to require that a file be saved to disk for this use. (It didn't occur to me to do this until last week, after using oXygen for nearly 10 years! So it's my failure of imagination, but I suspect I'm not alone.) That said, this technique doesn't address the use cases I described for goal #2: a mechanism to "open a new folder" via the command line (whether the folder is "appended" to an existing project or a new project is created).
To illustrate this idea with a pseudo command, imagine if the "oxygen" command could take a new
Code: Select all
oxygen -project /tmp/scratch.xpr repo/src
This parameter would take the project file and append the file/folder to an existing project, or create a new project if it does not exist. Presumably, the command would also switch the Editor to that project, if it was not already active. In other words, this flag would operate much as right-clicking on the project root and selecting Add Files or Add Folders does currently.
I hope this clarifies the idea. Thanks again!