andreasma at Free Software and other topics
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.
You’ll find the new section at https://amantke.de/dokumentationen-howtos/
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 created a first alpha release of the new collective.addons Plone add-on today and uploaded it to the ‚Cheeseshop‘ (https://pypi.org). You can find it at: https://pypi.org/project/collective.addons/
The source code of the new Plone add-on is available at the Plone community repository at Github: https://github.com/collective/collective.addons
I created a new Plone 5.2 and Python 3.6 buildout to migrate the Plone add-on collective.clamav to this Plone version and Python 3. I had to change the ‚import Globals‘ and the use of ‚Globals‘ according to the information on the upgrading Plone 5.1 to 5.2 website (https://docs.plone.org/manage/upgrading/version_specific_migration/upgrade_to_52.html). I also changed the ‚implements‘ statement to the ‚@implementer‘ decorator.
I had to remove the backward compatibility to the AT content types. It works with the new (Dexterity) Plone content types only. I tested it successful with the Eicar virus test signatur.
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.
The new release of the Plone add-on ‚tdf.templateuploadcenter‘ is available via the ‚Cheeseshop‘ (https://pypi.org) yet:
https://pypi.org/project/tdf.extensionuploadcenter/
It is version 0.36 and you could download it from there or much easier include it into your buildout script.
I made some changes and fixes on the Plone add-on that drives the current LibreOffice templates website. This changes makes it possible for a site administrator to set allowed file extensions on the site within the template center content type (without the need to touch the source code).
I created a release of this Plone add-on and published it today on the Cheeseshop (https://pypi.org) (release 0.31):
https://pypi.org/project/tdf.templateuploadcenter/
I’m working on a further Plone add-on that provides an environment to upload and manage product add-ons or extensions. This add-on will work with the new Plone version 5.2 and Python 3. The add-on will be published under the GPL license and the source code will be available in the Plone community repository on Github.com.
I worked on some further improvements of the Plone addon tdf.templateuploadcenter. A site administrator is able to edit the allowed image and template file extensions. Thus I wrote a new validator for this file extensions. I created a field to inform contributors about the currently allowed file extensions (with dynamic content).
The add-on provides not only projects with releases but also small projects where the template files are uploaded to the small project content type directly.
Today I made a new release of this Plone add-on, which drives the current LibreOffice templates website. The Plone add-on and its release are published as Free Software under the GPL-2 (General Public License version 2): https://pypi.org/project/tdf.templateuploadcenter/
I worked on a new Plone add-on during the last two month. This add-on provide an environment to upload and manage office template projects and files. I finished my work on a first alpha release of this add-on, which is named ‚collective.templates‘. It is hosted in the Github repository of the Plone community: https://github.com/collective/collective.templates .
The add-on is compatible with Plone 5.2 and runs on Python 2.7 as well as on Python 3.6 and newer.
I published a first alpha release of this new Plone add-on on the ‚Cheeseshop‘: https://pypi.org/project/collective.templates/ .
I worked on a new Plone add-on during the last weeks, which provides an environment to upload and manage office template files. This add-on is nearly finished yet. I’m going to publish this product, which is hosted on the Plone community Github repository (https://Github.com/collective), soon.