caplin / boxxer Goto Github PK

We might create a wrapper class around boxxer, named "$b" or something.

See: https://github.com/caplin/boxxer/wiki/API

We need to get rid of QuickPHP and have a catch up about how the node back-end works.

Width and height "weight" get stored as pixels.

We want to support Caplin Components too.

Currently, boxxer is being developed and tested in Chrome/Firefox and Opera. These browsers are all supported.

Our main target is to support every modern browser which properly support HTML5, including IE9.

Make boxxer.ViewContainer work properly.

It has been added as a feature under 2 hours, requires debugging and proper testing - or something.

We might want to consider integration of Backbone/Ember Views or at least supporting them...

Make boxxer.Dialog work properly.

It has been added as a feature under 2 hours, requires debugging and proper testing - or something.

Main classes should interact with each other.

Box contains optional ViewContainer, optional **Dialog* (as a cover or something)
Dialog contains either a ViewContainer or a Box instance
ViewContainer has reference to Dialog (hide, show, resize, etc.) and to container Box

My issues with the class I have written:

• It isn't scaleable when it comes to de/serializing a box or any JSON layout.
• We might want to go with boxxer.getLayout("mylayout.json"); too.
• Review and redesign JSON parsing.

To find the child in the whole Box hierarchy recursively

Create it after the Issue #14

Currently we have serialization and persistence too. Of course this requires the Public API to be finished.

We have QUnit, and Sinon.JS too. We should cover most of our stuff with tests.

We need to get that JSDoc grunt module work. The code is (more or less) properly documented, it should create a decent documentation.

I need to refactor the code so it will get more flat. The concatenation will provide a scope start and end file. This should also improve the performance but might raise some issues with the variable names.
We should only be exposing the methods we need.

We need to be able to sort and drag&drop the Boxes.

We need to review the code and optimize if required.

Honestly, we don't really need it. Users should include the shims since they know exactly what they are going to support.