P4A 4.0 update (continued)

Time goes bye, but that doesn’t mean I’m not thinking about the new version of P4A almost every day…The point is, P4A 3.8.x (use the github master version, it’s ok and much more updated compared to 3.8.4) it’s working fine also if it’s some years old, it does everything needed and it does is well.

To go forward I want to be really forward, this is how I think about innovation.

So, in the past month I’ve been rewriting all P4A’s core using autoload, composer, skeleton applications, namespaces and all the modern fashion programming :) It’s all on github if you want to take a look. At the moment there are no plan about removing the “builder” pattern or the “I live in the session” feature of P4A, it would become a completely different framework and simply it wouldn’t be P4A anymore.

Now we come to the GUI, this is always been a really tough task, it’s been years since the first time we spoke about it and we’re still there… I’ve trying everything (bootstrap, dojo, qooxdoo, extjs) more than one time wasting countless hours. Last but not least I thought I decided to go with a nice bootstrap admin theme called adminlte, I’ve also contributed to their repository fixing a few things but… just when I was about to finish… simply I didn’t like it anymore, simply it was not the leap forward I’d want.

So the question now is “what’s next?”. Actually there’s something big but it takes time. This thing comes from the last Google I/O… and it’s called Polymer! I think Polymer it’s going to be the next big thing for the years coming. It’s webcomponents, it’s declarative, it’s self contained, it’s modern looking, it’s material design (for the ones of you who know android), it should be the next library google is going to use for its products (gmail etc), it’s fast (much faster compared to dojo or other javascript RIA frameworks).
It the past weeks I’ve been working around 20 hours to integrate Polymer in P4A, results are good, it was quite easy (and that’s a good thing) due to it’s declarative nature and thanks to the wise shadowdom usage, but not perfect. Polymer it’s still very, very young. A lot of things are missing (dropdowns don’t work with value/description or do not support label or they can’t be submitted) a lot of components are lacking (datepicker, colorpicker, table/grids, consistent builtin file upload and surely many more).

I think it could be worth the wait, P4A could be the first framework to deliver Polymer applications, we would be again on top of the edge and this would be great for the live of P4A itself. I think I don’t want to look back at css/js frameworks, they seem so old compared to webcomponents. With Polymer (which by the way it’s under BSD license) it would also be much easier to create new widgets, there’s already a themes website which looks quite good and could be used by you to customize your applications.

If Polymer was complete (and fully working) P4A 4 would be already out, cause the porting was surprisingly easy, but it’s not so… we’ve to wait for it to be ready.

What do you think? Please let me know.

7 thoughts on “P4A 4.0 update (continued)

  1. Manny Popes

    Polymer is promising, love its adaptability for diff platform. It’s good to know your thinking of P4A almost daily, I just thought it’s gonna be the end of line for this great framework. There is still light at the end of the tunnel.

    We’re surviving on last version of p4a to-date. It’s gonna be worth the wait for the reborn of P4A. Cheers to that!!!

  2. BES

    Looking forward to the next generation of P4A! Keep us posted!

    What will be the minimum version of PHP supported?


  3. Hector Gonzalez

    iam looking your work and congratulation for it, dont stop your hands continue your work. from Venezuela

  4. Cris

    Hi, time has passed and Polymer is now at v1.7.
    I’m sure it has matured a lot and is now more than ready for your project to make the leap you want.
    So what’s the next step? Are you still working on this project? I love P4A!

  5. Fabrizio Balliano Post author

    absolutely! it’s a really amazing tool but the toolchain is really different from the beginning and it’s not really fitting the old approach that I’d need to use it. Also, it’s still lacking things like an official date/time picker. I think the use scope for polymer it’s probably different from a “data management” application, not sure but…

  6. BES

    Am about to start a new project and would love to do it with P4A 4.0.

    If Polymer isn’t working out, is an alternative in the works? Will 4.0 support PHP 7.1?

Leave a Reply

Your email address will not be published. Required fields are marked *