RapidWeaver 6 is a big leap forward and it will allow a lot of new magic stuff to be done. When it comes to third-party plugins this release requires new version of plugins to be released. Existing plugins will not work with RapidWeaver 6. But there will be a migration path for plugins so that existing plugins for RapidWeaver 5 will be migrated over to RapidWeaver 6 upon first launch, if the old plugins supports that.

I have been working for some time to update my plugins for RapidWeaver 6 and here is my status:

WP-Blog is almost ready. A new version for RapidWeaver 5 that supports migration will be available before the release of RapidWeaver 6.

@stash is currently work in progress. I will do my best to be ready before the release of RapidWeaver 6. But I cannot guarantee that it will be ready for the launch of RapidWeaver 6.

FlexibleList and High-Light have not yet been updated and I have still not decided if they will be updated.

So please stay tuned and watch this blog and my Twitter account for latest news about my plugins.

When I was working on a future release of FlexibleList I stumbled upon a bug. To be more precise it was a memoryleak. Since this future version is a long way from beeing finished and I don’t want my software out there for a long time with known bugs I have prepared…

I had some fun a while back playing with FlexibleList and created some new styles, partly on user request. But I never got around to actually adding them to my site until today. They are quite simple but still useful so they are now available on the example page for you to download. They all involve displaying images with a description and works without any special tricks to add the image to FlexibleList.(mer…)

A recent issue arose that pointed out a bug in FlexibleList. It was found when I released a small update to the Tabifier style for FlexibleList and I got a report that the style was not OK. After looking into it I quickly discovered that the style was in fact OK but instead it was a bug in the all so important ”Import style” option in FlexibleList.

The ”Tabifier” example style for FlexibleList has been updated with a small CSS fix. It fixes an issue with images in items that have been ”aligned” in RW which could be breaking out of the tabbed container.

[lang_en]It’s been a while since I posted something about FlexibleList. It didn’t even get mentioned around the release of RapidWeaver 4.0 because FlexibleList worked just fine without needing an update. So I thought, why don’t I release a new version now instead

[lang_en]I have uploaded two new example styles for FlexibleList today. Well, one was kind of old (Odd/Even) it’s just that I had forgotten to add it as a downloadable file.

The really new example is Two Columns which shows you how to basically create a two column table. But it’s not a real HTML table. All is done with CSS and you can adjust the width of the leftmost column in the CSS.

It’s time for a major update to FlexibleList today that extends it’s flexibility even further. You are now able to create styles complete with javascript and images, and put information directly in the page header etc.

The custom variables are now supported in almost every editable field in FlexibleList. There are still some limitations but if a variable isn’t supported it will not be converted so your should be able to easily see if it worked or not.

The UI has also seen it’s share of evolution, although it may not always be so obvious. If you feel that the item list or the content fields are too small when you are editing them you can now collapse the part of the splitview that you don’t want to see. Just drag the splitter towards the end that you want to hide and it will go away until you drag it back. FlexibleList also has full support for drag&drop between projects and copy&paste of items.

Just to get you started with the new styles I have bundled two updated styles with FlexibleList, Smooth Scroll and Tabifier. These styles have been updated and are now fully standalone so you just have to apply the styles to your page and they will work (unless there are some javascript conflict with other scripts on your page/theme). There is no longer any need to manually add the needed javascripts to the FlexibleList page.

If you want to now more about what has changed go and read the changelog. And be sure to read the user manual as it has been updated with this release.

FlexibleList continues to be donationware and requires RapidWeaver 3.5.x and OS X 10.3.9.

If you have updated Blocks to v3.1.1 you should notice that your FlexibleList pages can now be used in pageblocks. There is unfortunately one thing that doesn’t play so nice with Blocks but it’s out of my control to fix it so check the user manual for a workaround.