Posts

Vanilla Badges – Update

Due to an issue beyond my control, I could not meet the deadline for Preview Release for Vanilla Awards (Badges). The release is now scheduled after Easter, on 06/04/2013.

I will use the additional time to fix some issues I found and to add some more features to the plugin. One of them, the Awards Leaderboard is complete (screenshot below).

I would like to thank all the readers who registered for the Preview Release and apologies for the delay. I wish all of you a great Easter!

Awards Leaderboard screenshot

Awards - Leaderboard

Vanilla Badges Plugin – New preview images

As we are getting closer to the pre-release, I finally have some time to adjust the look and feel of the (many) User Interfaces of the plugin. I took a couple more screenshots and added them to the gallery in the original announcement. Feel free to have a look, any feedback is welcome!

Badges Plugin for Vanilla Forums is coming!

Vanilla Awards Announcemente PostIt took a lot of time and effort, but the first version of the Badges/Awards Plugin for Vanilla Forums 2.0 is coming out soon! This plugin was developed following the requests and feedback of several Users, and it has be named Awards to avoid confusion with the free Badges plugin released recently.

Based on current schedule, the Preview Release should be available by 29/03/2013.

Some of the features

Here are some of the features that this first version will include:

  • Fully customisable set of Rules.
  • Support for virtually unlimited Badges, each with its own image.
  • Support for virtually unlimited Badge Categories, each with its own image and CSS style (for advanced Users).
  • Ranking Points (to be used with Ranking Plugin, in development).
  • Tracking and notification of awarded Badges.
  • Convenient Admin interface.
  • Badges Widget, to show everybody your achievements.

New features are being added as you read, so stay tuned for the big day! 🙂

Sneak peek

Here are two screenshots of the plugin in its current status. Just a bit more polishing, and it will be ready to go!

Preview Release

Initially, a Preview Release of the plugin will provided at a discounted price to a few selected Users who agreed to become early adopters, and who are aware that, due to the plugin complexity, there may be some minor issues still to be solved.

If you would like to be considered for the pilot, please register your interest using the Contact page.

Thanks for your patience, and see you soon on release day!

The base image for the badge is courtesy of digitalart/FreeDigitalPhotos.net

Apology – Content removed due to poor quality

This post is an apology to all the readers for having published a post, now removed, which was not constructive and contained poor quality content and that upset one of our readers.

The purpose of this blog is sharing experiences related to Software Development, in the hope that they might be useful to fellow Developers. The removed post did little to achieve such objective, and contained excessive remarks that should have been avoided.

As the person responsible for the content of the blog, I would like to apologies to the reader who reported the post, and to anyone else who could have found it upsetting.

I will make sure that such type of content won’t be published again.

Regards,

Diego

Why you should always add Licensing Terms to any software you distribute

I recently got involved in a debate on the topic of Software Licensing, and I found it sad that there is so little understanding, amongst Developers, of such an important topic. Together with writing complete and accurate documentation, knowing how to license your Software is one of the skills that any Developer worth his salt must have. At the same time, Users must learn how to read licences, and get the habit of doing it, unless they like risking to violate them without even knowing. Read more

How NOT to interact with non-technical Users

The content of this post has been removed following a complaint received by a reader.

The objective of this blog is to share experience with fellow developers in a constructive way. We acknowledge that the original post didn’t meet such objective, due to some non-constructive remarks that should have been avoided.

We would like to extend an official apology to anyone who was offended by the post, and reassure all our readers that we won’t be publishing such type of content again.