-
Notifications
You must be signed in to change notification settings - Fork 2
Bits that make up JSE
j0yu edited this page Aug 6, 2016
·
3 revisions
JSE is made up of the following
-
1 JSE Maya Manager, then followed by...
- one or more JSEs, each main window containing...
-
1 master pane layout, which like a pane layout will hold either...
- a pane, or
- a pane layout, which will hold either...
-
a child pane, or
-
a child pane layout,
which may contain many more and more nested pane layouts
-
-
1 master pane layout, which like a pane layout will hold either...
- one or more JSEs, each main window containing...
Let's break down what I mean by each.
Rule
- Only 1 permitted per each Maya session, at any time
Purpose: Manage the multiple JSEs
- Syncronise all script editors contents
- Loading saved JSE windows when JSE is launched, if any
- Saving JSE windows when Maya shuts down
- Contain and edit global default settings for all JSE should they need to reset their settings
Rules
- Contain only 1 master pane layout
- Can only be destroyed if user chooses to:
- Close the one and only remaining pane that is the sole child of the master pane layout, or
- Destroy the JSE through multiple confirmation messages/options
Purpose: Give the user a banging script editor brah!
See the main goals of this project for what our script editor should do.
-
Commands/Actions
- [Launch Scripts] (https://github.com/j0yu/JSE/wiki/Commands#launch-scripts)
- [Debug] (https://github.com/j0yu/JSE/wiki/Commands#wrench-debug-wrench)
- Shelf Item Set-up/Usage
- Keyboard Shortcut setup
These are main, core concepts that may already exist now but written for planning future development