lavaca

lavaca copied to clipboard

Only allows one level of nesting right now, but feel free to change/optimize for that or in other ways. I just really wanted this feature.

loganthompson

Currently Cordova's "deviceready" event seems to be limited to a one-time callback. It might be nice to have this work like jQuery's document.ready, which accepts multiple invocations and tracks "load",...

zship

Look into having before/after methods for Controller routes

1

Brought up in the Lavaca meeting: example given was doing authentication before routes execute.

zship

Remove util/extend and use prototypal inheritance

1

This is a big one because this is Lavaca's classical inheritance mechanism. My argument for removing it would be to reduce complexity by removing one level of abstraction. It also...

zship

Remove mvc/View#mapChildViewEvent

6

I'd like to know if anyone knows what this is for. Doing a `git blame` shows that Kelly added it under 7c64abd "refactoring view classes..." Of the projects [PropertyCross, autotrader-web,...

zship

Make rendering process synchronous

1

This has always bugged me. I've always wondered why we use Promises in these places: `mvc/View#render` `mvc/View#renderPageView` `mvc/View#renderTemplate` `mvc/ViewManager#load` These sorts of things have never required asynchronicity for me. Turns...

zship

Replace net/History with standard window.History

1

Older browsers could use a polyfill. Files which depend on net/History: lavaca/src/mvc/Application.js lavaca/src/mvc/Router.js lavaca/src/mvc/Controller.js lavaca-starter/src/www/js/app/app.js lavaca-starter/src/www/js/app/ui/views/BaseView.js These would need to be checked to conform to the [History API](https://developer.mozilla.org/en-US/docs/Web/API/History).

zship

There are plenty of arguments out there against singletons (check the [Wikipedia article](http://en.wikipedia.org/wiki/Singleton_pattern), second paragraph), but my main beef is that they're impossible to subclass and they make it possible...

zship

Per the Lavaca meeting today, we'd like to split the code under fx/\* into a separate repo. This would be part of a larger effort to keep the main library...

zship

The path that a route takes from a url change to a View rendering seems a bit complex to me: `(init/popstate event) -> Router#exec -> Route#exec -> Controller#(method) -> Controller#view...

zship