This thread is more about editing layers and not about modify Squeekboard entirely. And some of your wishes are things that I think will never be supported with Squeekboard and need a totally different solution. Squeekbaord has predefined keys an cannot simulate everything. This may gets better if shortcuts would be implemented (this way we could implement up + left arrow to diagonal up-left arrow or even up-up-left).
Best thing would be if games support it by themselves. An additional keyboard is just a poor fix for unsupported inputs. However, in some cases it makes sense.
@ 5.) I created a new thread for that specific topic. Even if it could be handled in this thread, it’s better to make an own, because it’s for a very specific layout that will need a lot of work.
Very nice and posts. I have done the same with the default keyboard layout not quite being enough for me.
Here’s what I’ve got so far. It’s a bit more of a normal keyboard, with the symbol layer customised for writing Te Reo Māori (the New Zealand Native Language) and including symbols I use often. The keys are definitely on the small size, but seem to be big enough to minimise errors. I also made layouts for the Workman layout Workman-P in terminal as I have been wanting to switch to the layout for ages and figure this would be a good way to do it.
Todos:
fix the colouring on the keys (missing the return blue)
I worked on default terminal for Germany. I want to upstream it one day, but the whole process looks so complicated (never did a MR before nor compiled something from git) and I have not much time to learn it actually. However, for people who want the file right now, here it is:
@dos:
I run again into the issue where Modifiers get reset and tried to look deeper into the issue. So I found your bug report one day after you reported it - luckily was not looking before. That 8 bit border makes totally sense to me. But modifiers are not totally broken - if I copy a text and want to paste with Ctrl + v, I will write first time v and if I repeat it, it will paste what I copied. I’m just not allowed to do something else in between (like pushing backspace to remove the written V letter). That also works with nearly every other modifier and combination (except such as Ctrl+x, because marked text becomes letter x and so nothing to copy anymore).
Hopefully it get fixed soon, because my widescreen and terminal keyboard are modifier broken right now.
The cool thing with Squeekboard → we can add special use case keyboards. It speeds up things a lot. The padding-button typed padding: ;, so I just need to fill the values. I made this post to show you alternative ways to use Squeekboard.
Initial Release of my custom layout is here. As you can see above, it is a German layout, but you can customize it. If you want, I will also add your customized languages, but only if they match this style more or less. Here is a screenshot of the current state.
There is a file for 100%/200% screen scale, but also for 125%, 150% and 175%. I did the math that they fit perfectly into portrait view and wont support other scales. Landscape needs an update before releasing it.
You also can decide between the color version you see above, but you also can use a color version that matches the default Squeekboard color. Currently I just have one color-theme. If you have any wishes, I will create some more (or upload your creations).
For default color you can decide if you want a css-fix for font size etc or if you stay default without any css-file. It may looks less good, but it should be usable in any case.
Also, if you find any bugs, please let me know (in best case with screenshot).
Installation etc is described on README-file. There is only a manual installation right now and I have not much experience in creating scripts yet. I’m not sure if or when I will create such. So if someone wants to create it (@Emma? *asking kindly*), I would be happy.
I’m a bit confused. When I log-out I also have no access, so it is something with authorization. But the repository is marked as “public”. I’m not sure what I’m doing wrong.
For me one of the main reasons was the e.V. from Germany (eingetragener Verein aka registered association) behind. It’s much more trustworthy than Microsoft or even some smaller companies.
Another reason is the accessibility. Purism makes it not easy to create and activate an account and after I tried it, it got activated while I was not at home and 2 days later it was already deactivated, while the “send me a code to reactivate” never sent a code. I was tired by this and stopped trying. I understand that they want to protect their services, but I also don’t want to feel like begging for access.
And last but not least, user0 who didn’t accept any of the other git repositories accept this one. That can be interpreted as plus.
Thanks. All good to know. I already didn’t have a good feeling about what pain might be involved in opening a Purism source/issue reporting account. Now I’m even more aprehensive.
I have been researching the pros/cons of opening a Codeberg account and the information is readily available. What I was really asking above was the nature of the missing page problem, but it looks like FranklyFlawless has answered with what seems most likely.
I must be conflating Codeberg with one of its alternatives because I have a memory of a review article that touted lack of javascript, or maybe it was less javascript than others. I used to be able to count the sites I allow javascript on one hand, but I must be over a dozen now.
Well as previously discussed by the Purism community a while back, SourceHut has no JavaScript requirements, and most of its functions do not need a registered account.
I’ve forgotten that discussion, if I ever read it, but that page was referenced in one of the reviews I read yesterday. That was the source of my “no or little” javascript memory.
It looks very interesting. I’ll consider opening an account.
I need some clarification on some of your instructions:
Is squeekboard_colors.css used for Custom or Default colors, or both?
Is pink-glass.css used instead or in addition to squeekboard_colors.css?
What is the proper order of all css files to be used?
What should the gtk.css file look like for both Custom and Default color options?
Javascript is not absolutely required for using Codeberg. Here are the only features I’ve noticed that require javascript:
disable email subscriptions
delete a tag
automatically generate License and Readme files when creating repo
change the locations of “merge into” and “pull from” when issuing a pull request
I easily created a repo and manually created all files within it, all without having to enable javascript.
There are some buttons that are hidden behind a javascript button; you can access the actual buttons by simply switching from “Basic Page Style” to “No Style” using the “View” => “Page Style” option in the Menubar of your browser.
To anyone considering joining Codeberg, I recommend starting here:
