Before moving too far forward with the Extension API and marketplace, we need to decide what type of environment will be used to run extensions.

~~JavaScript Core, https://developer.apple.com/documentation/javascriptcore, is an option. It does not support ESM, but as some have mentioned, there are ways to work around these limitations using build tools.~~

Initially, a Swift extension API is being developed.

However, we ultimately plan to take an approach similar to Raycast that was described by mathieudutour here, https://github.com/CodeEditApp/CodeEdit/issues/180#issuecomment-1090153684. The architecture involves using node and communicating with the CodeEdit application using JSON-RPC. A react-reconciler will allow extensions to create a custom UI with React components.

Thank you to everyone who contributed to the conversation! Please feel free to continue to add feedback and/or suggestions.

Description

Fix the remaining UI styling issues per #638 and based on the original design prototype of CodeEdit. (also fix a little formatting issue)

This PR is still a WIP as the styling of changed files List has animation glitches. Glitches detail is in the comment here and here.

Related Issue

• #637
• #638

Checklist

• [x] I read and understood the contributing guide as well as the code of conduct
• [ ] My changes generate no new warnings
• [ ] My code builds and runs on my machine
• [ ] I documented my code
• [ ] Review requested

Screenshots

To be added.

Ability to remove items from the 'recent' list. (see #246)

Releated Issue

#246

Checklist (for drafts):

• [x] I read and understood the contributing guide as well as the code of conduct
• [x] My changes generate no new warnings
• [x] My code builds and runs on my machine
• [ ] Review requested

Screenshots (if appropriate):

Note.

I don't know how to add it to the MacOS menu bar

Description

• Optimize the layout and details to better follow the design prototype of CodeEdit (e.g. divider style, background color, and more).
• Make tab interactions feel similar with Xcode by optimizing animations, adjust hover effects, etc.
• [Moved to the future] Fix the hotkey conflict issue (Command-W is not working properly to close tab).
  • This issue seems a bit complicated and out of scope for this PR. So I decided to move it to a separate issue and work with others to resolve it.

Related Issue

• #49

Checklist

• [x] Tab Bar Style Fine-tuning.
• [x] Optimizing animations and interactions.
• [x] ~~Fix the close-tab hotkey issue.~~ (Moved to #473)
• [x] Add tab bar style preference.

• [x] I read and understood the contributing guide as well as the code of conduct
• [x] My changes generate no new warnings
• [x] My code builds and runs on my machine
• [x] I documented my code
• [x] Review requested

Screenshots

The general styling will be based on the design of Xcode and the initial design concept of CodeEdit.

Xcode style

Native style

Interaction Demo

https://user-images.githubusercontent.com/36816148/163754487-a73f7b55-bd62-4407-a918-0efb63ff3e7e.mov

References

Here is the animations and interactions of Tab Bar on Xcode.

https://user-images.githubusercontent.com/36816148/163563123-b77af785-c8f8-42bf-8dc1-2926a17913c1.mov

Description

This patch adds functionality for cloning a repository from the welcome view. Feel free to point out obvious mistakes as I am taking first touches with Swift world at the same time.

Related Issue

• closes #230

Checklist (for drafts):

• [x] UI might need some work
• [x] I read and understood the contributing guide as well as the code of conduct
• [x] My changes generate no new warnings
• [x] My code builds and runs on my machine
• [x] Review requested

Screenshots (if appropriate):

Description

Changes to Preferences

This PR implements a complete redesign of the Preferences window, coupled with a new way to persist settings. Instead of using UserDefaults settings are now saved to ~/.codeedit/preferences.json. This way one can easily export or import settings manually. It's also possible to sync it across devices using Dotfiles Workflows.

The main focus of the redesign is the window itself with a new toolbar selector on top (just like Xcode) to navigate to the different sections. Further the Themes section is implemented how it was discussed in #286. The thumbnails of the themes in the sidebar are adaptive to color changes.

The Editor itself will not adapt to theme changes yet since its implementation is yet work-in-progress Therefore the Preview tab in the Theme section is not yet implemented.

Theme-specific changes

Themes are saved in ~/.codeedit/themes/ as a ThemeName.json file. A default theme is provided bundled within the app and gets saved the first time preferences are opened. A template for themes can be found here.

When a theme gets edited, changes get saved in ~/.codeedit/preferences.json under "theme" > "overrides" > "theme_name". When a theme gets loaded it will override the values found there.

When a theme was reset, the override properties of this theme get deleted in the preferences.json file.

When a theme was gets deleted, the original theme_name.json file in ~/.codeedit/themes/ is deleted.

TODOs

• [x] Preferences UI overhaul
• [x] Selectable themes.
• [x] Use preferences.json instead of UserDefaults for persisting settings.
• [x] Don't overwrite themes when changing colors. Use preferences.jsons overrides instead.
• [x] Reset themes (right click > Reset Theme)
• [x] Implement remaining terminal colors.
• [x] Delete themes.
• [x] Enable list view in themes sidebar.
• [x] Font selector for editor. (not yet functional since new Editor is not implemented yet)
• [x] Documentation. (partly done) ~- [ ] Duplicate themes.~ (will be implemented later) ~- [ ] Sort themes by category: Bundled, Community, Custom.~ (will be implemented later)

Releated Issue

• #34
• #200
• #286
• #344

Checklist

• [x] I read and understood the contributing guide as well as the code of conduct
• [x] My changes generate no new warnings
• [x] My code builds and runs on my machine
• [x] Review requested

Screenshots

Editor Theme Settings / Icon Mode

Terminal Theme Settings / List Mode

Changing Colors -> Previews

https://user-images.githubusercontent.com/9460130/161055774-24ba70bb-ddf7-4748-b4e8-e958a2b6bc9e.mov

Terminal Tab

Text Editing Tab

Folder structure of ~/.codeedit/

~/.codeedit/preferences.json

https://user-images.githubusercontent.com/9460130/161261283-d0c56df2-bad1-4adf-bab7-aebbce9eb0f1.mov

Reset/Delete Theme

Description

Bugs Fixed

1. The About screen had an issue where the window titlebar had a wrong background:

https://github.com/CodeEditApp/CodeEdit/blob/e85ea0541c979b97ea447ecd4960d1a3f3b933de/CodeEditModules/Modules/About/src/AboutView.swift#L60-L66

This PR removes these lines of code and other associated lines, fixing the about screen (tested on macOS 12.3.1 both light and dark mode):

2. Very minor change from (c) to the copyright unicode logo.

Features Added

1. Added an Acknowledgements screen (Closes #340):

This PR adds a build phase (that fails silently in case of errors) that copies the generated Package.resolved file from CodeEdit.xcworkspace/xcshareddata/swiftpm/Package.resolved into the Project directory. This file has been added into the project as a reference without copying the file, as a result it'll always be up to date.

The acknowledgements screen automatically parses this Package.resolved file, therefore needing no separate database file or dependencies, and always staying up to date as the dependencies are updated.

Includes a simple Regex check to exclude first-party dependencies (i.e. CodeEdit*). Only third party dependencies are parsed and included in the Acknowledgements window, and alphabetical order is maintained.

Screenshots

2. This PR also updates the link to the License agreement and opens a browser pointing to the license file in this repo.

3. This PR also cleans up the text in the About window— moving and splitting a single Text() with multiple \n into separate Text()

4. Adds hover animations to the git commit hash in the about window:

Screenshots

5. Makes the version string and the commit hash selectable (and therefore copyable).

Related Issue

Adding Acknowledgement Screen:

• #340

Fixes some bugs related to About Screen PR:

• #378

Checklist

• [x] I read and understood the contributing guide as well as the code of conduct
• [x] My changes generate no new warnings
• [x] My code builds and runs on my machine
• [ ] Review requested - Will request for a review after Acknowledgements screen is completed.

Description

Using models for issues, I think it would be a good thing. Perhaps you should create two new tags(label) with icons if you want to leave the icons. I believe that the use of icons can give immediate feedback to understand what it is talking about.

Checklist (for drafts):

• [x] I read and understood the contributing guide as well as the code of conduct
• [x] My changes generate no new warnings
• [x] My code builds and runs on my machine
• [x] Review requested

Screenshots (if appropriate):

How do we want to manage preferences? Let's get a discussion going so we can arrive to the best solution for our users.

Do we want to sync via iCloud between devices?

Can project specific settings override global settings?

How do we want to display these settings?

Option A

Option B

Option C

Description

Added branch checkout modal which shows after cloning from the welcome view

Related Issue

Checklist

• [x] I read and understood the contributing guide as well as the code of conduct
• [x] My changes generate no new warnings
• [x] My code builds and runs on my machine
• [x] I documented my code
• [x] Review requested

Screenshots

Description

• [x] Fixed Duplicate File Functionality
• [x] Fixed SwiftLint Error

This is a duplicate of PR #730 by @Blackhole1123. I just carried on with the work. Fixed some merge conflicts and did some finishing touches.

Some changes had to be made from the initial requirements in #727. Initial requirement wanted the duplicate folder name current_name copy.<extension>. but I was coming across runtime errors when trying to include the space. So the new file are now prefixed with "_" e.g. current_name_copy.<extension>

Still some issues to resolved:

• [ ] ~~Upon create duplicate file receive following error Thread 1: EXC_BAD_ACCESS (code=1, address=0x70)(Possibly a new issue)~~
• [x] New duplicate is created but when renaming it, the file above is selected.
• [ ] ~~Go to rename file automatically when duplicate file. As per requirement~~

Related Issue

• #727

Checklist

• [x] I read and understood the contributing guide as well as the code of conduct
• [x] My changes generate no new warnings
• [x] My code builds and runs on my machine
• [x] Review requested

Screenshots

https://user-images.githubusercontent.com/80204376/188239240-840d7826-56e4-4b83-af2e-136c90a95f59.mov

Description

All text is lost when saving as Plain Text File.

To Reproduce

1. open new CodeEdit window
2. type some text
3. save as Plain Text File

The file is saved but is empty - no text is found. The giving file name is used and the file created at the selected location.

Expected behavior

Data should not be lost on save and a Plain Text File should be created with all the text that was there prior to saving.

Version information

CodeEdit: 1.0 (0) macOS: 13.1

Additional context

No response

Is your feature request related to a problem? Please describe.

Additional click into new editor window needed to start typing

Describe the solution you'd like

Clicking Create new file opens a new window, but cursor is not active. To start typing, a click into the window is needed. To avoid this it would be preferable if new windows opened with active cursor.

Also clicking into the window is not sufficient to trigger an active cursor. in CodeEdit the first line has to be clicked. This complicates getting started on a document even more.

Describe alternatives you've considered

I have nothing to add to this field.

Additional context

My use case is using CodeEdit mostly as text editor, so it may deviate from what developers need. But I was surprised about both behaviors:

• no active cursor on new document
• clicking in window does not enable active cursor

macOS 13.1 CodeEdit 1.0. (1)

Is your feature request related to a problem? Please describe.

No response

Describe the solution you'd like

After clicking File -> New to create a file, add an option to save it as a Swift file format

Describe alternatives you've considered

Save the corresponding file format according to the file extension name edited by the user

Additional context

.

Updates build number and pushes changes to main after a push to main. The pre-release action needs to be run manually.

To update the build number we can use Apple's own avgtool which will automatically change the build number in all targets.

I made the change to only make the pre-release run manually because the changes avgtool makes need to be committed and pushed first.

Later on when deploying releases with an actual version number changed based on tags we could easily create another action workflow for that where we set the version number to the tag value.

Any thoughts on this?

Resources

• https://medium.com/xcblog/agvtool-automating-ios-build-and-version-numbers-454cab6f1bbe
• https://developer.apple.com/library/archive/qa/qa1827/_index.html

Closes #890

Is your feature request related to a problem? Please describe.

No response

Describe the solution you'd like

The code editor to take full advantage of macbook's features, being made for mac in mind. Having the macbook pro touch bars have a "run" and "debug" button would be amazing. Maybe it could even show open tabs of the editor.

Describe alternatives you've considered

The touchbar COULD solely be black and not in use, but I feel that would be a waste.

Additional context

There could also be customization for the user, allowing the user to choose what they want on their touchbar based on pre-defined presets.

Description

Cursor remains an arrow when hovering over editor.

To Reproduce

Hover over the editor.

Expected behavior

When hovering over editor, cursor should change to an I-beam to indicate editable text.