Skip to content
Commits on Oct 17, 2011
  1. @joseph
  2. @joseph

    Merge pull request #66 from joseph/transitions

    Smoother transitions and animation in more browsers. Fixes #2.
    joseph committed Oct 16, 2011
Commits on Oct 14, 2011
  1. @joseph
  2. @joseph
  3. @joseph
  4. @joseph

    Workaround for iPad's sticky slideOut.

    Not much return for four hours work.
    joseph committed Oct 10, 2011
  5. @joseph
  6. @joseph

    Tidying a few Reader constants.

    AbortMessage now supplanted by monocle:incompatible.
    joseph committed Oct 10, 2011
  7. @joseph
  8. @joseph

    Less ugly and less obtrusive Slider wait control.

    I've always hated it. Now should only appear if the next page is
    actually taking a while to set (because it has a slight transition on
    the opacity, so near-zero setPage times shouldn't ever let the opacity
    reach 1). Need to test this on slower devices.
    joseph committed Oct 9, 2011
  9. @joseph

    Removing more superfluous defers and speeding successive turns.

    There's no point stacking the various style changes successively -- all
    of them will be applied on the next defer. So, just ensure there is a
    single defer before announcing the page change.
    
    Also, we can make the slide faster if there's been another slide very
    recently -- the user is obviously paging through the book quickly; let's
    not get in their way.
    joseph committed Oct 9, 2011
  10. @joseph
  11. @joseph
  12. @joseph
  13. @joseph
  14. @joseph
  15. @joseph
  16. @joseph
  17. @joseph

    Translating frame body in 3d too flickery. New iOS fix for blank slider.

    This one involves switching the order in which "onGoingBackward" works.
    Seems to have given a bit of a speed boost too.
    joseph committed Oct 14, 2011
Commits on Oct 10, 2011
  1. @joseph

    Must nuke padding and margins on body.

    Otherwise page dimension calculations get blown out on iOS WebKit.
    joseph committed Oct 10, 2011
Commits on Sep 23, 2011
  1. @joseph
  2. @joseph
  3. @joseph

    API-CHANGE: controlshow/hide events now prefixed with monocle:

    If you are listening to these events, you need to update your code to
    listen to 'monocle:controlshow' and 'monocle:controlhide' instead.
    
    The 'evt.m' object is no longer the control object itself -- it's now an
    object with a 'control' property, whose value is the control object.
    
    This brings these two events into conformance with other Monocle custom
    events.
    joseph committed Sep 23, 2011
  4. @joseph

    Wait for a monocle:turn event before dispatching monocle:loaded.

    I think this fixes #57, but I haven't been able to completely reproduce
    it. See the test/events/index.html test in particular.
    joseph committed Sep 23, 2011
  5. @joseph
Commits on Sep 15, 2011
  1. @joseph
Commits on Sep 14, 2011
  1. @joseph

    eInk panel now supports keyboard events, and clicking backwards.

    Clicking on the left half of the page now goes backwards; right half
    goes forwards. PageUp/PageDown are registered to backwards/forwards
    respectively.
    joseph committed Sep 14, 2011
  2. @joseph
  3. @joseph

    Define locus objects with CSS selector strings.

    Much like the XPath support in locus objects, if you create an object
    like { selector: 'p:nth-of-type(3)' }, you can jump to that element in
    all open pages.
    joseph committed Sep 14, 2011
Commits on Sep 13, 2011
  1. @joseph
  2. @joseph

    eInk Panel (supports Kindle3).

    If you provide a flipper option and/or a panel option to Monocle.Reader,
    these ALWAYS apply -- the legacy flipper no longer overrides it. So if
    you do provide these options, it's up to you to inspect the browser
    environment beforehand (such as by calling Monocle.Browser.survey
    manually) and provide the appropriate option.
    
    But by default, the legacy flipper is given to non-column browsers, and
    the instant flipper is given to eInk browsers. The instant flipper will
    by default assign the eInk panel to these browsers too.
    
    Also, Browser.env.isCompatible(). Monocle now aborts and fires
    "monocle:incompatible" if a browser fails to pass this test. You can
    stop this event if you want to handle it yourself.
    
    floatsIgnoreColumns workaround is back in effect.
    joseph committed Sep 13, 2011
  3. @joseph

    Refining column width calculations.

    iOS3 needs to have a scroll value applied before the style takes effect,
    which is pretty weird.
    
    Also removed the old "flickerOnJump" workaround - I think this was only
    a problem for early Snow Leopard. Impossible to test for now.
    joseph committed Sep 13, 2011
  4. @joseph

    Apply all CSS modifications to body at once.

    This decouples component measurement from page turns. Components are now
    measured on change and whenever Reader#recalculateDimensions is
    explicitly invoked.
    
    Still a bit of a work in progress, as there are some problematic race
    conditions on slower devices.
    
    This change also fixes #22, making componentchange fire when all style
    changes and measurements have been made to the component (at least,
    that's the theory).
    joseph committed Sep 13, 2011
  5. @joseph

    Detecting body width clipping.

    Improving the iframe-scroll-dimensions test to illustrate the problems
    of detecting component scrollWidth in Gecko in particular.
    
    Also includes a "full-screen" version of the Rabbit showcase. This
    provides a simple test where browser resizing or reorientation has an
    effect.
    joseph committed Sep 13, 2011
Commits on Sep 10, 2011
  1. @joseph
Something went wrong with that request. Please try again.