6 ms·
I experimented with this exact same approach earlier this year. It's barely sufficient, because, bluntly, most apps just aren't wired up right. So you end up
by etchalon 23d ago
I experimented with this exact same approach earlier this year.
It's barely sufficient, because, bluntly, most apps just aren't wired up right.
So you end up having to hand code a lot of specific profiles for specific apps to make this work well, and even then, you don't quite get the right level of detail to make it work out.
Will try this app, to see if it improved on my own approach, but man, the hope levels are low.
- Dramatize 23d agoYeah don't get your hope up too much. I need to push through more cleaning up of what's captured. Let me know how it goes, keen for some feedback
- hetsaraiya 23d agoI haven't read about how the Codex Appshots work yet, but this can be used to extract text properly. I guess. How does this idea look to you?
- Dramatize 23d agoAppshots is fine for what it is, but not great for building ambient context about your daily usage/work.
- hetsaraiya 23d agoBut we can clean that extracted text from Appshots. UPDATE: As i just checked it is also using Accessibility API. So i guess we will have access to the same set to data.
- zahlman 23d agoOne of the reasons people like TUIs is because the text is always just right there.
- ShinyLeftPad 23d agoNot if it's rendered on GPU, I guess?
- albert_e 23d agoI hope in near future _that_ layer of abstraction -- looking at a fairly standard application window with minor UI variations and reasoning about what area / labels within the UI mean what (possibly paired with app documentation) -- could probably become a light-weight fine-tuned vision model it itself that can run fully locally.