![]() ![]() Scaling up from this app to apps in general to computing overall and now to where we are socially, I assert that the space currently available for app development is boxed in by the limits of the personal contexts that we each have created thus far. One last big thought before stepping down from the soapbox. I’m simply saying I’m aligned with the idea and there’s considerably more west to go. Nor is there an intent to poke the bear, run, and see what happens. I know this opens up a whale of conversations that neither this forum or myself are prepared to take on. There’s no actual boundary to this idea of unification/stanardazation to make computing more fruitful. Many don’t even have the command.Ĭompletely agree and while initially overwhelming to confront, this particular app function siloing extends to many many functions scattered across most all apps. Benefit: Hookmark provides universal commands that work across contexts If there is demand, we’ll provide an option for a global keyboard shortcut. We intend to introduce a keyboard shortcut for these commands, so they each will reduce to But at least it is ballistic / keyboard driven (not requiring mousing around) c (select copy path or use arrow keys.)Īgreed, however, that even this is a lot of interaction. ![]() I imagine that most users would then use the keyboard: That’s how I explained it so people can get understand it, seeing it visually. I’m putting this out not for a fix but rather to point out something I often see from developers and that is that all the actual work needed to evoke commands is frequently not considered. Given this, I don’t see a benefit in using Hookmark’s longer sequence.
0 Comments
Leave a Reply. |