Commits on Oct 14, 2011
  1. Translating frame body in 3d too flickery. New iOS fix for blank slider.

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

    joseph committed Oct 10, 2011
    Otherwise page dimension calculations get blown out on iOS WebKit.
Commits on Sep 23, 2011
  1. API-CHANGE: controlshow/hide events now prefixed with monocle:

    joseph committed Sep 23, 2011
    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
  2. Wait for a monocle:turn event before dispatching monocle:loaded.

    joseph committed Sep 23, 2011
    I think this fixes #57, but I haven't been able to completely reproduce
    it. See the test/events/index.html test in particular.
Commits on Sep 15, 2011
Commits on Sep 14, 2011
  1. eInk panel now supports keyboard events, and clicking backwards.

    joseph committed Sep 14, 2011
    Clicking on the left half of the page now goes backwards; right half
    goes forwards. PageUp/PageDown are registered to backwards/forwards
  2. Define locus objects with CSS selector strings.

    joseph committed Sep 14, 2011
    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.
Commits on Sep 13, 2011
  1. eInk Panel (supports Kindle3).

    joseph committed Sep 13, 2011
    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.
  2. Refining column width calculations.

    joseph committed Sep 13, 2011
    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.
  3. Apply all CSS modifications to body at once.

    joseph committed Sep 13, 2011
    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).
  4. Detecting body width clipping.

    joseph committed Sep 13, 2011
    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
Commits on Sep 10, 2011
Commits on Sep 9, 2011
Commits on Sep 8, 2011
Commits on Sep 7, 2011
Commits on Sep 6, 2011
Commits on Sep 5, 2011
  1. Caching component width measurements.

    joseph committed Aug 29, 2011
    This is a reasonably significant change -- the Columns dimension will no
    longer automatically detect if a component is longer or shorter due to
    window resize or stylesheet changes or new DOM content or whatever.
    Now you need to call Reader#recalculateDimensions() explicitly whenever
    you do this. This is automatically done when calling resized or changing
    stylesheets using the methods provided in Reader. For other changes that
    may affect component size, call this method after.
  2. README tweaks.

    joseph committed Sep 5, 2011