Components are the fundamental building blocks of CBWIRE applications. They encapsulate both the data and behavior needed to create interactive user interface elements that respond to user actions without requiring full page refreshes. Think of components as self-contained, reusable pieces of functionality that manage their own state and handle their own user interactions.
Components can be as big or small as you like. For example, you may have a Signup form component that covers multiple steps or a simple button component that you reuse throughout your application.
Each CBWIRE component is a ColdBox component (.bx for BoxLang, .cfc for CFML) that extends the base cbwire.models.Component class. This inheritance provides all the reactive functionality and lifecycle methods needed to create dynamic user interfaces. Components follow a clear structure and naming convention, making them easy to organize and maintain as your application grows.
Components are made up of data properties, computed properties, actions, and a template. This separation of concerns keeps your code organized and maintainable while providing the flexibility to create complex interactive experiences.
When a component is rendered, CBWIRE automatically handles the initial setup, manages the component's lifecycle, and coordinates communication between the server and client. This abstraction allows you to focus on your application's business logic rather than the underlying mechanics of creating reactive interfaces.
// ./wires/Counter.bxclassextends="cbwire.models.Component"{ // Data properties data ={"counter":0// default value}; // Actionfunctionincrement(){data.counter++;} // Helper method also available to templatefunctionisEven(){returndata.counter %2==0;}}
// ./wires/Counter.cfccomponentextends="cbwire.models.Component"{ // Data propertiesdata={"counter":0// default value}; // Actionfunctionincrement(){data.counter++;} // Helper method also available to templatefunctionisEven(){returndata.counter%2==0;}}
By default, components are placed in the ./wires folder in the project root. You can change this location using the wiresLocationconfiguration setting.
Rendering Components
You can render a component using the wire() method.
You can call wire() from within your ColdBox layouts, ColdBox views, and also from your component templates ( See Nesting Components ).
External Components
You can render wires from folders and subfolders outside of the default ./wires folder.
You can also reference components within another ColdBox module by using the @module syntax.
Passing Parameters
You can pass data into a component as an additional argument using wire().
By passing in parameters, you can create reusable UI components that are unique but similar in functionality. For example, you could make a button component that you reuse throughout your app.
Using Parameters
Parameters are passed into your component's onMount() method. This is an optional method you can add.
CBWIRE only executes onMount() once when the component is initially rendered. It is not executed for subsequent update requests of the component.
Auto Populating Data Properties
Properties you pass into your component as params will be automatically populated if onMount() is not defined and a matching data property is found.
Passed-in properties must have a data type of string, boolean, numeric, date, array, or struct.
Nesting Components
You can nest components as much as you need by simply calling wire() from within a template ( See Nesting Components ).
CBWIREController
There may be areas of your application where you need to use wire() but don't have access to it. You can use the CBWIREController object to insert wires anywhere you need.