probablyrobert

6 ms·

1.
by probablyrobert 10mo ago
Shameless shill - I found Tridactyl and Vimium to be frustratingly limited due to the security restrictions imposed on web extensions, so I've been working on https://glide-browser.app/ for a while; It's a fork of
2.
by probablyrobert 1y ago
Thank you! I just implemented the ones I use the most, e.g. diw, but the motions system is still in very early stages and there are lots of motions I haven't implemented yet. I do plan on implementing as many motions as is feasible, bu
3.
by probablyrobert 1y ago
I'm not entirely sure what is going to happen with imports to be honest. My current thinking is that they'll be supported eventually but that imported modules should not have access to glide APIs. For anything that does need to us
4.
by probablyrobert 1y ago
DRM is not possible to support unfortunately: https://glide-browser.app/faq#why-can't-i-play-drm-content Firefox Sync does work! RPC is not currently supported but I agree it would be pretty interesting, tweety[0] was
5.
by probablyrobert 1y ago
Ah not yet sadly - https://github.com/glide-browser/glide/discussions/3 I personally prefer non-smooth scrolling as it feels faster.
6.
by probablyrobert 1y ago
I'm not very familiar with Helix keybindings myself but if there are vim equivalents (and if they're actually implemented, a fair amount of mappings are missing right now) then you should be able to! There's a `motion` excmd
7.
by probablyrobert 1y ago
ah yeah sorry about that, the API docs aren't quite complete yet. I'd recommend just looking at the glide.d.ts[0], it should be pretty readable (I hope). Yes the TS API supports it as well with the `selector` property: ``` glide.h
8.
by probablyrobert 1y ago
oh that is very helpful, thanks for sharing :)
9.
by probablyrobert 1y ago
You can use CSS selectors already! https://glide-browser.app/hints#excmds I've used it to add keymappings so that hints only apply to certain kinds of buttons on a page, e.g. https://github.com/RobertCr
10.
by probablyrobert 1y ago
Oh wow this is very cool, thank you for sharing!!
11.
by probablyrobert 1y ago
You can't configure extensions yet but you can set prefs! https://glide-browser.app/api#glide.prefs.set
12.
by probablyrobert 1y ago
Yes! All standard input elements have vim motions support but fair warning that a lot of the standard motions aren't implemented yet.
13.
by probablyrobert 1y ago
It's implemented as a set of patches + new files for net new files I add myself, then to build it, the firefox source is downloaded and patched automatically - so bumping the underlying firefox version is generally very easy. I'm
14.
by probablyrobert 1y ago
Author here - happy to answer any questions :)
15.
by probablyrobert 1y ago
Currently the easiest way to pull over settings I'm aware of is to use Firefox Sync[0]. I haven't looked into other settings import solutions yet. [0]: https://www.firefox.com/en-GB/features/sync/
16.
Show HN: Glide, an extensible, keyboard-focused web browser(blog.craigie.dev)
207 points by probablyrobert 1y ago|52 comments
17.
by probablyrobert 5y ago
The most obvious way would be to simply annotate the fields, e.g. class Book(MonDoc): title: str = StrField() yearPublished: int = IntField() If this means too much redundant information for you then you could try defining th
18.
by probablyrobert 5y ago
Thanks for the suggestion, I've created an issue to track this as I do agree that `ANY` conveys the operation more clearly. https://github.com/RobertCraigie/prisma-client-py/issues/293
19.
by probablyrobert 5y ago
If you're wanting to automatically generate the Prisma Schema then all you have to do is create the schema file, define the datasource connection and then run `prisma db pull`
20.
by probablyrobert 5y ago
I am not very familiar with EdgeDB but it is quite different to Prisma. EdgeDB is a database while Prisma is a database client. EdgeDB do provide their own clients to interface with the EdgeDB database but with Prisma you can connect to man
21.
by probablyrobert 5y ago
Ah sorry I misread your comment, I thought you were agreeing and saying that filtering by a relational field is also unacceptable DSL. Thank you :)
22.
by probablyrobert 5y ago
I find the relational API very easy and intuitive to work with. What do you not like about it?
23.
by probablyrobert 5y ago
How do you suggest to improve it?
24.
by probablyrobert 5y ago
Unfortunately this is a solo project, however I am in communication with the Prisma team and the core engine that Prisma Python uses is backed by Prisma.
25.
by probablyrobert 5y ago
Yes I had heard about that but due to the nature of Python typing, they can't actually type the query API properly without falling back to Any, negating the benefits of type checking.
26.
by probablyrobert 5y ago
Use whatever works for you! I personally felt the same until I learned of Prisma. The main benefits for me are type checking and autocomplete. Autocomplete is the big one as it lessens the learning curve immensely. You no longer have to sea
27.
by probablyrobert 5y ago
My understanding of SQLModel is that it brings the benefits of both Pydantic and SQLAlchemy. The benefit of merging Pydantic with SQLAlchemy is that you can then use the database models directly in FastAPI route definitions.
28.
by probablyrobert 5y ago
Thank you for sharing! It is much appreciated!
29.
by probablyrobert 5y ago
No need to worry, the current behaviour will be preserved :) The method used to interface with the internal engine will be able to be configured in the schema: https://www.prisma.io/docs/reference/api-reference&#x2
30.
by probablyrobert 5y ago
Yes mapped types is a good example, Pick is also a good example: https://www.typescriptlang.org/docs/handbook/utility-types.h...

More ›