Implement the option of re-rendering all or a portion of a view's template.

We need to return the timeout id when using Lavaca.delay

x-dust 0.5.3 fixes a breaking issue with Android 2.x

A utility method for assembling query-string URLs should be included as part of StringUtils.

Uncaught RangeError: Maximum call stack size exceeded
ns.Promise.Lavaca.extend.succeeded
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get
ns.Translation.get
app.onOfflineAjax
_onAjaxError
ns.Promise.Lavaca.extend.error
ns.ajax
ns.Map.Disposable.extend.load
ns.Map.Disposable.extend.get

Would like to be able to pass models and/or configuration options to widgets when initializing them using Lavaca.mvc.View#mapWidget

iOS app icons and startup images need to be revisited. Current implementation doesn't seem to fully work and we also need to update to include iPhone 5's new screen dimensions.

This seems to be a good resource for a comprehensive solution:
https://gist.github.com/2222823

In the sink app, the 'sign in' view is created on layer 1 so that it comes on top of the other existing view, but because the dom is rendered with the animation class already attached, the animation doesn't happen.

What I believe would help in adoption of the framework is creating a tutorial page on getlavaca.com that would walk people through creating a simple to do app. doesn't necessarily have to be to do mvc specs, but something that will use a good portion of the fucntionality needed to begin building an application.

You should be able to pre-compile your templates and have Lavaca automatically pick them up and create instances of the appropriate template class.

Basically this would just be a shortcut so we won't always have to type collection.add.apply(collection, [...])

It's a pain point to manage the correct order of all script files. It'd be nice to switch to a require.js-style setup where dependencies are managed fluidly, and to tie this into the build system.

Would like to see a way to have Lavaca.mvc.View and Lavaca.ui.Widget automatically unbind their handlers when disposed. Use case is binding event listeners to a Lavaca.mvc.Model/Collection then needing to manually unbind those handlers when the user transitions to another view (see Todos sample app)

PhoneGap 1.9.0 is out now, Lavaca is on 1.6.0 still. Should be updated.

Lavaca.mvc.View should support events that fire when the view enters or exits (maybe along with beforeenter and beforeexit?)

currently the view itself is re-rendered, but the views inside the view are not

Things that must be included:

• New templating system, syntax changes, and how to switch back to x-dust
• Computed properties.

Need documentation on how to setup a new project from the Spring MVC version of Lavaca.

When you create a new Lavaca.mvc.Collection type and assign its TModel property to be another Lavaca.mvc.Collection type, the collection does not instantiate its child collections as expected.

Lavaca.mvc.Collection's fetch method is currently expecting a JSON array back from the server, even though Collection is capable of supporting additional data. Would like to see support for this format:

{
"attr1": "foo",
"attr2": "bar",
"items": [
{
"id": 1
},
{
"id": 2
}
]
}

If no easing is provided the callback doesn't get called.

if (easing instanceof Function) {
      callback = easing;
      easing = null;
 }

This block of code should be moved outside of the isSupported test

Given that we are getting rid of Widgets and instead allowing views to contain other child views, we should port existing widgets over to this new system.

Implement client-side code to execute a route when the page is initially loaded or is refreshed.

When jQuery is used in noConflict() mode, Lavaca.env.Device breaks because it contains a $ that isn't imported from Lavaca.$

Line 478:

should be:

Using the touch function in the following manner without a delegate does not seem to work
el.touch(self.dragStart, self.dragMove, self.dragEnd, self);

If I use a delegate in this manner, it does work
el.touch('.item', self.dragStart, self.dragMove, self.dragEnd, self);

When replacing the current history state and the app is set to use hash-tag history mode, the browser back button will no longer let the user go backwards in history.

Could be useful for hiding/showing certain things based on the current environment, or displaying values such as build number.

When using jQuery instead of Zepto .remove() removes the event handlers. It can be resolved by substituting .detach() for .remove() in the view.

Allow setting a data-external attribute on anchor tags that indicates that the link points to an external page and should not be handled with the router (as suggested by @sindresorhus). This should be a more semantic way of doing this than the current way of setting rel="nofollow" or target="_blank", although both of those methods will still work.

IE10 touch uses slightly different event names. It would be nice to support these to make Lavaca even more cross platform

Scenario: You have a collection of multiple paths, each of which is a collection of multiple points, each of which is a model with X and Y attributes that indicate position. Assuming that the collection of paths is the data passed to the view, it'd be nice if there was a way to map events from the view to the individual points without having to iterate through the paths. Problem is that if you have to manually update event handlers when the view is disposed or when paths/points are added/removed.

Not all Android devices will test as Android devices with the checks currently being done in the framework.

In order to easily check the status of the model

Add support for attributes that are computed and returned via a function.

Should follow the underscore _.sortBy pattern, where you can pass either a string to sort by that attribute, or a custom iterator function. Would also be nice to have an Ascending/Descending parameter.

The view's exit method fails to execute on Android 4.1. This is the result of the "self" variable not being set correctly in the app.ui.BaseView#exit method when animation is disabled.

Should not have fully qualified names on all methods/fields, only on static ones.

We should introduce a generic UIElement type that could serve as the super type for UI types like Lavaca.mvc.View and Lavaca.ui.Widget and features event mapping.

Pending release of Cordova 2.2

It seems like you would want the enter event to wait until the animations that bring in the view to animate to completion. For example, if you want to focus the cursor in the first field of a form and you do it on enter, it currently places the cursor during the animation and results in a sloppy entrance.

It's a pain point to have to reference script and style files in both the index.html and in the scripts.xml and styles.xml. The build process should be tweaked to be able to automatically pull the JS and CSS files from specially annotated sections of the index.html.

Would be nice for history state change and routing to be more extensible, so that a history change event could be intercepted or claimed by the view. This would be useful in having the back/forward buttons navigate between tabs on a page.

Page transitions (particularly on the "Sign-In" panel in the Sink app) are jumpy in iOS 6 Beta 3. Need to keep an eye on this as the betas are released.

Currently, the sample apps are passing around view column properties on the model. This messes with using Lavaca.mvc.Model objects directly for the views. We should just make column a property on the view.

Documentation needs to be generated from the Lavaca Spring library.

Would like to see the Python x-dust library used with Atnotate to generate full HTML versions of the docs instead of using the JS version of x-dust to do client-side HTML generation from JSON data.

The default Lavaca.mvc.Application#onTapLink should handle links with target="_blank"

We will still have a build method to include xdust in cases that it is needed

On Android devices, routes with multiple variables in their patterns are only parsing every other variable.