bladerunnerjs.org
BladeRunnerJS Documentation
http://bladerunnerjs.org/docs
BRJS) is fundamentally about following a set of conventions that work when building very large and complex front-end applications. BRJS is an extensible toolkit and lightweight JavaScript framework to support these conventions and workflows. The BRJS documentation is broken up into 3 high-level sections:. Overview of core concepts within BRJS. Documentation about using BRJS to build an application. Docs on extending the BRJS toolkit functionality e.g. creating plugins. And includes a Jetty. Where objects...
bladerunnerjs.org
Concepts
http://bladerunnerjs.org/docs/concepts
The purpose of the concepts section is to provide enough basic detail for somebody to answer the following questions:. Why would I need it? How do I use it? The contents of the. How do I use it? Parts of the concept docs wont go into too much detail. In-depth information will be found in and appropriate User Guide or Tutorial. IoC (Inversion of Control). Add a Blade to an Aspect. Using the Unbundled Resources. Using the AliasRegistry (IoC). Building and Deploying Apps. Using the brjs CLI.
bladerunnerjs.org
Workbench Tools
http://bladerunnerjs.org/docs/concepts/workbench_tools
Are pieces of functionality that help you develop and test a blade. As part of the developer workflow. They reside within a Workbench. Normally have some UI representation within the Workbench and allow you to interact with the Blade through stubbed services. And via the EventHub. For example you can view your Blade in different states by sending it mock events via a mock events Workbench Widget. The default Workbench Tools are:. KnockoutJS View Model Visualisation. Add a Blade to an Aspect.
bladerunnerjs.org
Services
http://bladerunnerjs.org/docs/concepts/services
Services provide access to shared resources. They are a means of decoupling implementation detail from the interface that the service provides. For example, a. Used within the application, may have one implementation that persists data to a database via a web service and another that persists to. Services can be registered and accessed from any part of the application via a ServiceRegistry. Service contracts (the functions they provide) can be enforced through the use of interfaces if required. In conjun...
bladerunnerjs.org
Workbenches
http://bladerunnerjs.org/docs/concepts/workbenches
Are a core part of the BRJS development process, which may be used for bladesets or blades. They let you run, view and modify individual blades, so that you can develop and debug each component in isolation from the rest of your application. A Caplin Trader FX Tile Blade. Running within a Blade Workbench. Add a Blade to an Aspect. Using the Unbundled Resources. Using the AliasRegistry (IoC). Building and Deploying Apps. Using the brjs CLI. IoC (Inversion of Control). Roadmap to 1.0.
bladerunnerjs.org
Blades
http://bladerunnerjs.org/docs/concepts/blades
A blade encapsulates all the required resources JavaScript, HTML, CSS, XML, images, etc to implement a particular high level feature. For example, a blade might implement a map UI, a chat window, a charting module or an alerting mechanism. A blade usually (but not always) corresponds to a particular area of the display. Blades can be run in isolation during development in a Workbench. Making them easy to develop, debug and test. Inter-blade communication is achieved via an event hub. Blades do not limit ...
bladerunnerjs.org
Aspects
http://bladerunnerjs.org/docs/concepts/aspects
Aspects take multiple blades and use them to compose a view. There are lots of reasons you might want to use an aspect. These could include the following:. Different aspects for defined steps in an application workflow e.g. Login and Main. Composing aspects out of application blades for different devices such as tablets or mobiles. Aspects for different service levels or user permissions, for example aspects containing more blades providing access to more features for premium customers. How to Use Aspects.
bladerunnerjs.org
CommandPlugin Tutorial
http://bladerunnerjs.org/docs/extend/command_plugin_tutorial
Is the simplest extension point for BladeRunnerJS. As the plugin name suggests, it gives you the ability to define commands that you can execute via the. Command in the form:. Brjs your command plugin name. Also has access to the BRJS model. Eclipse IDE - used in this tutorial, but it will be easy to convert these steps to using another IDE. BladeRunnerJS - of course, youll need BladeRunnerJS installed. This tutorial well introduce you to the basic concepts by creating a very simple ListAppsPlugin. Pleas...
bladerunnerjs.org
ModelObserverPlugin Tutorial
http://bladerunnerjs.org/docs/extend/model_observer_plugin_tutorial
This section of the documentation is coming soon. Add a Blade to an Aspect. Using the Unbundled Resources. Using the AliasRegistry (IoC). Building and Deploying Apps. Using the brjs CLI. IoC (Inversion of Control). Roadmap to 1.0. Got a suggestion to improve the docs? You can find the source on github. Please submit a pull request or raise an issue. 2000 - present Caplin Systems.
bladerunnerjs.org
Roadmap to BRJS 1.0
http://bladerunnerjs.org/docs/roadmap
Roadmap to BRJS 1.0. A key part of building a scalable application is loosely coupled communication between application components. We had an event hub, but took it out as it was a bit too complicated for general use cases. We want to add this key concept back in. Nodejs style client-side code. We dont like the way we currently need to write our JavaScript. We like the Node.js coding style and moduling system. So, were adding support for it within BRJS applications. Will look like this:. Are a really pow...
