eessppeelllloo/processing4
1
0
Fork 0
mirror of https://github.com/processing/processing4.git synced 2026-02-13 10:30:44 +01:00
Code Issues Packages Projects Releases Wiki Activity

a friendly reminder

Browse Source
This commit is contained in:
Manindra Moharana
2013-06-19 00:55:31 +05:30
parent 8a00d5a774
commit dec4c58633
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
pdex/Todo, GSoC 2013.txt
View File

@@ -1,6 +1,6 @@
TODO List for Experimental Mode Plus- GSOC 2013
This would also be a break down of my thought process and ideas as I tackle various tasks.
This would also be a break down of my thought process and ideas as I tackle various tasks. Also lines are fairly long. Make sure you turn on word wrap. ;)
Manindra Moharana (me@mkmoharana.com)
@@ -34,7 +34,7 @@ First major hurdle is offset mapping
x for the above, I've decide to first implement a sketch outline like feature, which would highlight an AST element precisely in the pde code. This would ensure I've got the mapping working properly. And may lead to a future feature.
* This is precise upto a certain line. Once on a line, pde stuff have to be taken into consideration.
x Edge case - multiple staetments in a single line
* PDE specific enhancements will also have to be tackled like int(), # literals.
* PDE specific enhancements will also have to be tackled like int(), # literals. Although after being able to precisely locate ast nodes in a single line(with multiple statements per line), it seems this problem might not occur at all! Need to examine test cases further.
Refactoring would work only when code is compiler error free. I plan to do a find replace type op on the compile ready code.
1. First identify the declaration of the variable in the AST.