We are about to switch to a new forum software. Until then we have removed the registration on this forum.
My name is Jun Shern, I'm a 3rd year Electrical and Electronic Engineering student at Imperial College London. I'm a huge fan of Processing for giving me my start in programming (almost 5 years ago!), and more recently I've been playing around with the fantastic p5.js. I would love to give back to the Processing community with a Google Summer of Code project!
I've tried encouraging my non-coder friends to get started with p5.js, and I found that many people struggle with the initial setup of the HTML and JS files, which puts them off before even getting to touch a single line of p5.js. The solution to this, of course, is the p5.js Web Editor which the team have already done a marvelous job on, but there is still more work to be done!
I've already approached Cassie (sorry, I haven't figured out yet how to find/tag people on this forum) about this, and I have a couple of ideas which I'd love to work on as my GSoC 2017 project. The ideas follow a common theme of improving the workflow and overall coding experience within the p5.js Web Editor, and are divided into SMALL and FEATURE:
I anticipate these fixes to be not too difficult, and I will attempt to tackle these at the beginning of / before the project, to acquaint myself with the current code of the editor and how it all works.
ENHANCEMENTAdd shortcuts for "Search/Replace" (Ctrl+F currently doesn't work in-editor) EDIT: Oh that's so strange, I managed to get the standard Ctrl+F working sometimes but not all the time... Will look into this more!
ENHANCEMENTAdd shortcut for "Select All" (Ctrl+A currently doesn't work in-editor) EDIT: Again the same issue as Ctrl+F, I managed to get the standard Ctrl+A working sometimes but not all the time... Will look into this more!
VISUALCan we change the syntax highlighting colorscheme (especially for dark mode)? Or perhaps give users an option to choose between available colorschemes in the Settings menu.
UIInstead of hiding nav features from unregistered users, could we perhaps fade-out the features and turn them off? This gives new users a better idea of what's available, and we could also implement a hover pop-up "Login to enable this feature"
VISUALFile browser and editor scrollbar colors should be dark when in "Dark" mode
VISUALUI buttons show pop-up of shortcut keys (if available) when hovered
UIOption to hide Preview pane
UICreate a button / shortcut key to "Run in new window". This essentially implements
Nav > Share > Fullscreen. _The above ^ two points are related; I personally much prefer to have a fullscreen editor window to code in, and have my preview in a separate tab and switch between the two. (I'd imagine that most smaller-screen users would prefer this too!)
BUGClick on Preview pane to focus Keyboard (right now all keystrokes sent to editor, doesn’t allow sketch to receive keystrokes?)
I anticipate these to be more difficult to implement, and the specific details of the implementation may evolve depending on priority of issues and available time.
HIGH-PRIORITY Autocompletion & In-Editor Documentation
MID-PRIORITY Improving the Settings menu
LOW-PRIORITY Different "Views"/"Layouts" options (like what CodePen and many other IDEs offer)
I realize that these are quite a large assortment of different things to implement, but based on my own experiences with the editor and what is available in other full-fledged editors, I believe these to be very useful features which will greatly improve the development experience of new and experienced users alike! I am however open to suggestions on other things to work on related to the editor, especially any more high-priority issues I might have missed.
I would be very grateful for any feedback you can give me before I put these ideas into proposal form! :)