Repository navigation
✨ iPadOS #1443
Description
Activity
This will not happen anytime soon, if it happens at all. Our first priority is getting a proper CodeEdit version for macOS, which is not done by a long shot.
To go into more detail, the CodeEdit codebase makes a lot of use of macOS API's. Another things is that CodeEdit will lean heavily on extensions and those will likely not be available on iPad, due to Apple very strict policies for extensions.
So if it will ever happen, a new app will have to be build, that may reuse some of CodeEdit's packages, like the TextView (provided the API's that it uses are available on iPadOS).
Currently iPadOS is still a weak OS to develop on. It's too locked down, there is no terminal shell that can interact with a file system. Development build tools are barely available, so only scripting languages work. An option to fix that is to make it cloud based, but that is a lot of work and then it won't be free to use, because we will have server costs.
Never say never, but as @matthijseikelenboom said, our priority is first with macOS.
That said, this is a community driven project, so if you or others want to take on this effort, anyone is more than welcome to however the focus will be on core features to reach v1.
- locked and limited conversation to collaborators
on Oct 10, 2023
Description
As iPads and iPadOS gets more capable, I imagine many users would like an iPadOS version of the app. Not fully featured, but optimized for mobile. As a developer, I think this would be great. As a user, I think that updates could be pushed to projects while developers are traveling without their Mac.
Alternatives Considered
Maybe like how Apple did Swift Playgrounds. As a stripped down version of Xcode
Additional Context
No response
Screenshots
No response