You can find me and other members of PrimeTek hanging out there.ġ) Visit Apollo Live demo /apollo-ngĢ) Configure a design and take a screenshot
RT cagataycivici: PrimeLand Discord Server has reached 8k members. RT cagataycivici: Special thanks to all contributors of PrimeFaces 12.0.0. JSF has an ecosystem, if members of the ecosystem conflict it won’t be an healthy 12.0.0-RC3 is out now with 40+ improvements, we're getting ready for the final release ?… /i/web/status/1… 1 week ago This is a nice example of cooperation between component libraries, of course there is a competition since these projects are trying to solve same problems in web development but competition should not harm JSF users but provide benefit. In cooperation with Dmitry, I’ve identified the issue and fixed it, tried adding OpenFaces 3.0 to PrimeFaces showcase, played with some components from both libraries and tests passed well. Last week, OpenFaces 3.0 is released featuring JSF 2.0 support and Dmitry Pikhulya from OpenFaces team contacted me regarding an issue between PrimeFaces 2.2.RC1 and OpenFaces 3.0, OpenFaces components were not functioning because PrimeFaces was preventing it. Prior to JSF 2.0 as everyone including PrimeFaces cooked their own solution for Ajax, Resource Loading and other things causing pain for JSF developers who want to use some components from XFaces and YFaces. One of the promises of JSF 2.0 is component library interoperability, still component library authors should work together to identify issues that can or cannot be covered in JSF 2.0 Standards.