Bike 2, requested features

Bike Outliner
1

I’ve been using Bike 2 all day and have really enjoyed it. I’ll be using this as my daily driver for notes & planning my day!

A couple of things I thought were worth sharing:

  1. I specifically miss the Navigation Bar from Bike 1. I feel like with Bike 2, while I appreciate the ability to totally focus on a node & its children, that I feel a bit lost in relation to where this is relative to the root node.
  2. I wish many/all of the app-level Menu commands were available in the Command Palette (i.e. “Hide Sidebar”, etc.).
  3. Since I recently learned about space to toggle strikethrough of a row in block editing mode, I would love support for that in Bike 2! Currently, I get around that via ⌘+shift+-, but the space shortcut is much more ergonomic.
  4. It appears clicking links to rows within the document don’t work correctly.
2 Likes
2

+1 for 1. and 2.

3

Good list, thanks

Navigation bar is still on my list, just haven’t got there yet.

Related things that I’m thinking about:

  1. I don’t love the 1.x navigation UI, and I especially don’t like it when I’m not focused into a branch.
  2. I have no design yet, but I am thinking I might remove the show/hide option, and only show a more prominent bar when focused.
  3. Also I think I want the new Search view to act a bit like focus in. So when you start a search you’ll focus into a new state to perform your search. But you can also focus back out and get your previous state before the search. Seems like that should also be part of navigation bar.

anyway, still thinking, but I do plan navigation bar.

At the moment you can exit to outline mode and type “md” for “mark done”. This was mostly a test case for multi-stroke key sequences. And long term I was hoping to design a VIM style key sequences for outline manipulations that “md” could fit into. I still hope to do that, but won’t be fore 2.0.

All that said, I probably will change back to “space” instead of “md” for the 2.0 release.

And last, maybe you have figured this out already, but you could do this yourself in an extension’s app context with this code:

  bike.keybindings.addKeybindings({
    keymap: 'block-mode',
    keybindings: {
      space: 'bike:toggle-done',
    },
  })
4

Latest preview has changed to using spacebar: Bike 2.0 (Preview 245)

1 Like
5

I would love to see a file format that supports bold/italic/strikethrough font formatting but is more readable (and editable) in a text editor (e.g., on iOS/iPadOS) than the current HTML format. I think I’m likely referring to a form of markdown, but there could be other options.

1 Like
6

So happy to hear the navigation bar is on the list! Thank you.

I agree with all of your considerations/things you’re thinking about.

  • I don’t care for the Navigation Bar to appear when not focused in Bike 1.
  • +1 to only showing it when focused and dropping the option.
  • Search sounds neat! Seems like a nice way to be able to expose filtering.

That said, I have found myself using Bike 1 instead of Bike 2 solely because of the Navigation Bar! I tend to use Bike as both: a scratch pad throughout the day and a place to keep a brain dump of things organized by project. I use focusing on nodes as a way to “zoom in” on only what’s important at the moment. Without the navigation bar, I feel lost. Hence, me using Bike 1 for the time being.

Thanks, Jesse!