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

One Last Time

Okay. So finally the list of GSOC'16 selected students is out and I am glad that my project got selected under Plone Foundation. I am really looking forward to work on my project which is basically improving the add-on named easyforms. I have already started working on the same project and will plan with my mentor for future work. I will keep this blog updated with the work I will be doing during the project as I did last summer too. Cheers.

Tickling with tests

Hello everyone, So finally we have been at the end of the project and I really enjoyed each and every part of it. So after unit testing the transform its time to write functional tests and integration tests or we can say the browser tests for our add-on. I have written the functional tests to ensure that the new add-on is imported and all the profiles are installed and the editor is using our new transform and not the old transform. So for that we have already implemented the registration of new add-on to replace it with old one and we also have to make tinyMCE uses our new transform. How to make tinyMCE uses our new transform in place of old transfrom ? So for understanding that we should have the idea how tinyMCE calls for the transform script. So it uses getToolByName in portal_transform to get the required transform. So tinyMCE search for safe_html in portal_transform and the old transform was named safe_html. So here we had two ways to proceed :- 1) Either change tinyMCE