forked from bootstrapworld/wescheme
-
Notifications
You must be signed in to change notification settings - Fork 0
/
plan.txt
78 lines (38 loc) · 2.57 KB
/
plan.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
Done so far:
Runtime error highlighting
static error highlighting - paren matching
TODO:
Look at selenium!
Compatibility with other browsers (so far only tested on chrome) *this should be tested everyday ideally*
Finish cond
Highlight cond branches, implement cond design error messages from the document
Change error messages to match design error messages
Change the I's, change procedure to function etc.
Implement clicking a highlighted element in the error message to move a cursor to the highlighted error in the source, along with changing the focus of the defintions window to the highlighted error code
Go through error-struct-to-dom.ss and address all major errors
Bug fixes:
1. col undefined, line undefined FIXED
2. else clause error, compile time error FIXED
3. (circle 20 'solid 'rubbish) //rubbish should be a color type. there is no error stating this, in fact nothing appears FIXED
4. change colors to be color-blind friendly, and make the colors cyclic (they go to random now) FIXED
5. (check-expect test expected (img img)(overlay/xy pizza 0 50 salad))
If ahead of schedule:
dimming highlighted colors over time
documentation link (if the error mentions a professional function)
Testing notes:
From the design docs, example 8 is supposed to show a runtime error but a compile time error is present.
------------------------------------------------
EOD Wednesday, July 11
Finish all work regarding highlighting cond branches, and rewording cond error messages. This includes the if statement, and anything really related to cond, such as parenthesis. The specific goal is to mimic the appearance and behavior of the design docs.
//as of monday, very close to completely finished with this
EOD Friday, July 13
Fix any bugs that are found/created throughout the week.
EOD Wednesday, July 18
Go through error-struct-to-dom.ss and address all major errors, implementing their correct error messages. The goal is to expand functionality to include more parts of Scheme/Racket code, as the framework should be created by now.
EOD Friday, July 20
Most major errors should be addressed/implemented by now.
EOD Wednesday, July 25
It is unknown how long it will take to implement clicking a highlighted element in the error message to move a cursor to the highlighted error in the source, along with changing the focus of the defintions window to the highlighted error code. However, it will likely be done by now.
EOD Friday, July 27
In theory, everything works perfectly! =]
In reality, this is time to continue debugging, extensive testing, code review, and corner cases.