Well, quite a lot to be honest. So I have to break it down a little bit.
Translations
First of all, Dutch translations. There were no translations before, nor a .pot file to base a new translation on. So with this Dutch translation, comes the .pot file for others to add new translations. I hope this is the start of adding a lot more of translations to the list. Block Designer is currently being used in a lot of countries:
- Austria
- Australia
- Belgium
- Brazil
- Canada
- Colombia
- Denmark
- Finland
- France
- Germany
- India
- Ireland
- Italy
- Japan
- Luxembourg
- New Zealand
- Poland
- Portugal
- Puerto Rico
- Romania
- Slovakia
- South Africa
- Sweden
- Switzerland
- Thailand
- The Netherlands
- Turkey
- United Arab Emirates
- United Kingdom
- United States
And probably more I do not even know about. So with 30+ countries, it would be nice serving a lot of different languages, next to the existing English and Dutch languages.
If you're able to do a translation for ANY language, do let me know. Someone could be already translation in the meantime, so just in case, let me know when you're willing to do a translation before actually translating.
Code generation
Block Designer was generating some code here or there, which wasn't used (or was there more than once). This because some field types might use them in some circumstances. So Block Designer wasn't being smart here. But now, Block Designer is quite a lot smarter. It will know when to use some variables, know when to include "use statements" or assets (CSS and/or JavaScript).
There has also be an improvement of indenting the generated code. Sometimes it would not indent, indent too much or it needed some extra indenting. Well, that's history. Block Designer will be able to generate well indented code, so you'll be able to read it right away (if you are a developer or understanding code that is).
Within coding, you can have coding standards. The most used one is PSR-2 (you can read about that over on PHP-FIG). As of version 2.x, this Add-On will be following these standards more then before.
Extra's
The "Select" field type did not have a function to translate the entered options, using concrete5's translate function (that would be t("Your option") in code). Within multilingual sites, you will be certainly needing this option.
Talking about the same "Select" field type, it had some issues when used in a "Repeatable" field type. A fix has been applied too.
Developer information
- Added ability to not escape text boxes/text areas, within a "Repeatable" item
- Added smart function "getAssets" to field types for requiring and registering assets in the controller's functions (see DateTime field type for a comprehensive example)
- Removed unnecessary (empty) template files which where used to build the block type (along with some extra code)
- Removed unnecessary use statements within single pages "Block Config" & "Block Order"