This blog post is written by Marcus Frödin from Atex Polopoly. We at polopolyforum.se is glad to see that Marcus is contributing to the community. More about Marcus later on.

If you’re in any way tapped in to the Atex universe it must’ve been hard to miss the mass of Tablet-related material we’ve been pushing in the last few months. And for good reason! The team has been hard at work creating what I think is an awesomely cool product that finally takes the correct approach to production for tablets.

But one thing that’s a bit of a shame with this tablet craze is that our continuous development of new stuff in Polopoly gets the PR backseat. So I thought I’d change that by just showcasing a bunch of the new features we’ve been releasing in the two developer releases we’ve put out this year: 10.1-DR1 and 10.1-DR2.

What makes me especially proud are the small things we continually add that make Polopoly a nicer place to spend your day, whether you’re a developer or an editor.

Autosave

For example, for DR1, we added autosave. For anyone who’s ever finished a text and gone away lunch only to find that they forgot to click save and everything’s gone — well, no more! As of DR1, all articles are auto saved every few minutes, and every time you switch away from the tab of that article. And if you’re logged out, you’ll find all your old content on your desktop when you log in again. If you already had a previous version saved, you’ll get the option to revert back to that version or to keep working on your saved one. Developers can add this feature to other content by simply adding the parameter <param name=”enableAutosave”>true</param> to the input templates they want to hook up.

Conditional layouts

And for developers, one small thing we’ve added is conditional layouts, via the com.polopoly.cm.app.widget.LayoutCondition interface. By implementing this interface, you can make any layout conditionally visible, depending on whatever you chose, such as permissions. Simply create an input template,

<input-template name="p.Example.it">
<policy>com.polopoly.cm.app.quickcreator.widget.HideWhenUserHasPageLayoutCondition</policy>
</input-template>

And a content that uses this input template,

<content>
<metadata>
<contentid><major>Content</major><externalid>p.Example</externalid></contentid>
<input-template><externalid>p.Example.it</externalid></input-template>
</metadata>
</content>

And you can now refer from it in any layout by adding the idparam layout-condition:

<layout name="xyz" input-template="p.Page">
<idparam name="layout-condition">
<externalid>p.Example</externalid>
</idparam>
</layout>

Ipso presto! This is something we know every project does in some fashion, and it so it felt reasonable to add product support for it.

And of course, these are just two of the many small new features we’ve added – download and check it out.

Vi rekommenderar också:

• Vårstädning – ta bort gamla inputmallar ur ditt källkodsträd
• Polopoly version 9.13.1
• Sommar, sol och version 9.13
• Polopolyversion 9.13.2
• 9.16.1 General Release Notes