We’re excited to announce that RapidWeaver Elements Beta 3.0.10 is now available
This update has a ton of refinements and new features that add extra polish to Elements. We’ve listed the main headline changes below, but be sure to read the release notes for all the details!
You should find this build noticeably faster at opening projects and switching between pages, and there are more speed and performance improvements on the way
There are also eight new projects for you to explore, and Asterra shows off the new in-editor Three.js preview. It’s pretty wild, and a sign of things to come.
Big one. Hats off to the Elements team! A lot of work has gone into this update. I knew something was cooking— It was so quiet here lately , you could hear a needle drop.
Asterra AI with Image Ripple looks wild. Cant’t wait for more.
Having Three.js render live in the Elements editor has a lot of potential, here’s just a few fun demos we threw together to test it out.
The first project, Asterra is available in the new Projects window of the latest beta. This is just a custom component, but we plan to ship a three.js component that would be more polished and enable some cool features for your website.
Not sure there’s many (or any?) website builders that can do this in the editor
Or is this something that will be addressed in a separate fix?
Apart from that, the feature itself is really great. However, as long as the issue with absolute URLs in the RSS feed isn’t fixed, the feed unfortunately isn’t really usable.
The first thing you say about 3.0.10 is:
“Text Component: Copy and paste now keeps links, formatting, and line breaks”
I can’t get this to work.. If I copy text from RapidWeaver Classic to a Text, or Typography component in Elements 3.0.10 the layout is preserved but not the links. What am I doing wrong?
You’re not doing anything wrong. The 3.0.10 paste that keeps links is the HTML path, from the web or a doc. Classic copy is attributed/RTF, which Elements doesn’t read yet, so you get the layout without the links.
I’m afraid Classic paste doesn’t keep links today. I’ve filed a ticket for that, and we’ll try and get a fix for it into the next build.
@tpbradley
Tom, I’m guessing this one is mostly your work…
I have to say, this is by far the best part of the update for me so far. In my larger projects, I’m actually seeing a performance improvement of around 30–40%.
CPU usage is noticeably lower as well, which means a lot less stress on my fans.
Since you don’t often get the big praise you deserve, a huge thank you from me for this great update. Really nice work!
Thanks, that’s really kind. I’m really glad you’ve noticed the difference! It’s a remarkable improvement over the previous build, and there’s still more to come.
Thanks for your reply Tom Bradley. I’m not sure I understand your first paragraph. Pasting text from Classic into another text app does preserve the links. I write most of my pages in Scrivener and paste them into Classic. That works ok for links and I can successfully paste links back from Classic into Scrivener if I need to. Pasting from Scrivener into Elements does not preserve the links. However I’ve got an app by Alfons Schmid called Notebooks (https://www.notebooksapp.com); pasting from Classic into a formatted page in Notebooks preserves the links that can then be pasted into Elements. So it turns out I’ve found a rather indirect way of getting links from Classic into Elements!
My guess is Notebooks is converting to Markdown or another format before it copies into Elements, which would work. It’s the direct copy from Classic to Elements that isn’t working.
