Hej!

Kom och häng med oss på Atex Polopoly en kväll. Vi bjuder in till Geek Night, den 22 November 17.30. En kväll fylld av blixttal, både Polopolyrelaterat och helt annat, som vi vill dela med dig.

Geek Night är en fin tradition på kontoret. Vi tar en kväll och delar med oss av erfarenheter och pratar teknik. Den här gången breddar vi inbjudan till alla som vill komma. Vi kommer att prata om hur man använder Clojure i Polopoly, om hur man testar iPad-appar med Cucumber och om erfarenheter kring att köra 300 000 tester om dygnet i moln, både EC2 och hemmabyggda. Bland annat. Kom förbi, lyssna, diskutera och ta en öl och ät lite pizza.

Den 22 November 17.30 i våra lokaler på Alströmergatan 22 i Stockholm. Garanterat tekniskt, garanterat nördigt och garanterat inget säljsnack.

Anmäl dig på http://bit.ly/atexgeeknight så snart du bara kan. Har du frågor, hör av dig till mig på: marcus.frodin@atex.com!

/ Marcus, Produktägare Polopoly

Hi again! I thought I’d follow up last weeks feature rundown with some other cool stuff we’re doing.

Since we, like most developers, spend our days submerged in tooling. Maven, Jenkins, Eclipse, JRebel and tons more. At Polopoly, we try to be dilligent about contributing back fixes to Open source projects we use. You can find patches, bug reports and pull requests from us on everything from Velocity and SolR to jQuery UI and Firefox.

As of a few weeks ago, we’ve started pushing up some of our own stuff on our GitHub account, and since we’d love pull requests, I thought I’d just write about them a bit.

Here you’ll find, amongst others, two Maven plugins to make life easier when dealing with Less CSS and unminified and unconcatenated Javascript. You’ll also find patches we’ve done to Jenkins plugins for Git and EC2 that haven’t made their way back to core yet and a JRebel plugin that allows you to update files on content from JRebel, without having to reimport them by reading them from the file system instead. If you deal a lot with output templates in plugins, it allows you to re-read the velocity files as you go.

And you’ll also find one plugin for Eclipse, pp-eclipse, that contains a life saving feature when you’re dealing with a ton of input templates, ”Open by external id”. Pressing Shift+Alt+P gives you the familiar ”Open Type” dialog, but with content instead. It does this by indexing all the XML in your project, and is in general pretty awesome. It also contains a shortcut to import Content XML quickly, Shift+Alt+X.

As I said, a few very useful tools that we’d love to get your contributions on.

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.