Vue.js logo

Learning Vue.js is fun – if I run into a problem that has taken me some head scratching time to solve and/or and no easy Stack Overflow answer, why not writing a blog post for you and my future self? 🙂

Today’s stumbling block is bi-directionally binding of a Component (v-model), to the root data object – being the Components generated in a v-for loop. Sounds unclear? Think about a lot of instances of a Component containing, say, checkboxes or radiobuttons, automatically generated from an array. It’s a quite frequent scenario, at least in my projects, so let’s have a look.

Continue Reading...

About one year ago I had a so-called “aha moment” and decided to write a book. I had two or three subjects in mind, first choice was HTML Panels’ Licensing Solutions – i.e. how to build trial versions, anti-piracy systems, and the like. Luckily, and I really mean: luckily, I changed my mind and tackled a topic appealing to a slightly broader audience: the HTML Panels Development course was born.

Still, licensing systems in the context of HTML Panels are a soft spot of mine (see my old post about partial serial number verification), and I wish I had time to write that book! I did build, from my biased point of view, very good prototypes back then: for instance implementing RSA encryption, or server-side automatic licensing files delivery to be used in conjunction with e-commerce providers.

Whatever you choose to do, you’re protection system must rely on secured code that nobody can look at – which is what this article is all about.

Continue Reading...

Hello readers, I’m happy to inform you that the “Adobe Photoshop HTML Panels Development” book is in good shape! I’ve kept writing, even if my life by the end of the year has got pretty intense.

I’d like to share with you the book’s Index as it is now; most of the content is already in place, even if stuff is not yet final. I’ve built several demo panels (about 17 of them, and counting), which code will be available alongside with the book.

Continue Reading...

The latest release of Photoshop introduces, among the rest, a new version of the Common Extensibility Platform, CEP6.1. In turn, CEP6.1 is a major break in backward compatibility due to the way it manages Node.js. If you have an extension using Node.js, chances are that it’s now broken in Photoshop CC2015.1. Read along to know why, and how to fix it.

Continue Reading...