Extensions Project Joins PrimeFaces

Extensions Project Joins PrimeFaces

We are excited to announce that PrimeFaces Extensions project will be merged into PrimeFaces. Extensions have a lot of great components that are popular in PrimeFaces community. Merger will have various advantages such as avoiding compatibility issues between core and extensions, better support for future.

To begin with, not all components will be merged and they will stay at extensions project, popular components such as timeline, inputnumber and keyfilter will be moved to core whereas components having duplicate functionality will be reviewed to see if missing functionality in core will be added from the extended one. Finally components including codemirror are not planned for the core.

Overall we are all excited and will start moving them in near future targeting 5.4 release.

  • Peter
    29 October 2015 at 11:11


  • Oleg
    29 October 2015 at 13:24

    Thanks for announcing! We will “freeze” the PF Extensions project. Some important components will be moved to the PF core and other ones to a new “Sandbox” project. Users can fork, fix the sandboxed components, add new ones, provide pull requests, etc. If we see, a sandboxed component is a good one, it can be moved to the PF core. Is it a good strategy?

  • Melloware
    29 October 2015 at 13:43

    This is great news. The components my company uses heavily are…

    1. TimePicker
    2. InputNumber
    3. CodeMirror
    4. KeyFilter

  • Julienng
    29 October 2015 at 15:22

    That can be cool to see with : .

    KeyFilter/inputMask have functionality in the same area that can be merged with this library and do a lot more than what both component can offer now.

    I use it in replacement of inputMask and inputRegex parameter I develop for keyFilter.

    But I can open an issue to talk about it on github if you want.

    Julien CAVALEIRO

  • V
    29 October 2015 at 16:23

    pe:layout allows arbitrary nesting of pe:layoutPanes. Also allows doing things like:
    And a lot more… pe:layout should become the new p:layout.

    • V
      29 October 2015 at 16:24

      Eh, formatting.

      — h:form
      — — pe:layoutPane
      — — pe:layoutPane

      Two panes in one form.

  • Fausto
    29 October 2015 at 17:06

    That’s great news.

  • Oleg
    30 October 2015 at 01:24

    I’m not sure currently if pe:timePicker should be migrated to PrimeFaces or stay in the “Sandbox”. We can discuss this later. looks promising. It has some features from KeyFilter/InputMask/InputNumber.

    pe:layout uses the same jQuery plugin as p:layout, I’m sure PrimeFaces can extend p:layout easily.

Post a Comment