ig-nav-drawer optimizations

[IG-Stanimir-Dimitrov]

Description

The ig-nav-drawer requires some optimization since it was developed on an earlier angular version.

[damyanpetev]

There seems to be a gestures issue with Hammer.js and Chrome 55+ (works in FF) due to changes to input events. As far as I cant tell pans (touchmove-like) get stuck past the initial trigger and swipes don't get recognized at all (due to pan stopping). Possibly related to hammerjs/hammer.js#1065 and others. Appears to be related to the target as changing the document handlers to body helped.

I see a similar issue with Carousel that uses renderer.listen(this.elementRef.nativeElement, "swipeleft".. and also fails on Chrome (though somehow a similar declarative handler works for the calendar just fine). I've logged #458 for that.

[damyanpetev]

Since this is a generic task, beyond the fix for gestures I do have some suggestions:

• Rename <ig-nav-drawer> to <igx-nav-drawer> to align with other components
• Expose a NavigationModule[NNF] for the nav service and directives or include them in existing modules
• Use our pre-built animations - that might require our own app container component to work with pinned state, though.
• A mini-template version in the samples

@IG-Stanimir-Dimitrov , @kdinev thoughts/suggestions?

[IG-Stanimir-Dimitrov]

@damyanpetev , I agree on the first three points though some of the animations will be an overkill .
Also update the navDrawer spec in the wiki with the latest changes.

[damyanpetev]

@IG-Stanimir-Dimitrov The drawer can have two templates, the mini is a visible collapsed state (e.g. just icons). Last points in the spec stories. The originals samples for component had one, and the new have the ideal icon setup to show that off as well.

[damyanpetev]

Actually an addition - since pinThreshold is evaluated on init only, it might be a good idea to add a resize handler to make it dynamic?

[IG-Stanimir-Dimitrov]

@damyanpetev , I agree - even a basic scenario like a rotating tablet will be handled much better if the pinThreshold is evaluated reactively on resize.

[IG-Stanimir-Dimitrov]

This issue was closed with PR #465

@damyanpetev , update specification as well as the readme.md with the changed igx name and new pinThreshold break point.