• This repository has been archived on 09/May/2021
  • Stars
    star
    283
  • Rank 146,066 (Top 3 %)
  • Language
    JavaScript
  • Created about 14 years ago
  • Updated about 9 years ago

Reviews

There are no reviews yet. Be the first to send feedback to the community and the maintainers!

Repository Details

Reduces the amount of code you need to write when using Appcelerator Titanium. Adds support for JSS, localization, default properties, and more.

Redux has a simple goal: To reduce the amount of code you need to write when using Appcelerator Titanium.

To use its features, include the redux.js file at the top of your app.js or Alloy.js:

require('redux').inject(this);

build status

FEATURES

SHORTHAND FOR COMMON FUNCTIONS

Some functions you use all the time. Redux makes them shorter, and easier to type.

Normal Code

Titanium.API.info('hi');
Titanium.API.error('hi');
Titanium.API.warn('hi');
Titanium.API.log('info', 'hi');
Titanium.UI.currentWindow;
Titanium.UI.currentTab;

Redux Code

info('hi');
error('hi');
warn('hi');
log('info', 'hi');
currentWindow(); // or...
win();
currentTab(); // or...
tab();

Note that currentWindow, win, currentTab, and tab are all functions that return a reference to Ti.UI.currentWindow or Ti.UI.currentTab. This is necessary because the current window and tab can change as you open and close windows. By making them functions, you always have access to the real "current" window or tab.

UI CONSTRUCTION

Create new Ti elements using the new Constructor() syntax you're used to in JavaScript. Note that by making your elements this way, you also get to take advantage of other Redux features like JSS, default properties, and more. You can use this syntax for any element normally created using the syntax Ti.*.create*. For example, Ti.Network.createHTTPClient() or Ti.UI.createLabel() could instead be new HTTPClient() or new Label(), respectively.

Normal Code

var label = Titanium.UI.createLabel();

Redux Code

var label = new Label();

Warning Titanium optimizes your installation packages based on what Titanium elements you use. By using redux, it can't tell which to include or exclude. But we can fix this easily by giving it blatant hints in our app.js, like this:

/* Trick Titanium into including the packages we want */
var used = [Titanium.UI.createLabel, Titanium.UI.createWebView, Ti.Platform.locale];

Now we can use the short redux constructors and locale constant in our RJSS without worrying about Titanium accidentally excluding something we are using.

Note that we put them in a "used" array so that JSLint won't complain.

USING EASY CONSTRUCTORS AND STYLING ON YOUR OWN OBJECTS AND MODULES

Module support is really easy to add to redux:

Redux Code

var Paint = require('ti.paint'); // include the paint module
redux.fn.addNaturalConstructor(this, Paint, 'View', 'PaintView');
var paintView = new PaintView(); // eq to calling Paint.createView(), but with RJSS applied!

There is full RJSS support for these newly created natural constructors. That means you could put a style like the following in your RJSS, and it would get applied to the object we just made:

Redux RJSS Code

PaintView { backgroundColor: 'red' }

Styling your own objects with RJSS is very straightforward, if you don't want to add the full easy constructors:

Redux Code

var args = redux.fn.style('Label', { id: 'Label1' });
// args is now a plain object with all your RJSS included
// pass it to a normal label creation call:
var styledLabel = Ti.UI.createLabel(args);

UI PROPERTY DEFAULTS BY ELEMENT TYPE

You can specify default properties for your UI elements. This lets you specify properties in one place, and for multiple elements. This is especially useful for application wide settings, like fonts and colors, but also useful to help you keep your design logic out of your business logic. Note that property defaults by element type are considered less important than property defaults by ID or properties passed in to the constructor, and can be overridden by either of these.

Normal Code Not Supported

Redux Code

Label.setDefault({ font: {fontWeight: 'bold' } });
var label = new Label();
alert(label.font.fontWeight == 'bold');

UI PROPERTY DEFAULTS BY SELECTOR

Using a similar method to setting UI Property Defaults by Element Type, you can set them for your UI elements by their IDs or class names. Note that property defaults by ID are considered more important than default properties by element type and class names, and will override them.

Normal Code Not Supported

Redux Code

$.setDefault('#myID', { text: 'Hello, World!', color: 'red' });
$.setDefault('.myClassName', { font: { fontSize: 12 }, color: 'green' });
var label = new Label({ id: 'myID', className: 'myClass', color: 'blue' });
alert(label.text == 'Hello, World!');
alert(label.color == 'blue');
alert(label.font.fontSize == 12);

EVENT BINDING

Bind events in a more natural way. Note the wrapping $() and the fluent calls.

Normal Code

var button = Titanium.UI.createButton({ title: 'Click Me!' });
button.addEventListener('click', function() { alert('clicked!'); });
button.fireEvent('click');
button.fireEvent('click', {src: 'me'});

Redux Code

var button = new Button({ title: 'Click Me!' });
$(button).click(function() { alert('clicked!'); })
     .click()
     .click({src: 'me'});

You can add support for custom events. Normal Code

button.addEventListener('myCustomEvent', function() { });

Redux Code

$.addEventBinder('myCustomEvent');    // only needs to be called once, then can be used again and again
$(button).myCustomEvent(function() { });

RJSS

RJSS, or Redux JavaScript Style Sheets, let you create CSS-like rules to style your UI elements. Note that RJSS can only style elements you create using Redux's method of creating elements, and that this isn't actual CSS.

Normal Code Not Supported until Version 1.5

Redux Code for Including RJSS from your app.js (or any .js file)

includeRJSS('common.rjss');

Redux Code for Styling Elements from common.rjss (or any .rjss file)

Window {
    backgroundColor: '#fff'
}
/* add comments! use familiar c style comment blocks like this one */
Label {
    backgroundColor: '#faa',
    color: '#333'
}
/* add an attribute that will act as a filter */
[Ti.Platform.osname="android"] Label {
    backgroundColor: '#aaf',
    color: '#666'
}
/* select by id */
#HelloWorld {
    left: 15,
    right: 15,
    height: 70,
    top: 50
}
/* by className */
.myClassName {
    text: 'Set by class name'
}
/* by multiple selectors */
.selector1, #selector2, Label {
    text: 'Set for all three selectors'
}
/* attribute with its own block */
[Ti.Platform.locale="en"] {
    #HelloWorld {
            text: 'Hello, World!'
    }
    .myClassName {
        text: 'Set by class name'
    }
}
[Ti.Platform.locale="es"] {
    #HelloWorld {
        text: 'Bienvenido, Mundo!'
    }
    .myClassName {
        text: 'Establecido por el nombre de clase'
    }
}
/* variables */
$background = 'white';
Window {
	backgroundColor: $background
}

Here are some key features of RJSS to note--you'll want to use them:

  • Include as many .rjss files as you need to keep yourself organized.
  • Have as many rules as you need.
  • Have multiple rules for a single element.
  • Attributes can contain ANY valid Javascript -- [true], [false], [new Date().getDay()=1], as long as you don't use square braces [].
  • Attributes can work negatively too -- [Ti.Platform.locale!="en"]
  • White space doesn't matter; put it where you want it.
  • You can localize your app using the [Ti.Platform.locale="language"] attribute.
  • The includeRJSS function can take in multiple files or just one.
  • ID rules have higher precedence than className rules, which have higher precedence than element rules.
  • Chain selectors to reduce the amount of RJSS you need to write -- Window, Label { backgroundColor: '#fff' }.
  • Attributes can have code blocks so they control multiple rules -- [Ti.Platform.osname='iphone'] { #foo {} #bar {} }.
  • Chain attributes for more complicated rules -- [Ti.Platform.osname="iphone"||Ti.Platform.osname="ipad"] Window { backgroundColor: '#bef'}.
  • Specify multiple class names on your objects -- className: 'big_text red_text'.
  • Add comments to your RJSS using /* and */. Note that // comments are not supported.
  • Variables must start with a $, and end with a ;. They must be valid JavaScript variable names.

RJSS COMPILATION

To compile RJSS with your app, you must update your tiapp.xml and copy the "plugins/redux/plugin.py" folder from this repository in to your app's directory.

For example, look at the "test" app included in this repository.

Now edit your tiapp.xml, inserting this "plugins" element:

<plugins>
    <plugin version="1.0">redux</plugin>
</plugins>

DYNAMIC STYLING

You can apply RJSS to elements after they are created. For example, you can use this to toggle a button between two classNames when the user touches it.

Normal Code Not Supported

Redux Code

var button = new Button({ className: 'Off' });
$(button).applyStyle('Button', { className: 'On' });

CONTACT INFORMATION

Redux was made by Dawson Toth from TothSolutions, LLC. (www.tothsolutions.com). TothSolutions, LLC. uses Appcelerator every day to create mobile applications for its clients, and created Redux to ease that process and give back to the community that created Appcelerator.

We can be contacted through our website -- www.tothsolutions.com/Contact

Since making Redux, I was hired by Appcelerator, Inc. I'm now a full time engineer with them. Note that this doesn't mean Redux is officially supported. If you have issues, PLEASE work to figure it out on your own, and then submit a PR!

Don't contact Appcelerator with issues, just report it here: https://github.com/dawsontoth/Appcelerator-Titanium-Redux/issues/new

LICENSE

Copyright (c) 2014, Toth Solutions, LLC.

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.