Skip to content
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

Merge with original VSCode extension #32

Closed
Colin-Stone opened this issue Apr 1, 2019 · 2 comments
Closed

Merge with original VSCode extension #32

Colin-Stone opened this issue Apr 1, 2019 · 2 comments
Labels

Comments

@Colin-Stone
Copy link
Member

@Colin-Stone commented on Mon Apr 01 2019

Keep all of the Zowe VSCode extensions as one extension


@Colin-Stone commented on Mon Apr 01 2019

Consider creating a joined up taxonomy structured as follows:

Zowe
|
| ----Favorites
|
| ---- MyProfile 1
		|
		| ---- Datasets
		|		|
		|		| ---- MYUSER.TEST.JCL
		|		|	:	:
		|		| ---- MYUSER.PROD.JCL
						|
						| ---- COMPARE
						| ---- COPY
		|
		| ---- USS Files
		|		|
		|		| ---- /u/myuser
		|				|
		|				| ---- file1.txt
		|
		| ---- Jobs
				|
				| ---- AJOB1(INPUT)
				| ---- AJOB2(ACTIVE)
				| ---- TSU1(ABEND S222)
@Colin-Stone
Copy link
Member Author

Counter argument against the above layout came in asking that we retain the separation as it is not usual that a customer uses the features at the same time and the views would become very cluttered with elements not needed all of time. So the proposal is for this.
Screenshot 2019-04-08 at 13 17 49
Maybe we can start with this and reconsider once complete.

@phaumer
Copy link
Member

phaumer commented Apr 11, 2019

Created issue: #38

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants