Skip to content
This repository

Nov 28, 2013

  1. TransitionPanel: "current child" variable was not correclty updated

    The view overrides the "showChild" function to queue up transitions,
    with a view to running only one transition at any given time. It
    did not update the "currentChild" parameter accordingly, meaning
    further transitions did not start from the right view.
    authored November 28, 2013
  2. Transition/Swipe: unknown transitions, event handlers undelegation

    The transition panel crashed when a non supported transition was
    requested. Unknown transitions are now properly converted to "no"
    transition.
    
    The touch event handlers that the slidepanel view attached to the
    slide container are now properly unbound when the content is replaced
    one way or the other to enable garbage collection and avoid side
    effects.
    
    The transition panel also triggers a "transitionend" event (was
    "transitionEnd") to be more consistent with the DOM event it relates
    to.
    authored November 28, 2013
  3. Card panel: ensured only "first" child is shown at first

    The view rendered all children without selecting the current child,
    meaning that all cards typically appeared on screen until a call to
    "showChild" eventually hid away other cards.
    
    The view now picks up the "first" child, or rather the first name
    it finds when it enumerates the keys of the list of children. Note
    that this order is not guaranteed in theory, it just happens to be
    fairly consistent across runtimes...
    authored November 28, 2013

Nov 26, 2013

  1. SlidePanel: re-written to add native support for swipe interactions

    The SlidePanel view now extends TransitionPanel, restricting
    supported transitions to slides. It also supports swiping among
    views in any direction.
    
    The position of the children views is dynamic. The view calls the
    "getTargetChild" function when it starts a swipe in a direction to
    retrieve the name of the child view that it should position and
    transition to. That function should typically passed to the view
    when it is created, or be overwritten in derived classes.
    
    On top of the "getTargetChild" function, two parameters can be set
    when the view is created:
    
    - "swipeThreshold": the minimal horizontal/vertical distance that the
    user finger must move before the view decides to start a swipe in the
    requested direction. In pixels. 5 by default.
    
    - "swipeChangeThreshold": the minimal distance that the user finger
    must have moved at the end of the swipe for the view to consider that
    it should transition to the target child. In percent (of the width or
    height, depending on the direction). 30 by default.
    
    Beware: as with TransitionPanel, the view now creates two div levels
    instead of just one as before, one flagged "joshfire-outer" and the
    other flagged "joshfire-inner".
    authored November 26, 2013
  2. Transition panel: "transition:end" event renamed "transitionEnd"

    The commit also exposes the "positionSlides" function that positions
    the target slide next to the original one and hides all other views
    in preparation for a slide transition. This will be useful for the
    "SlidePanel" derived class.
    authored November 26, 2013
  3. CardPanel: first child displayed by default

    The view displayed all children one after the other. It now picks up
    the first child by default when it gets rendered for the first time.
    authored November 26, 2013

Nov 25, 2013

  1. Transition panel: now using infinite translations to avoid flickering

    The transition panel does not reset the viewport position anymore
    after transition to avoid flickering effects on some devices.
    
    The panel now also triggers a "transition:end" event when the
    transition is over. Only one transition may run at a given time.
    authored November 25, 2013

Nov 14, 2013

  1. Updated Woodman library to latest version (v0.9.0)

    This brings in fixes for possible precompiler crash conditions in
    particular.
    authored November 14, 2013

Sep 24, 2013

  1. François Daoust

    Merge pull request #48 from dieppe/master

    Remove symlink to joshfire-framework in map example.
    authored September 24, 2013
  2. Remove symlink to joshfire-framework in map example.

    Use a symlink to joshfire-framework/lib instead.
    
    This allows cordova-cli to copy the folder when adding a platform
    (otherwise, the symlink is followed an infinite time...)
    authored September 24, 2013

Sep 20, 2013

  1. François Daoust

    Merge pull request #47 from dieppe/master

    Moved the "update" method from UIItem down to View.
    authored September 20, 2013
  2. Move the update method from UIItem down to View.

    authored September 20, 2013

Sep 04, 2013

  1. Do not break the prototype chain when extending iScroll

    authored September 04, 2013

Aug 13, 2013

  1. Dynamic container: restricted updates to "final" collection events

    The dynamic container may decide to update its child based on changes
    made to an underlying collection. The class used to listen to all
    possible change events, including e.g. "add", but these events may
    be followed by other similar events.
    
    If the class decided to create a List once it received a first "add"
    event, the List would be initialized with a complete collection
    (all items would already be present) but would still receive the
    following "add" events, making it think that new items are being added
    to the collection.
    authored August 13, 2013

Jul 30, 2013

  1. athibaud

    [optimize script] renamed minify arg to prettyprint

    which makes a more sensible default. defaults to false if not set.
    authored July 30, 2013

Jul 29, 2013

  1. athibaud

    [optimise script] minify option is a boolean, not a value

    --optname [optvalue] means you want a value for the option
    --minify is a boolean so doesn't require a value
    authored July 29, 2013

Jul 25, 2013

  1. Arthur Jamain

    Reverts the minifying condition ...

    ... That i've broken in hte first place. Noone reads the second line of a commit anyway. Right ? ...
    authored July 25, 2013

Jul 17, 2013

  1. Arthur Jamain

    Nothing to see here ...

    authored July 17, 2013

Jul 15, 2013

  1. Arthur Jamain

    Added commander support. This allows for CLI options...

    Which enables us to specify options in whichever order we want and be a little more explicit about it. Retro compatibility tests remain to be done for this version.
    
    Also added support for several new options which allow the user to specify a device, formfactor, etc. without having to specify a complete user agent.
    authored July 15, 2013
  2. Arthur Jamain

    Added commander as a dependency

    authored July 15, 2013
  3. Arthur Jamain

    Added devicedetect lib...

    The point is to let the developper define multiple implementations of a class for a panel of devices. The plugin lets the dev require a file and will load the correct ones according to tests designed by the dev. These tests/mappings will be covered in another commit (namely on the boilerplate project.)
    
    devicedetect provides a runtime object to the dev for him to run tests. It does so by parsing the client's UA using UAparser (hence its inclusion) when it is run unoptimized. Otherwise, UAParser is still used in nodejs to - if necessary - parse a UA string that has been provided as a CLI argument to the optimizer script.
    
    This is necessary since we can't fully rely on the adapter variable anymore - we seek to handle multiple formfactors, os or constructor which gets a tad complicated.
    authored July 15, 2013
  4. Arthur Jamain

    Added path declarations to require.config...

    ... In all the adapters. This is used by the upcoming devicedetect plugin so that require can load it correctly. devicedetect is the actual plugin, runtime is a lib loaded by the plugin which provides insight about the app's runtime. runtime's path is swapped at optimization so it points to a simple JSON instead.
    authored July 15, 2013

Jul 04, 2013

  1. Arthur Jamain

    Changed the way onscrollhandler is bound

    authored July 04, 2013
  2. Arthur Jamain

    If there is already an onScroll function in the class, don't override…

    … it with null
    authored July 04, 2013

Jul 03, 2013

  1. Arthur Jamain

    Quickfix : only the entries are expected in the success callback

    authored July 03, 2013

Jul 02, 2013

  1. Arthur Jamain

    Small mistake in export of the module

    authored July 02, 2013
  2. Arthur Jamain

    Added a UA-based device identification function

    authored July 02, 2013

Jul 01, 2013

  1. Florian Cargoët

    Added some bing options, remove magic zoom pan feature

  2. Florian Cargoët

    Safer call to render callback

    Since render didn't have parameters before, it's sometimes passed as an event handler "as is". When that's the case, render() receive the event arguments.

Jun 27, 2013

  1. Map / Bing : handle the 'disableDefaultUI' option

    And remove dashboard, scaleBar, and mapTypeSelector
    authored June 27, 2013
  2. François Daoust

    Merge pull request #46 from joshfire/map_wip

    Map View : Google, Bing & OSM Support
    authored June 27, 2013

Jun 26, 2013

  1. Add a map example

    ./examples/map/index.html
    
    Demo :
    Different providers (Google, Bing, OSM over Google)
    Changing Zoom
    Changing location
    Adding/removing markers
    authored June 27, 2013
  2. Map UI Refactoring + Bing & OSM Support

    OSM is supported through Google Maps
    
    Map API :
    * addMarker ({lat:float, lng:float})
    * addMarkers ([marker*])
    * removeMarker(marker)
    * clearMarkers()
    * setCenter({lat:float, lng:float)
    * getCenter()
    * setZoom(int)
    * getZoom
    * moveToLocation ({lat:float, lng:float})
    * panTo({lat:float, lng:float})
    
    Function names are still a bit weird.. Sorry about that. It's part coming from the old framework, part from the mess it was.
    
    Everything *should* be OK. Fixed a few things which were not working (events publishing using the old fashioned way for example).
    
    I'm adding an example page too.
    authored June 27, 2013

Jun 25, 2013

  1. Map : add api key when injecting google maps script

    authored June 25, 2013
  2. OSM (partial) support

    Support OSM tiles, displayed over a google maps, and using GMaps API
    
    Use
    {
    provider:'osm',
    mapType : 'default' || 'toner' || 'mapbox'
    }
    authored June 25, 2013
Something went wrong with that request. Please try again.