BrightSide gets a new language module, isolating the resources treatment. With the new Elephant Locale project, will be easier to mantain locale resources from external sources, as well as indicating which languages should appear as available to final users. The goal of this project is to incorporate collaborations in locale maintenance, making easy the way new languages get their way into the whole set of modules.

Turro.Org will also stop giving direct support for Castilian (Spanish). Provisionally and in order to allow fresh versions of Castilian, French and German, collaborators will be able to edit these resources from Turro.Org. Soon we'll come with instructions on how to collaborate with the project.

Catalan and English will continue to be directly supported.

BrightSide is getting new updates to stable modules. As a well-structured platform, changes spread among all parts, improving the whole. Wizard-like forms, welcome panels, summaries.

The goal, making things easy for final users, while keeping the scalability. Most of the improvements were include as self-contained plugged components.

Welcome panel

Source code browsable at Full report.

BrightSide is now running on top of ZK new version, ZK 6.0.1. Code upgrade went smoothly, as if previous issues were all solved, an effect of the ZK project activity. Some improvements shine by themselves:

• Speed, new version runs faster.
• Control over UI, components layout is close to perfection, while composers handle the hard part. 

Lifeline is quite an improvement in Facebook presentation, definitely. But does the same apply for you? I mean, does Facebook lifeline be a good presentation for you?

Previously, they were showing your activity, clearly within Facebook scope. Now, with the inclusion of birthday and from there on, they seem to claim your life is what is shown or, at least, what you choose to show. This move makes a difference, a huge difference. You might wonder why do I mention this at all. Right, I tell you.

As a matter of fact, BrightSide is intended for final users. You could see the Application Framework as a good starting place for writing your code, but the objective were always final users.

When analyzing, developing or testing you're not seeing what a final user will see. Your efforts aim to performance, some good-looking design and as less as posible bugs. For sure any final user will be happy having such an application... with the time. But not at first glance. Clarity and a good design are more significant when somebody first meets your application.