Create a VMKeyboardService.
Not yet fully enabled, though does listen for 'focus' events and can handle
arbitrary conditions like 'inDialog'.
Right now, handling of these kinds of events is global.
This implementation will also allow each Page to register more than one set
of shortcuts. In theory, shortcuts common to different views could be shared,
though may be difficult depending on how much information they would need to
share between them.
Issue #130.
␄
Add a Logger.clear() method.
I have wanted this so many times!
Issue #130.
␄
Create DebugKeys as an optional set of shortcuts for Global.
No-op as VMKeyboardService does not yet actively enable keys.
Issue #130.
␄
Change the pagination Scroller to use a different element.
Instead of using the button, use the li that surrounds the button. This
allows shining to work, so we can go back to the more traditional "navigate to
an item (page number) then select it (Enter key)."
Issue #143.
␄
Allow pagination Scroller to get focus.
This whole #lastScroller thing is nice. It may be worth converting some
existing Pages that use the hasActiveSubitem() approach.
Issue #143.
␄
Give pagination Scroller a bit of a buffer on the bottom.
Now that we are doing a traditional scrolling, having some room at the bottom
of the screen is a little nicer.
Issue #143.
␄
Missed a place where we need to loop over values in a Map.
Issue #130.
␄
Change hotkey from Enter to c.
In other cases where we can easily detect that focus is on an element inside
the current Scroller element. There we can elect to allow the standard
browser function take over (e.g., TABbing to a link and hitting ENTER).
So here, we will use n and p to select a page, then c to change to it.
Issue #143.
␄
Give the job cards a bottom scroll margin as well.
Just looks nicer.
Issue #143.
␄
Change the job card Scroller to use a different element.
Like the recent change to the pagination one, use the surrounding li. It
allows the highlights to shine through.
However, we are going to keep the auto-click on change feature. Unlike
scrolling through the pages at the bottom, moving to a job card then selecting
it feels clunky. Updating as we navigate feels natural. Maybe it is due to
the dual pane layout.
Issue #143.
␄
Add method to navigate to a specific item.
Technically, this can already be achieved through the item setter, however,
that sometimes looks a little strange:
this._foo.item = this._foo.item
will become
this._foo.goto(this._foo.item)
Issue #143.
␄
Add methods to get uid and then later go to it directly.
This will simplify some unusual page loads. It could also be used to simplify
some refreshes in the short term.
Issues #143, #150.
␄
Migrate JobCollections to the ScrollerService.
Issues #143, #149.
␄
Initial work selecting job card on initial page load.
- Updated
pageReadySelector
- Handle activate message
- Do update the pagination scroller
Issue #143.
␄
Bump version number.
␄
