Frequently Asked Questions

General

What is Componyx?

Componyx is the brand behind Componyx.UI, a UI component library and Bindary, a data-binding layer, both built to work directly with plain HTML, CSS and JavaScript. No build step, no dependency sprawl. See the About page for the full story.

Are Componyx.UI and Bindary free to use?

Yes. Both are free to use, commercially or personally, as a company, freelancer or agency. They're source-available under the Business Source License 1.1. See the License page for the full details and a plain-language summary.

Do I need .NET to use Componyx.UI or Bindary?

No. Componyx.UI and Bindary are client-side technologies and work on any web page regardless of the backend. Optional .NET integration via NuGet makes setup easier in .NET projects, but isn't required.

Are there any third-party dependencies?

The client-side core of Componyx.UI and Bindary has zero external runtime dependencies. Optional server-side integrations, such as .NET and Node.js, may use a small number of standard packages, but these aren't required to use Componyx.UI or Bindary in the browser.

Is Componyx.UI ready for production use?

Yes. Both have been refined through more than a decade of use in real production systems.

Do I need npm or a build step, to use Componyx.UI and Bindary?

No. You don't need npm, a bundler or a build step.

In a .NET project, install via NuGet and the required resources are handled for you. Outside .NET, you can install via npm or load the bundled files directly from a CDN such as jsDelivr or unpkg.

Does Componyx.UI have TypeScript support?

Yes. Componyx.UI includes complete TypeScript definitions, providing autocomplete and type checking when used from a TypeScript project. The library itself is written in plain JavaScript, so there's no compiler or build step involved.

Which browsers are supported?

Chrome, latest 2 major versions
Microsoft Edge, latest 2 major versions
Firefox, latest 2 major versions
Safari, latest 2 major versions

Contributing

Can I contribute?

Yes and it's genuinely welcome. Right now that mostly means bug reports, testing new releases, suggesting improvements and building your own components on top of Bindary, which doesn't require touching the core repository.

I found a bug or want to request a feature. What do I do?

Open an issue on GitHub. Include steps to reproduce and, if possible, a minimal example. That's the most useful thing you can provide, whether or not you plan to fix the issue yourself.

How do I report a security issue?

Please don't open a public issue for security concerns. Reach out directly via the contact page so the issue can be addressed before details are made public.

Can I submit a pull request against Componyx.UI or Bindary itself?

For now, the core repository is kept to a small, trusted group. If you'd like to get more involved, reach out via the contact page.

Bindary

What is Bindary, exactly?

A reactive data-binding layer for plain HTML. It binds values, repeats data, handles routing and keeps your UI in sync with your data, all through b-* attributes on regular HTML elements. See the Bindary overview.

Can I build my own components on top of Bindary?

Yes. You can create, distribute and sell your own components using Bindary's public data-binding API, whether free or commercial.

Do I need Componyx.UI to use Bindary?

No. Bindary works entirely on its own. Componyx.UI and Bindary are independent, but designed to work well together.

Componyx.UI

Are the CSS stylesheets required for components to work?

The core stylesheet is required. It defines the structural styles each component needs to render correctly. Most components also include a separate theme stylesheet for their visual appearance, which you can override or replace entirely.

How do I avoid CSS conflicts with my own stylesheets?

Every component wraps its markup in a root element named after the component itself, such as .grid, .app-skin or .combo-box. Component styles are scoped under these classes rather than generic selectors.

Keep your own selectors specific enough to avoid conflicts with a component's internal structure.

Less specific, more likely to conflict: .content { width: 500px; }

More specific, safer: section.home > header > .content { width: 500px; }

Can I use Componyx.UI components in a React, Vue or Angular application?

Yes. Componyx.UI has no dependency on a particular framework. Components can be added to any page through declarative HTML or JavaScript, regardless of what else the page is built with.