Skip to main content

Summarizing Summer

It was a great pleasure to work with great coders/developers at Plone Foundation and learning a lot from them during the course of the program. This blog is about summarizing the whole work I have done during this summer under Google summer of code 2016 under Plone Foundation.

So my project mainly focuses on improving forms in plone for dexterity. We already have forms in plone for archetype. So there is a project named collective.easyform which basically provide forms for Plone as dexterity contenttype. The main focus of the project was to improve that code base. Make this stable for plone 5.0 and above. Make all the test cases passing for the code base. Try to cover tests as much as possible code base. Also implement functionalities for fields/actions of the forms in correct place. Make the plone more user friendly. Finally for users who want to migrate their already present forms in Plone Form Gen (PFG) which is archetype to easyforms which are dexterity based forms Plone. This will require creating a custom control panel for users(Admins) so that they will be having options to migrate all the from PFG to easyforms and later on create a report of the migration of the forms.

So we have already improved all the test cases and all test cases are passing for the project and project is stable for plone5 and upper versions. Here is the code base for the following feature.

After that we worked on improving easyforms feature so that it is more user friendly and the code base for the following can be found here

After that we created custom control panel so that Admins have option to migrate the forms. Here is the code base for the same.

After that we started working on migrating easyforms and we started with fields and succeeded in writing migration for fields and we can improve those migration gradually. These migration are not that easy as normal migrations in plone as PFG were Folder so they have heirachy in fields and we have to handle each and every field manually. Here is the code base for migrations for PFG to easyforms.

I really learnt a lot during the whole time and I am hoping the same for future also as I will continue the work for migration to improve the migrations.

Cheers

Comments

Popular posts from this blog

Introduction to Code Base for easyform

So its been the end of community bonding period and I have been looking into the code base for which I will be working for this summer's project. Collective.easyform , A project for Plone which helps in create forms for plone using dexterity content type. So the project mainly focuses on Improving this add-on to work for properly for Plone5. Current Status of collective easyforms :- Wooh!! It's breaking and failing at lot of the parts. So right now the project is failing for tests and one of the main task of the project is the improve tests to make them work for project. Improving tests help us in tracking the future changes of the project so that we can see if new things/features are working properly in the code. Work done till now :- So till now I have done the setup for the project and did one feature correction, the basic mailer_template which is the default one is not able to render properly and it was showing error , so to make it fix everytime, we have to co...

New Releases at plone , releases my sweat !!

Hello everyone!!, in the blog I will share my experience that how things become terrifying if the new version of some product is released in plone. The main problem occurs when we have not pin up the products to the specific versions in the buildouts. Wow!! its a lot much at one shot. Don't worry we will understand each and everything. Lets start.. Plone uses buildouts to make a structure of its code. There are builduts.cfg (Configuration files) to set up plone projects. What is buildout ? Buildout is a Python-based build system for creating, assembling and deploying applications from multiple parts, some of which may be non-Python-based. It lets you create a buildout configuration and reproduce the same software later. So plone uses these buildouts for setups. I have also configured the buildout for my project and things were going great until there is new release for plone 5.0.dev from plone 4.3.6(the previous plone version). Here is the snip...