Skip to content

dart-bridge/framework

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Bridge

Build Status Coverage Status Pub Status License

Join the chat at https://gitter.im/dart-bridge/framework

This is the framework repository. The application package is here. Documentation is here.


Bridge

An end-to-end web app framework for Dart

Dart is an amazing language. Not only for creating client side apps, but for servers as well. Since it works on both sides, we have a huge opportunity as developers to maximize code reusability, and to once and for all bridge the gap between the server and the client.

Bridge is an effort to streamline the experience of working with a Dart based back-end. Besides having facilities for server side templating and other things you'd expect from a modern framework, it also provides an out-of-the-box WebSocket abstraction called Tether. With this, we can seamlessly send data structures from server to client, and client to server too!


Getting started

This repository is the home for the framework itself. To create an application based on Bridge, complete these steps:

  1. Install the Dart SDK.
  2. Use pub (comes with the SDK) to activate the Bridge Installer: pub global activate new_bridge
  3. Use the installer to create a new project: new_bridge my_first_project (This creates a folder in the current directory called "my_first_project")
  4. Go into the newly created directory and start the Bridge CLI: dart bridge
  5. Start the server (start) and visit localhost:1337. You can speed everything up by sending through the boot commands start and watch to start the server instantly, and restarting the app on each file save: dart bridge start, watch

Contributing

Contributing to Bridge can be done in different ways. You can:

  • Post issues on this repository if you encounter any bugs.
  • Fork the repository, create a failing unit test, and make a pull request.
  • Better yet, fix the issue yourself, and make the PR.
  • Help with the documentation by posting pull requests to the docs repo.

If you have feature requests, please join our Gitter channel and raise your voice!