forked from fathominfo/processing-p5js-mode
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathtodo.txt
103 lines (84 loc) · 4.17 KB
/
todo.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
0010 (1.2.3 or 1.3)
X add revision check to the build
_ still a lot of temp files left around?
_ write the temp stuff to another folder?
_ when using p5jsMode, just require that sketches are saved
_ too many problems with unsaved code not working properly
_ (instead of doing the weird tricks with temp files)
_ better means of understanding actual use of p5jsMode?
_ shows as installed on 30% of machines using the manager
_ need better solution when opening sketch.js files
_ just rename the sketch.js file itself
_ https://github.com/fathominfo/processing-p5js-mode/issues/14
_ This might be better handled by an “Import” tool that pulls
_ from a local folder or from the online editor.
_ if starting a new sketch, must reload the browser first?
_ what's happening here? concerned about code mods not updating
_ set no cache on returned objects?
_ when sketch is moved while the editor is open
_ it can't re-create any of the supporting files
_ leaving you with a broken sketch, which is messy b/c it looks ok
_ how to enable the cdn version?
_ would be nice to use by default, but don't net connection as requirement
_ or is there a way to handle it inside the p5js server?
_ just have a preference/checkbox in the menu
_ enabling the cdn will remove p5.min.js from the sketch
_ new sketches inherit the last setting
_ how do we bring back the auto-update block if it's broken?
_ or if it's not present, stop updating that file?
_ ability to update p5*.js in the libraries subfolder
_ automatically notify user if version in the template is updated?
_ not just about p5jsMode updates, but updating older sketches
_ this could be a Mode menu item, grayed out if up-to-date
_ other import library changes
_ it's actually 'add library' not 'import' in this case
_ probably need a way to *remove* the libraries too
_ get contributed libraries working?
_ refactor library imports in p5
_ properly refactor rebuildLibraryList() and the isCompatible() code
_ which is currently only found in ExampleContribution, but should be
_ implemented in a more general way for the other contribs
_ clean up the static stuff since it's not just Examples
_ Library.discover(File) is static and expects .jar files
_ even once that's fixed, need to make sure js libs don't show up w/ Java
_ meaning that there needs to be other ironing in there
_ make it possible for the main class to be something besides the default name
_ want to use sketch.js (this is a fine restriction)
_ how difficult to have modes determine whether a sketch is a sketch?
_ so that the main sketch class doesn't have to follow a naming convention
_ Mode.rebuildSketchbookTree() handles creation of the sketchbook menu
_ which calls Base.addSketches() to do the actual adding
_ would need some means of specifying what the 'main' file is
_ at least with p5js we could provisionally just use sketch.js?
_ mode option for showing html and css or not
_ might be nice to hide these for beginners who will never modify them
_ is it time to add Mode preferences?
_ other supported types from old/offline p5js editor
_ txt, html, css, js, json, scss, xml, csv, less
_ include: html, css, js, json, scss, less
_ exclude: xml, txt, csv (like to be in data folder)
_ add basic syntax highlighting for css
. . .
roll the version/revision numbers in mode.properties
# update the release in mode.properties (it'll match the rev number here)
git tag -a release-1.0 -m '1.0 final'
git tag -a v1.0.1 -m 'version 1.0.1'
git tag -a v1.0.2 -m 'version 1.0.2'
git tag -a v1.0.3 -m 'version 1.0.3'
git tag -a v1.0.4 -m 'version 1.0.4'
git tag -a v1.1 -m 'version 1.1'
git tag -a v1.1.1 -m 'version 1.1.1'
git tag -a v1.2 -m 'version 1.2'
git tag -a v1.2.1 -m 'version 1.2.1'
git tag -a v1.2.2 -m 'version 1.2.2'
git push origin --tags
# delete the previous 'latest'
git tag -d latest
git push origin :refs/tags/latest
# create new 'latest' tag with the current state of the repo
git tag -f -a latest -m 'version 1.2.2'
# actually update things
git push -f --tags
ant dist
then upload dist/p5jsMode.zip and dist/p5jsMode.txt to the 'latest' tag
and name/put some info about the release into the 1.2.2 tag