The LibreOffice extensions and templates website (https://extensions.libreoffice.org) got back his customized home page again since about a week. This site was created inside a Plone policy add-on package a time ago and its source code got some CSS-fixes some weeks ago. Great to see that it is again up.
I removed the entry: ‘firefox -v’ and added the three lines at the beginning, thus the missing geckodriver got downloaded, extracted and put into the directory which fited.
With this edits of the .travis.yml file the robot example test runs. I got the same message, once I ran the robot test example on my computer. I could fix it by downloading the geckodriver and install it on the machine.
But it seemed nobody took care of an update of the available LibreOffice versions on the LibreOffice extensions website (https://extensions.libreoffice.org/extensions). This new version was added there just recently. Thus the contributors of the LibreOffice extensions website get a notice of the new LibreOffice version and the opportunity to mark their extension as compatible with that version very lately.
But there are some contributors of the LibreOffice extensions website which reacted very quickly and marked their extension compatible with the newest LibreOffice version. I want to thank them for their quick reaction and their contribution to the project.
I worked on a further edit dialog of the Plone add-on collective.templates today. I added another register to the dialog and reordered some content fields to make it more smooth for the user. You could see some of the register of the template center edit view below.
I created already a new Plone add-on for the upload and management of office template files during the last weeks. I made some further changes to the source code of the add-on during the last days and published new releases of the software.
I reworked the edit view for template projects today. I gave it another structure with register for the different content parts. The dialog is much clearer yet and that will help a contributor to finish the dialog much faster and submit his new project (or edit one of his / her projects).
Here are some screenshots of the dialog and its register:
There is another register for the optional upload of template files for different platforms. It looks similar to the above one. There is also a register to upload a screenshot of the template. This screenshot will be shown to the user in the template project view.
I created a new section for documentation and howtos and added first content about LibreOffice and Plone to it. You could get there my documentation about non-code LibreOffice extensions and a howto about the development of a validation function for file extensions that could be changed by the Plone site-administrator without getting his hands dirty inside the code of a Plone add-on.
I worked on a new Plone add-on to manage and to provide software product add-ons during the last weeks. This new add-on, named collective.addons, runs on Plone 5.2 and Python 3. It has currently a localization in German language too, but it would be easy to add further localizations to the add-on later. It needs only the creation of a subdirectory inside the locales subdirectory and a new po-file for the further language.
I’m currently working on a new Plone add-on to manage the upload and distribution of product add-ons / extensions. I develop this add-on from scratch with my experience from other Plone add-ons which I created within a Python 2 Plone environment.
The development of the new add-on is done inside an environment of the latest Plone version (5.2) in combination with Python 3 (3.6 in this case). I started the development using Python 3 because the support for Python 2 stopps in less than five month and I thought it is not usefull to create a new add-on within an nearly outdated Python environment.
You could get the calculation of the Python 2 version retirement at pythonclock.org.
It’s time for projects using Python 2 to think about the migration to Python 3 soon.
I made a bunch of changes to the Plone add-on which drives the current LibreOffice extensions website during the last weeks. I especially made it easy to enter the file extensions for extension, image and documentation files and change them if needed. This is possible without the need of any programming skills. I had to create new validators for this purpose and replace the old ones with them.