|You might also find it helpful to read key concepts if you haven’t yet
Start the BRJS process
The BladeRunnerJS process starts an ApplicationServer that receives requests for your webapp. It pulls together all of your code and serves them in a few "bundle" files. You are free to split all your code into as many files and directories as you like, without the overhead of getting them all loaded into the browser. Just stick to the BladeRunnerJS structure and it takes care of itself.
Loading files on an F5
BladeRunnerJS works in two modes: "dev mode", where all assets for your app are loaded on-demand, as soon as you hit F5. You can add/remove and change dependencies for files, F5 is always your only build step for fast develop-refresh cycles. "prod mode" is where all assets are pre-bundled into one file, minified and gzipped at build time and inserted into a war for deployment onto J2EE servers.
In development mode, when the application index.html is being requested, BladeRunnerJS reads special tags that are included in the source page to work out which assets are required and in what configuration
<link rel="stylesheet" href="../v/dev/css/common/bundle.css"/>
<link rel="stylesheet" title="noir" href="../v/dev/css/noir/bundle.css"/>
Build the Layout Manager and Components
The application also bootstraps the layout manager which then loads components. Or it simply creates the components and puts them on the page if it is a simple app.
Webcentric is CaplinTrader’s library for providing rich GUI frameworks that allow the user to customise, save and manage the layout of components. It loads the user’s layout from the server, puts the layout on the screen and loads the components based on the configuration in the layout.