webappsolution / flow-mvc Goto Github PK

We might just want to create our own dispatcher right in our base classes as opposed to injecting them and relying on DeftJS.

Needs basic unit tests.

Basic unit tests.

Need unit tests for both ExtJS and Touch.

Basic unit tests.

Hi,

I noticed a type error inside the file app/view/extjs/EmployeeDetailView.js

Line 26:
Ext.define("CafeTownsend.view.touch.EmployeeDetailView", {

Should be:
Ext.define("CafeTownsend.view.extjs.EmployeeDetailView", {

Notice: 'touch' should be replaced by 'extjs', as we are inside the extjs folder.

Please update the source code with this change, thanks !!

• same syntax of coding throughout.
• clean JSDuck documentation for all classes, methods, properties, events, etc.

Need a ant build.

Basic unit tests.

test

Finish unit tests for:

• selected record
• update
• figure out why it's not working for touch 2.0

The event handler methods get called but for some reason the spyOn() doesn't pass and say it's been called.

Either fix, remove, or leave TODO as a NOTE if necessary.

We need to have a modicum of branding and design for the documentation/site, at least to the level Deft has for legitimacy. Do so. This is dependent on a name choice.

There was some refactoring of the token and base service and we probably need to deprecate or remove most of it from the base service.

We need to create a site for the mvc module. Either a sub-domain of git, or a new domain. This needs to include all of the documentation as well as links to here and our site + contact info.

The 3rd parameter for addEventListener needs to be optional. Look into either using Ext.bind or something else as the most common use case will be using 2 parameters and expecting it to work like Flex.

Flow is only usable with Open source projects ATM. This is due to the commercial licence agreement terms.

Since there is in fact quite a bit of boilerplate code, what if Ik whipped up a quick generator (with ExtJS of course and packaged with their native desktop packager) that created Models, Stores, Events, Controllers, Services, Mock Services?

Needs basic unit tests.

Basic unit tests.

A TodoMVC application would be nice as well. Those are pretty to visually point out the differences between frameworks. Backbone and Angular's version of TodoMVC are pretty telling for example. Comparing with Deft's would help.

http://todomvc.com/

Finalize package path and naming structure for framework. Considering tooling is a challenge, the shorter the better, but not so much to be unreadable. Part of the solution vs. the problem and all that. This is dependent upon choosing a name.

See if we can either make it easier to wrap Log4JavaScript, or use Ext, or both without having our framework beholden to our customized verison in case someone doesn't want to use it. Will assign to Brian once complete.