I would love to start talking about the lazy loading again that was added into RW7.2. Users are complaining about things being slower using their projects and some key features in Stacks have become less reliable because of it.
Most users do not have huge large projects that take many minutes to open. To these users, working with their project files feels slower because moving between pages takes longer, open a link dialog could potentially take a long time since all of the pages need to be loaded. I feel that this lazy load feature has hurt more users than it has improved.
The partials feature in Stacks was a huge game changing feature. It allows users to quickly change stacks across many pages. This has become unreliable now with the lazy loading since not all pages that contain a partial are loaded. Users will now change a partial expecting it to work as it did in RW7.1. However, when they publish, not all of their changes actually get published. This is even worse because it makes RapidWeaver and Stack unpredictable. When this happens users will get frustrated and lose trust in the product. None of us want that.
I could be wrong but I am pretty sure that there is nothing that @isaiah can do with this. Its a limitation in the RW API now. The ball is in Realmac’s court. Any serious RapidWeaver user will be using Stacks. When RapidWeaver breaks a major feature of Stacks, it hurts all of us.
I would love to see 2 things happen…
- Have an option to disable this and go back to the way things were. Sometimes the side effects are just too annoying.
- With lazy loading enabled, it would be great if it were true lazy loading, not just on-demand loading. After the first page of a project loads, RapidWeaver should be loading all of the other pages in the project run the background.