trabian / titanium-backbone Goto Github PK

Ctrl-c on the cake process fixes it, so it must be something that's not being released properly.

Recent additions have allowed us to move most of the Titanium-specific functionality out of the base View class to Backbone.$. With that change it should be possible for View classes to extend Backbone.View directly instead of a base View class:

Current:

View = require 'tb/views/base'

class Button extends View

Goal:

class Button extends Backbone.View

Currently tb/views/base is responsible for:

• setting Backbone.$ to ti.$
• aliasing tagName to viewName
• setting the default viewName to 'View'
• Overriding _configure to merge attributes passed via the constructor

These should be easy to include in Backbone.View via composition rather than inheritance.

Now that Pixate is free it might be a better solution than our custom CSS styling. We should at least do a quick spike on it.

https://github.com/Pixate/Titanium-Pixate

Backbone uses $.ajax(options) instead of $.ajax(url, options), which is certainly understandable. We need to support this method of calling $.ajax as well.

Should we setup a discussion list? Some matters doesn't fit the issues. For example, have you guys looked at kranium? It integrates backbone and a lot of other stuff. It's open source too. Maybe we could learn some lessons from it, or even fork it. I don't know.

Running

$ sudo npm install -g

I got the following error:

https://gist.github.com/2819925.js

The goal is to make titanium-backbone-ks runnable directly instead of running it as a module of titanium-backbone.

Match API of http://api.jquery.com/removeAttr/

This should support:

• Basic http requests
• Deferreds
• As many of jQuery's $.ajax settings as possible (see below)
• Global setup via $.ajaxSetup()

Supported Settings

• accepts
• async (Only supported on iOS according to the Titanium documentation)
• beforeSend
• cache
• complete
• contents
• contentType
• context
• converters
• data
• dataFilter
• dataType
• error
• global
• headers
• ifModified
• processData
• statusCode
• success
• timeout
• type (also method)
• url
• xhrFields

To consider:

• password
• username

I don't know if its a problem with the build script or with stitch-up but, after running

titanium-backbone new myapp
cd myapp
npm install

I get the following error:

/path/to/myapp/node_modules/titanium-backbone/node_modules/stitch-up/lib/utils/merge.coffee:51
for (_i = 0, _len = deps.length; _i < _len; _i++) {

@svallory and @tonydewan have both been part of discussions regarding the project name. I'm no huge fan of titanium-backbone but haven't really come up with an alternative.

What about keeping the name as 'titanium-backbone' but shortening the command to 'tb'? Any other ideas?

Backbone.stitckit is a library for binding models to views:

class SampleView extends Backbone.View

  # Any time the `name` attribute of @model is updated, the text of the element matching .name will be updated as well.
  bindings:
    '.name': 'name'

It would be helpful to have this integrated with titanium-backbone.

For example:

View = require 'tb/views/base'

$ = Backbone.$

module.exports = class Window extends View

  viewName: 'Window'

  attributes:
    layout: 'vertical'
    backgroundColor: '#'

  events:
    'click Button': 'showAlert'

  showAlert: ->
    alert 'click'

  render: ->

    $('<Button>')
      .attr('title', 'Testing')
      .appendTo @$el

    $('<Label>')
      .attr('text', 'Test Label')
      .appendTo @$el

    @

If I click on the button then the alert shows as expected. If I click anywhere else then I get the following error:

Script Error = Can't find variable: context at app-impl.js (line 5017).

The offending code is in closest():

      closest: function(selector) {
        var node;
        node = this[0];
        while (node && !_matches(node, selector)) {
          node = (node !== context) && node.parent;
        }
        return $(node);
      },

It looks like I accidentally copied over the 'context' variable even though we're not using context yet.

This looks promising: https://github.com/omorandi/TiInspector

Ti Inspector allows debugging Appcelerator Titanium applications in the Chrome DevTools web interface.

It shouldn't require any additions to the titanium-backbone framework but could make its way into our documentation as a recommended tool.

It would be nice to be able to use the normal Titanium build tools without needing to use a Cake (or Make or ...) task.

Here's info on how to do that: http://appersonlabs.com/2013/04/12/titanium-build-plugins-in-sdk-3-x-x/#.UeVhXmRgbAU

This is likely because table views do not treat children the same was as other views. This is particularly an issue when styling a table.

Some views such as TableViews only handle special types of children (e.g. TableViewRows and TableViewSections as children of TableView). In the case of TableView the name of the method used to add these special children is appendRow and appendSection.

$.append should use the appropriate method depending on the type of container being added to and should throw an exception if the view being added is not acceptable or if the container should not accept any children.

Non-containers

• Throw an error on 'append' for these view types.

Views that are not intended to act as containers for other views:

• ActivityIndicator
• Button
• ImageView
• Label
• ProgressBar
• SearchBar
• Slider
• Switch
• TextArea
• TextField
• WebView

Special-purpose containers

• ButtonBar and TabbedBar should not accept append with a child view because items are added as elements of a special-purpose 'labels' array.
• Picker can only hold PickerRows and PickerColumns, which are added using the add method. Throw error if anything else is added.
• TableView is a specialized container for TableViewSection (appendSection and deleteSection) and TableViewRow (appendRow and deleteRow) objects. Throw error on others.
• TableViewSection is a specialized container for TableViewRow objects, which are added using the add method. The add method on TableViewSection can only be used to add TableViewRow objects.
• Toolbar is designed to hold buttons and certain other controls, added to its items array.
• The Tab, TabGroup, NavigationGroup and SplitWindow objects are special containers that manage windows and should not be added to arbitrary views.

With changes in the 'refactor' branch, the README is no longer accurate. It should include:

• A summary of the purpose and motivation of the framework
• An overview of the current status of development
• Instructions for:
  • Installation
  • Running the tests
  • Running the kitchen sink

Also acceptable would be links within the README pointing to this information within the wiki.

I would like to be able to create views using a template engine such as jade. This might look something like:

View.heading
  Label This is a heading
  Label= subheading
Button Click me!

template = require './template'

class SampleView extends Backbone.View

  render: ->

    @$el.append template { subheading: 'And this is a subheading' }

    @

This has proved to be a very helpful pattern when building Backbone apps on the web and should be fairly easy to implement in titanium-backbone.

As a first step we should extend the $('') creation syntax to support attributes, nesting, and text nodes:

Update $('') syntax to support:

• Attributes: $("<View height='50''>")
• Nesting: $("<View><Label height='20' /><Button title='Click me!' /></View>")
• Text nodes: $("<Label>Label Text</Label>") should create a label with a text attribute of 'Label Text' while $("<Button>Click Me!</Label>") should create a button with a title attribute of 'Click Me!'