-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce Executor View #1596
Comments
Could you give a detailed example for each views? How do you expect the trees look like? My guess: Showing all the target files(==product files, *.tvn) in Executor view? |
Executor view contains the Simulator and device target.
I updated a Executor view image. :) |
@jyoungyun Thanks for the explanation. This is off-topic but how did you upload the image? I've been failing uploading it and I also failed to get URL exception approval from IT center. |
What
I would like to propose a new concept to support product file execution.
Product file generated through compilation of cfg files with toolchain can execute multiple functions such as inference or profile.
Now, product files can be inferred and profiled through ONE Explorer. However, considering the target device, it is not easy to express it as a toolchain and a target view. This is because the product file can be executed on the simulator of toolchain and the target device.
So I suggest the executor view.
It includes a simulator of toolchain and a target device.
Like tje toolchain view, the user can select the default executor. The default executor is then used to run the product file.
When a user installs a new toolchain, a simulator is automatically added. It is natural scenario to add toolchain and simulator when installing a toolchain. (If not, I am also considering changing the name of Toolchain view as Compiler(?).)
Details
Toolchain view
Executor view
View design
/cc @Samsung/one-vscode
The text was updated successfully, but these errors were encountered: