vzcode 0.2.1 → 0.3.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +30 -17
- package/cli.js +5 -0
- package/dist/assets/{index-5e86a45f.js → index-4694dca8.js} +33 -33
- package/dist/assets/index-58524f84.css +1 -0
- package/dist/favicon.ico +0 -0
- package/dist/index.html +3 -4
- package/package.json +1 -1
- package/src/App.jsx +3 -2
- package/src/settings.jsx +34 -0
- package/src/style.css +30 -1
- package/dist/assets/index-5c2f5f84.css +0 -1
- package/dist/vite.svg +0 -1
package/README.md
CHANGED
|
@@ -19,14 +19,20 @@ This project is nascent but has enough features to actually use, a minimum viabl
|
|
|
19
19
|
- Syntax highlighting for several Web languages
|
|
20
20
|
- Auto-saves changes back to the file system
|
|
21
21
|
|
|
22
|
-
##
|
|
22
|
+
## Use Cases
|
|
23
23
|
|
|
24
|
-
|
|
24
|
+
### Local Editor
|
|
25
|
+
|
|
26
|
+
One way to use this is as an editor on your system, taking the place of an existing editor like VSCode or Vim:
|
|
25
27
|
|
|
26
28
|
- Install with `npm install -g vzcode`
|
|
27
29
|
- Launch with `cd myProject; vzcode`
|
|
28
30
|
|
|
29
|
-
|
|
31
|
+
### Project-specific Editor
|
|
32
|
+
|
|
33
|
+
Another way to use this is to set up this editor within your project. This gives developers of your project a quick way to start editing code, in case they do not already have a preferred IDE, or they want to take advantage of VZCode features.
|
|
34
|
+
|
|
35
|
+
This can be done introducing a new npm script and dependency like this:
|
|
30
36
|
|
|
31
37
|
```json
|
|
32
38
|
{
|
|
@@ -42,6 +48,12 @@ Another way to use this is to set up this editor within your project by introduc
|
|
|
42
48
|
|
|
43
49
|
Then run `npm run edit` to start the editor.
|
|
44
50
|
|
|
51
|
+
### Staging Site Editor
|
|
52
|
+
|
|
53
|
+
[Experimental idea]
|
|
54
|
+
|
|
55
|
+
VZCode could be hosted on a long-running server. The idea here is that an individual or team that is developing a product can make code changes, leveraging multiplayer mode remotely, and have those changes appear instantly on a "staging site" (a server hosting the latest version of the work) running something like the Vite dev server. This would allow collaborators to, for example, make minor tweaks live on client calls and have the client see the updates in real time.
|
|
56
|
+
|
|
45
57
|
## Stack
|
|
46
58
|
|
|
47
59
|
- [NodeJS](https://nodejs.org/en/)
|
|
@@ -83,32 +95,33 @@ See also [VZCode Kanban Board](https://github.com/orgs/vizhub-core/projects/2/vi
|
|
|
83
95
|
|
|
84
96
|
February 2023
|
|
85
97
|
|
|
86
|
-
- Get the first version working, including:
|
|
87
|
-
- ShareDB server
|
|
88
|
-
- Auto-save
|
|
89
|
-
- Edit the content of multiple files (no support for folders initially)
|
|
98
|
+
- [x] Get the first version working, including:
|
|
99
|
+
- [x] ShareDB server
|
|
100
|
+
- [x] Auto-save
|
|
101
|
+
- [x] Edit the content of multiple files (no support for folders initially)
|
|
90
102
|
|
|
91
103
|
March 2023
|
|
92
104
|
|
|
93
|
-
- Make it usable, including:
|
|
94
|
-
- UX for adding new files, renaming files, deleting files
|
|
95
|
-
- Implement presence (the ability to see the cursors of others in real time)
|
|
96
|
-
-
|
|
105
|
+
- [x] Make it usable, including:
|
|
106
|
+
- [x] UX for adding new files, renaming files, deleting files
|
|
107
|
+
- [x] Implement presence (the ability to see the cursors of others in real time)
|
|
108
|
+
- [x] Publish an early release to NPM
|
|
109
|
+
- [ ] Test out how it works using tunneling services such as NGrok
|
|
97
110
|
|
|
98
111
|
April 2023
|
|
99
112
|
|
|
100
|
-
- Add support for nested directories, including:
|
|
101
|
-
- Develop a tree-based sidebar UI allowing directory navigation
|
|
102
|
-
- Dogfood the product and try to collaboratively develop something, maybe a data visualization
|
|
103
|
-
- Gather feedback from early users and iterate based on that
|
|
104
|
-
- Publish a YouTube video presentation of the work to date
|
|
113
|
+
- [ ] Add support for nested directories, including:
|
|
114
|
+
- [ ] Develop a tree-based sidebar UI allowing directory navigation
|
|
115
|
+
- [ ] Dogfood the product and try to collaboratively develop something, maybe a data visualization
|
|
116
|
+
- [ ] Gather feedback from early users and iterate based on that
|
|
117
|
+
- [ ] Publish a YouTube video presentation of the work to date
|
|
105
118
|
|
|
106
119
|
## Team
|
|
107
120
|
|
|
108
121
|
- Curran Kelleher
|
|
109
122
|
- Students from [RPI RCOS](https://rcos.io/)
|
|
110
123
|
- Additional external collaborators, TBD
|
|
111
|
-
-
|
|
124
|
+
- Contributions welcome!
|
|
112
125
|
|
|
113
126
|
## Spaces
|
|
114
127
|
|
package/cli.js
CHANGED
|
@@ -46,6 +46,11 @@ ShareDB.types.register(json1Presence.type);
|
|
|
46
46
|
|
|
47
47
|
const app = express();
|
|
48
48
|
|
|
49
|
+
app.post('/saveTime', (req, res) => {
|
|
50
|
+
//autoSaveDebounceTimeMS = req.body.autoSaveDebounceTimeMS;
|
|
51
|
+
console.log('autoSaveDebounceTimeMS', req.body);
|
|
52
|
+
});
|
|
53
|
+
|
|
49
54
|
// Use ShareDB over WebSocket
|
|
50
55
|
const shareDBBackend = new ShareDB({
|
|
51
56
|
// Enable presence
|