Bike 2.0 (Preview 285)

[jessegrosjean]

@doug

I have some custom keybindings to toggle the sidebar and inspector, but they don’t show up in the menu. is this what you want?

@Gorgonzola

OK, might have found it. The key here is to clear the filter, and then Go Back Forward until you end up with a historic filtered state. Here’s what I see with a fresh outline with no Go Back history:

1. Filter outline.
2. Clear filter.
3. Go forward once. You should see outline filtered again with the filter you used in step 1.
4. Clear filter. Filter clears but outline remains filtered.

@jessegrosjean

Actually maybe this isn’t so complex. What if I just move through highlighted text ranges, but if not present in a matched row, then I block select the entire row?

@avi-cenna

For CLI tool, I was thinking of using it from a script or Claude Code, e.g. add an entry to an existing outline, in which case it would potentially be useful not to have the constraint of the file already being open in Bike.

I think these are all addressed in latest release. Let me know!

[doug]

fixed!

[kc1]

@jessegrosjean

Toggle sidebar buttons are out of titlebar, and instead there is a single popup for accessing them and full window and other view features. (Extension commands can also be added). With that in place I cleaned up editor toolbar, removing the zoom Full Window button.

Is there any option to have the toggle sidebar (and other) buttons back in the tool bar? Especially for the sidebar, having it hidden in a dropdown on the other side of the window is a lot of extra work when you’re used to using a mouse to do things.

I can understand some people not wanting toolbar buttons, but I find having selected important ones readily available to be very helpful..

[jessegrosjean]

@kc1

Is there any option to have the toggle sidebar (and other) buttons back in the tool bar? Especially for the sidebar, having it hidden in a dropdown on the other side of the window is a lot of extra work when you’re used to using a mouse to do things.

First, to be clear in Bike’s terminology for these things:

• window titlebar (top of window, also contains window’s title)
• editor toolbar (top of editor, where back/forward buttons are)
• editor status bar (bottom of editor, where word count is)

For now there’s no option in the window titlebar, for directly clicking to show perform command. But you do still have option to include Sidebar/Inspector toggle in editor toolbar or editor status bar.

Ideally I would to allow you to configure commands in these location to be in top level, or in menus, but for 2.0 I expect titlebar will be hard coded to a popup menu, and the other bars hard coded to top level buttons.

[kc1]

Thanks for explaining things about the location of items.

@jessegrosjean

But you do still have option to include Sidebar/Inspector toggle in editor toolbar or editor status bar.

I tried adding it to the sidebar, but it ends up at the opposite side of the window:

@jessegrosjean

Ideally I would to allow you to configure commands in these location to be in top level, or in menus, but for 2.0 I expect titlebar will be hard coded to a popup menu, and the other bars hard coded to top level buttons.

This is honestly really disappointing.

There’s a lot of muscle memory that’s being put aside suddenly here that goes against how I’ve used apps on the Mac for years. Even if it the toggle button in the status bar could show up on the left side, it’s still not the same as most other apps that I use that have sidebars that can toggle.

Again, I can understand having an option for some kind of a minimal UI, but for people like me, established, consistent patterns are way more helpful.

[kc1]

Thanks for explaining things about the location of items.

@jessegrosjean

But you do still have option to include Sidebar/Inspector toggle in editor toolbar or editor status bar.

I tried adding it to the sidebar, but it ends up at the opposite side of the window:

@jessegrosjean

Ideally I would to allow you to configure commands in these location to be in top level, or in menus, but for 2.0 I expect titlebar will be hard coded to a popup menu, and the other bars hard coded to top level buttons.

This is honestly really disappointing.

There’s a lot of muscle memory that’s being put aside suddenly here that goes against how I’ve used apps on the Mac for years. Even if it the toggle button in the status bar could show up on the left side, it’s still not the same as most other apps that I use that have sidebars that can toggle.

Again, I can understand having an option for some kind of a minimal UI, but for people like me, established, consistent patterns are way more helpful.

Edit:

Sorry for reading quickly, I saw that I can put it in the Editor toolbar as well. But it’s still on the wrong side of the window. If the title bar really has to be hard-coded, could it at least have the option to place things in certain places or left/right somehow in the other areas? Ideally, I’d want the option to place it first, before the <> and home buttons.

[jessegrosjean]

@kc1

Again, I can understand having an option for some kind of a minimal UI, but for people like me, established, consistent patterns are way more helpful.

I understand and do expect to add more button position configuration post 2.0. Please do bring it up again if I seem to need reminding.

@kc1

If the title bar really has to be hard-coded, could it at least have the option to place things in certain places or left/right somehow in the other areas? Ideally, I’d want the option to place it first, before the <> and home buttons.

The goal will be to have them all 3 dynamic. Separators, spacers, submenus, etc. Can it get that far? Not sure. But that’s goal.

[kc1]

Thanks! Post-2.0 sounds less ominous than waiting until 3.0.

@jessegrosjean

The goal will be to have them all 3 dynamic. Separators, spacers, submenus, etc. Can it get that far? Not sure. But that’s goal.

With those options, I think I could really like it far more than just having the Apple’s default Customize toolbar options. Looking through the options, it looks way more helpful. So I really do appreciate it.

I think the placement of the sidebar and inspector buttons are what I expect to be most consistent across apps that have them, since toggling them open implies I’m very likely going to move the cursor directly to them afterward. Would it be possible to temporarily hard-code the sidebar button to show up on the left if the user chooses to show it?

[jessegrosjean]

@kc1

Would it be possible to temporarily hard-code the sidebar button to show up on the left if the user chooses to show it

I don’t think that would be easy with current code. The solution is to build more configuration possibilities into the layout and Interface Explorer. I’ll get there, will just be not immediate.