p5.js 1.0 roadmap

[lmccart]

I've just posted a first draft of a roadmap to 1.0 in the developer_docs folder.

This document is a list of possible features, improvements, and maintenance items for a future 1.0 version of p5.js. The first draft was created by the working group at UCLA Design Media Arts and is put out for your feedback. This is a working draft that may be updated and will be significantly revised at the p5.js Contributor’s Conference, schedule for August 2019. Our goal is to release p5.js 1.0 by the end of 2019.

With the exception of ES6 migration, the tasks here are not ordered by priority. The milestones on github is where we prioritize tasks for releases and track progress.

Feedback is welcome in this issue thread.

[unjust]

If "Phase 3 Codebase" is implementing the p5 lib with es6 features - I'm thinking this should be started earlier so we can use documentation and examples against the new codebase.

Things can be done a bit in parallel of course - we don't need to wait to document until the whole codebase is ready, but we should be upgrading the codebase and create the documentation to reflect what we know we are changing. I'm new to the project so just leaving my 2 cents but will follow whatever decision.

Also I'd really like to contribute to the transition :-)

[lmccart]

I agree @unjust. The first phase consists of just updating the current examples. I imagine most of the ES6 port will not change that much of the user facing API. For the parts that do change, we'll update the documentation and examples at the same time to reflect these changes, as you suggest.

[chrisorban]

Hi @lmccart can you designate the iPad arrow keys as part of the 0.9.0 milestones? It's now the second oldest Pull request I don't think it would take a ton of work to get it merged into the main branch. It would be a big help to the K-12 effort. There are a surprising number of one-to-one iPad schools and Ohio State now gives iPads to all our incoming freshmen.

#3286

[Kevin-Hamilton]

@chrisorban FYI it looks like this UIKit/Webkit bug with iPad external keyboards is going to be fixed in iPadOS 13, see:
https://bugs.webkit.org/show_bug.cgi?id=149054
microsoft/monaco-editor#293

[lmccart]

Hi @chrisorban thank you for your work on this. We're not able to support library modifications to support external third-party peripherals because it gets too tricky to determine which ones to add, and this is really a bug with Apple's keyboard itself. We'd suggest making your own library (as I think you have done) and including it in student projects to add the desired modifications.

However, ads @Kevin-Hamilton mentions, it does luckily look like this issue will be fixed in the iOS 13.

[chrisorban]

Hi @lmccart I will be trying out iOS 13 as soon as I can to see if the changes fix the issue with iPad keyboards. My understanding is that the public beta of iOS 13 will come out next month (i.e. July 2019). Thanks again @Kevin-Hamilton for pointing this out. In the meantime, that's fine to close the iPad keyboard pull request. After iOS 13 comes out we can revisit whether we need to add a library for the keyboard.