eeDepart - vision of the 2e FE future

What's eeDepart?

Both a framework and a working implementation

What problems is eeDepart trying to solve?

• Limited code reuse between projects
• Limited code reuse inside the project
• No best practices on where and how to do some specifics

genericdatatable.inc

First attempt at making a reusable component that could be dropped in the code and used by defining configuration and data processing that is domain related

Implementation... could have been better :) but it helped us realise it's all about the interface and creating smaller, reusable functions

Slight digression

Backbone.js gives structure to web applications

Marionette.js is a composite application library for Backbone.js that aims to simplify the construction of large scale JavaScript applications.

It is a collection of common design and implementation patterns found in the applications that have been built with Backbone.js

Goals of eeDepart

1. provide CKI application architecture
2. provide interface definitions
3. provide an application with working generic CKI processing
4. be a repository with best practices

Project organisation

1. eeFEtools
2. eeDepart core
3. eeDepart custom

So how does this work?

1. ck.fly
2. app.js
3. eeDepart.js
4. module trigger (e.g. retrieveApp.js)

How do you use eeDepart for new CKI?

1. copy configuration files
2. add PHP implementations (e.g. processing changes)
3. override views/templates in JS

Override example

Questions