Stacks integration with RW

Given how fundamental Stacks is to RW these days, am I alone in thinking it would be nice to shift all those Stacks controls upstairs into RW’s toolbar? There’s plenty of room.

While we’re at it, is there a keyboard command to show/hide the Stacks Library?

If you go into the Stacks preferences, you can see a list of shortcuts. Grabbing an old screenshot so this may be a bit out of date:

Edit: Forgot that this quick video existed as well.


Because of the plugin architecture of RapidWeaver, this is not possible.

@oldgustav - the RapidWeaver plugin API gives us access to some things and not to others. the toolbar isn’t currently on the list.

i do occasionally break the rules and barge in even where i’m not wanted – but only for pinpoint accurate changes – as rarely as possible – and never for something as mission critical as the entire toolbar. i’d really have to have an API to do that.

but you can put your requests in to @tpbradley and @dan – i’d happily move my buttons up there. keeping an entire custom toolbar (or two or three or four) working through all the iterations of OS and RW hasn’t been super fun – i’d happily scratch that off my to-do list. :smiley:

Thanks for this! How could I have missed it all this time…

That explains it. But how is it that Safari lets certain 3rd party addons appear in its menu bar, eg. Buffer?

It would all look very tidy up there too…

It’s just up to the app to decide how they want to let other developers contribute. It’s not impossible at all.

RW gives me access to a lot of areas, but not everything.

You’d think that in that case, why not just give access to everything? The answer is that it’s a balancing act. The API is how all the plugins communicate with the app. Changes to the API mean that all the plugins break. That hurts everyone, especially the users.

So the app tries not to change the API too much or too quickly (usually not at all – without fair warning – a.k.a. “deprecation”).

Between RW4 and RW8 – about 10 years – the toolbar has changed quite a bit. It’s a key design element of the app. Keeping it out of the API gave the app the freedom to innovate and design without the burden of maintaining compatibility.

So a good API is one that gives some access, but keeps enough out of the API to still innovate quickly.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.