-
-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Customization options #283
Conversation
I fixed the typing errors in the code I've written. Did I break something in the build process? |
Sorry I've been a bit busy with life and work.. I'll take a look this weekend and help if I can. |
Hey! I tried to check out this branch but I get a build error when running
I'm not so sure what to do to fix it.
It looks like the build error was introduced in commit: 6f76118 |
Yes I remember running a command that might have updated packages. The error has to do with something unrelated to the changes: |
This fixes some build errors related to an unwanted typescript package upgrade
@Bubobubobubobubo @tmhglnd yes, apparently a lot of packages were upgraded automatically at some point, including typescript, which causes that error. I reverted the changes on package-lock.json and re-installed the dependencies, and it's building again. Will look into that build problem later in another issue... This looks great! I'm going to make a few more edits if you don't mind @Bubobubobubobubo
|
Thank you for taking a look! Sorry about the auto-upgrade mishap. About customization, we could save a single object in localStorage to facilitate passing the configuration around in different components. I wasn't sure how localStorage was handled so I.. did nothing 😄. I can take a look and test if needed for the following commits :) |
You might be able to push to this branch by adding the repo it is based on as a remote. Not a Git wizard myself 🥹 |
I would need permission for that, now I get this error: |
I made a pull request: Bubobubobubobubo#3 Some extra things I updated:
I Also noticed that the names do show up when you hover the mouse on the little circle above the cursor line. So I guess they are still there but it is indeed some css customization that got lost in the process of adding custom themes. |
Some fixes and ideas added
@tmhglnd: I have merged your changes into the branch. |
Just a word of caution from personal experience: handling keyboard shortcuts can be quite difficult if you start to take into account that there will be multiple editing modes now. Some keyboard shortcuts will simply break because of the Vim Mode. Generally speaking, I'm not a big fan of these. A good command prompt can be tremendously better, especially since you only need to remember only one keybinding to summon it. On another topic, I think that we are at a good point to start to get a bit creative with customization options. What about adding sliders for |
Created a new pull request here Bubobubobubobubo#4 With fixes for the name badges and the unwanted dotted |
Also true, I guess we need to test them more. I performed a couple or days ago and had some issues with some shortcuts, for example, at one point, I tried to comment a line with CMD+/ but mistyped and pressed CMD+. and silenced everything 😨 same thing with Ctrl+Enter in Mac, which executes all the code instead of the current block.
Yes! That'd be great. We could make use of a Settings Dialog and throw everything in there 😄 I'd tackle this in a separate PR though |
Hello, bumping this PR. What can be done to get it merged in the near future? |
Hey! Let me take a look at the to-do list I had, I don't quite remember if it's up to date, maybe some of these things can be done later and we can merge this now... |
Ok I think it's ready! @Bubobubobubobubo @tmhglnd Do you want to take a last look? Just in case you feel something is missing... These were my last changes:
The only thing that I didn't restored was the shortcuts for toggling Line numbers and Word wrapping, because I wasn't sure what was the best way to handle it now that it is a prop set in parent components and not handled in the editor itself. But I figured this isn't that bad now that settings are saved automatically, you just have to toggle them once if you prefer :) |
I don't have much time to program currently and I trust your judgment 🙏. IMO, the essential is to get something merged that we can gradually improve on. I'm sure more CSS hacks will find their way in in due time. I'll probably do more commits in the upcoming months when time will be a resource again. |
Alright, I'll merge it for now. As you mentioned, we can still make adjustments later. Thanks to both of you for your hard work and suggestions, and a shoutout to @diegodorado for motivating these customization improvements with the Vim mode! 😊 |
I think I added this to reduce the font-size differences between the fonts. For me it looked good I remember, but if it gives issues on your end then we leave it out. I haven't had a look at it in a while. In any case I think all looks good so far! I don't mind not having the shortkeys for wrapping/line-numbers, the setting in the menu are fine. |
I also notice now that selection highlighting is difficult to see when the selection is just on 1 line. When switching to multiple lines it becomes better visible. |
oh nice! |
This PR is rather large and unfocused so I will keep it as a draft for now. Some help is necessary to review the code in order to tame the remaining ugly bits. I don't know much about React and my frontend skills are shallow. The PR is adding some much needed customization options to Flok:
It also refactors the keybinding based CodeMirror extension system that Flok was using. Now, options are accessed through the menu:
EDIT: well, lots of typing errors to fix.