Skip to end of metadata
Go to start of metadata

New, dynamic user interface for monitors, tablets, mobile phones

The new user interface also can be controlled on a display of a mobile phone or a tablet. Even the help on the right-hand side can be enabled on a tablet or monitor along configuring the settings in the main screen.

The validation of input fields was newly developed especially for LoxBerry. The updated error messages explain exactly what to do. Special characters for Miniserver passwords are no problem anymore.

Automatic updates - for operating system, LoxBerry, plugins

 

Introducing LoxBerry Update there is a fluent way to release versions with new functions, and to quickly correct errors. With automatic plugin updates directly out of LoxBerry's plugin management, a plugin update is done without effort.

All update features can be configured to notify, to automatically install and - if you don't like annoying update messages, completely turned off. 

Hostname and port can be changed easily

 

Operating multiple LoxBerrys needs to change their hostnames. This now can be done directly from the web interface - without steeping through expansive masses of config files.

The same is valid for the web server port - for users of HA-bridge or other applications that insist to use port 80, you can change the LoxBerry port in the UI.

In the LoxBerry Services widget, at the webserver options, you'll now also find a button to the Apache error log - if, nevertheless, something goes wrong in LoxBerry or a plugin. 

Easier navigation, clear information

 

To free space on your screen, plugins and system settings were splitted. Directly from the plugins page you can access the plugin management and the plugin archive.

Adding a new button in the footer, you can directly access the system settings. And if LoxBerry requires a reboot, this is pointed out at the power button.

Fully integrated multilingual support

As translating LoxBerry in older versions was a pain (for the translators, and later for LoxBerry developers), we completely redesigned LoxBerry's language system from scratch, to fully integrate multilingual support. LoxBerry users directly can translate LoxBerry in the web interface. The created language can be downloaded and submitted to the LoxBerry Core team, to ship it with LoxBerry Update.

But this feature does not stop for system translation - also plugins can use LoxBerry's language system, and plugin users can help delevopers to translate plugins. The generated plugin language file can be downloaded and submitted to the plugin author to integrate it with an update.

LoxBerry is more reliable

Just as on the Miniserver, the SD card has an expiration date on the Raspberry. And we putted off the evil day.

Now LoxBerry uses the RAM disk for log files and constant disk writes. By default, MySQL is not delivered anymore, that had many write operations. Services were optimized to reduce write access to a minimum.

And to be on the safe side: Use the Loxberry Backup plugin to do scheduled backups of your LoxBerry.

Contribute to LoxBerry

We'll be happy about contributing to translating LoxBerry to your native language. Read the Translation Guide for LoxBerry for best practices.

Please report any issues to our issue tracker at Github. Also place your feature requests and ideas there. Place your questions about LoxBerry to the LoxBerry area in loxforum.com. Don't hasitate to write in English.

Don't restrain yourself to donate!  But not to us, but to caricatural organisations. Visit the donation widget where we have added international help organisations.

More details

LoxBerry got a completely redesigned base, not only with a new operating system version (switched from Raspian Jessie to Strech), but also the complete LoxBerry architecture.

The base system now uses a template system that can be used for both system and plugins. Multilingual support is completely integrated to LoxBerry and can be used by plugins too. LoxBerry switched it's development text language from German to English. Translations always proceeding from the English base language.

The plugin interface now raised to V2 (from V1) with extensive enhancements. Many commonly used workarounds because of permission problems are addressed by integrated functions. Plugin developers can make use of a lot of system wide variables to find and access their plugin directories. PHP can be natively used also for LoxBerry web interface generation, and included modules for Perl and PHP supply functions to generate the HTML headers and footers and multilingual support, and easily access configuration data of the Miniservers within one function call.

Plugins developed for LoxBerry 0.2.3 are normally compatible with LoxBerry 1.0. Small issues were already fixed and published by the plugin authors during the closed beta period, for compatibility to both versions. The plugin archive shows the compatibility state for every plugin.

Numbers and facts about LoxBerry: LoxBerry Version 1.0 - BEYOND THE LIMITS (English)

Changelog

The detailed changelog (German only) for users, plugin developers and image integrators, you can find here: Changelog V1.0 (English)


  • No labels