infiniquery
Building search screens has never been easier.
Building search screens has never been easier.
Building a complex search screen, with infiniquery, is as easy as writing a simple XML file.
Infiniquery generates the entire frontend for you, after inspecting your Java backend objects via reflection. Once you have your JPA entities in place, in the backend, you don't need to write any HTML, CSS or JavaScript! The framework does that for you.
Fresh, modern and fully intuitive, infiniquery empowers end users to create free, flexible queries, without syntax learning overhead.
"Simplicity is the ultimate form of sophistication." Leonardo da Vinci
Empower end users to express freely and recombine conditions, values and operators in visual queries of unlimited power. The power is limited only by user's imagination.
Users are served information in a sequential manner, allowing them to focus on one thing at a time - just like the human brain is optimally designed to work like. The user is only seeing what he is interested in and not abused with extra information in the page. Fully intuitive. No user manual needed for end-users. Easy to follow documentation for application developers.
Instead of investing full design and development cycles into maintaining old-school search screens (based on hardcoded user interface components), infiniquery allows developers to create and update search screens, only by editing an xml file, in a fully declarative way. No interface redesign, no coding and no server restart needed. The interface is dynamically generated by the framework, under the user's clicks.
Cross-browser compatible front-end. Back-end build on top of the standard Java Persistence API, connectable to all major RDBMS. Able to work with popular non-standard data types (like Joda DateTime), without forcing compile or runtime dependencies to such APIs. Can be extended even to work with non-relational databases (see the Documentation and FAQ for more details).
Secure against SQL injection attacks. Clean demarcation preventing backend details to be exposed onto the frontend (still can be configured to allow this if you need it for administration purposes). Optional security restrictions, based on user roles, are supported out of the box.