@lion/ui 0.17.0-menu-system.1 → 0.17.1

package/components/overlays/NEXT.md

@@ -1,49 +0,0 @@
-- Redesign goals OverlayController
-  - Simplicity
-    - One primitive to (controller to) rule them all
-      - Aligned api with all disclosure mechanisms (openables: <https://open-ui.org/components/openable.explainer/>)
-      - Aligned with platform overlay primitives (popover, dialog and tooltip)
-    - Controller will be elegantly aligned with host
-      - Controller props will be mapped to a host via a mixin, w/o requiring lots of boilerplate
-      - No race conditions due to unaligned heart beats: both hook in to the same "tick": the reactive update cycle of lit (which can theoretically be swapped by other cycles, see <https://lit.dev/docs/frameworks/react/#usecontroller>)
-        - In general, all property effects / events / reactivity should be aligned as much as possible with the update cycle (for predictability and perf. We only need
-    - All components will just be configuration (no need to redefine a lot of logic)
-    - OverlayController (or OpenableController, or DisclosureController, or VisitibilityToggleController) will be the biggest common denominator. Having all logic in one place, makes it a lot easier to erase about then having it scattered across many mixin and/or controller levels
-    - Even though the amount of logic is large (and might feel a bit monolithic), this is just needed when we want to have a stable, battle tested abstraction around all edge cases that building accessible disclosures should handle
-      - However, this does not come at an extra performance cost (see performance, you will only load what you need)
-    - The current OverlayController is a long file that can benefit from some modularity and cleanup
-      - Every overlay feature can be provided in a separate file with knowledge about the overlay lifecycle
-      - We can provide/reuse some utils like Resettable from VisibilityToggleCtrl ()
-  - Flexibility
-    - Re-use your markup for different screen sizes and/or devices (that may have different appearances, but the same functionality/semantics)
-      - Think of:
-        - a datepicker that opens as dropdown on desktop and as centered modal dialog on mobile
-        - a menubutton that opens as dropdown on desktop and as bottomsheet
-        - A menu that opens as dropdown on desktop and a collapsible (or even a plain list) on mobile
-    - As explained above, controllers are the most re-usable primitives, as a web component/mixin does not always provide the flexibility we need
-      - Controllers can be easliy mapped to directives (giving the same flexibility as "platform attributes" like popover). Forward compatible with <https://github.com/WICG/webcomponents/issues/1029>
-      - Controllers can be easily mapped to web components or mixins
-      - Contrary to mixins, it’s easy to conditionally load a controller
-      - Contrary to mixins, it’s easy to “undo” a controller (which is helpful in edge cases)
-  - Performance
-    - Will leverage the platform where possible:
-      - Use popover
-  - Forward compatibility
-    - Aligns as much as possible with (future) platform apis
-      - This leverages existing dev knowledge (api familiarity)
-      - This allows to build drop in replacements
-      - This allows to rely on the platform (reducing maintenance costs, increasing performance)
-  - Completeness
-    - Supports all use cases to build every UI thinkable:
-      - Will have optional dependency to menu controllers and interactive list controllers
-      - Supports visually hidden scenarios, hides
-  - Backward compatibility
-    - Since the amount of consumers of our overlay system (directly or indirectly) is large, we should provide a compatibility mechanism where possible. At the same time, we want to create an api as clean/aligned/forward compatible as possible. We could consider an optional compat-layer (a global import at the top of an app extending OverlayController prototype). Think of:
-      - Mapping popper api to popover concepts
-      -
-
-# Why start with OverlayController?
-
-- there is a lot of value in cleaning it up as there are many platform improvements
-- it's used by many
-- It is already a controller (we created it before Lit controllers existed) and therefore impact is minimal

package/dist-types/components/collapsible/src/DisclosureMixin.d.ts

@@ -1,3 +0,0 @@
-export type DisclosureHost = import('../types/DisclosureMixinTypes.js').DisclosureHost;
-export type DisclosureMixin = import('../types/DisclosureMixinTypes.js').DisclosureMixin;
-//# sourceMappingURL=DisclosureMixin.d.ts.map

package/dist-types/components/collapsible/src/DisclosureMixin.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"DisclosureMixin.d.ts","sourceRoot":"","sources":["../../../../components/collapsible/src/DisclosureMixin.js"],"names":[],"mappings":"6BACa,OAAO,kCAAkC,EAAE,cAAc;8BACzD,OAAO,kCAAkC,EAAE,eAAe"}

package/dist-types/components/collapsible/types/DisclosureMixinTypes.d.ts

@@ -1,24 +0,0 @@
-import { Constructor } from '@open-wc/dedupe-mixin';
-import { LitElement } from 'lit';
-export declare class DisclosureHost {
-    opened: Boolean;
-    protected get _invokerNode(): HTMLElement;
-    protected get _contentNode(): HTMLElement;
-    toggle(): void;
-    open(): void;
-    close(): void;
-    protected _onOpenedChanged(): Promise<void>;
-    protected _onDisclosureShow(): void;
-    protected _onDisclosureHide(): void;
-    protected _showAnimation(cfg: object): Promise<void>;
-    protected _hideAnimation(cfg: object): Promise<void>;
-    protected _refreshAnimateCompletePromise(): void;
-    protected _setupOpenCloseListeners(): void;
-    protected _teardownOpenCloseListeners(): void;
-    private __setupAnimation;
-    private __teardownAnimation;
-    private __handleAnimateComplete;
-}
-export declare function DisclosureImplementation<T extends Constructor<LitElement>>(superclass: T): T & Constructor<DisclosureHost> & DisclosureHost & Pick<typeof DisclosureHost, keyof typeof DisclosureHost> & Pick<typeof LitElement, keyof typeof LitElement>;
-export type DisclosureMixin = typeof DisclosureImplementation;
-//# sourceMappingURL=DisclosureMixinTypes.d.ts.map

package/dist-types/components/collapsible/types/DisclosureMixinTypes.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"DisclosureMixinTypes.d.ts","sourceRoot":"","sources":["../../../../components/collapsible/types/DisclosureMixinTypes.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,WAAW,EAAE,MAAM,uBAAuB,CAAC;AACpD,OAAO,EAAE,UAAU,EAAE,MAAM,KAAK,CAAC;AAEjC,MAAM,CAAC,OAAO,OAAO,cAAc;IAC1B,MAAM,EAAE,OAAO,CAAC;IAEvB,SAAS,KAAK,YAAY,IAAI,WAAW,CAAC;IAE1C,SAAS,KAAK,YAAY,IAAI,WAAW,CAAC;IAEnC,MAAM,IAAI,IAAI;IAEd,IAAI,IAAI,IAAI;IAEZ,KAAK,IAAI,IAAI;IAEpB,SAAS,CAAC,gBAAgB,IAAI,OAAO,CAAC,IAAI,CAAC;IAE3C,SAAS,CAAC,iBAAiB,IAAI,IAAI;IAEnC,SAAS,CAAC,iBAAiB,IAAI,IAAI;IAEnC,SAAS,CAAC,cAAc,CAAC,GAAG,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAEpD,SAAS,CAAC,cAAc,CAAC,GAAG,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAEpD,SAAS,CAAC,8BAA8B,IAAI,IAAI;IAEhD,SAAS,CAAC,wBAAwB,IAAI,IAAI;IAE1C,SAAS,CAAC,2BAA2B,IAAI,IAAI;IAE7C,OAAO,CAAC,gBAAgB;IAExB,OAAO,CAAC,mBAAmB;IAE3B,OAAO,CAAC,uBAAuB;CAChC;AAED,MAAM,CAAC,OAAO,UAAU,wBAAwB,CAAC,CAAC,SAAS,WAAW,CAAC,UAAU,CAAC,EAChF,UAAU,EAAE,CAAC,GACZ,CAAC,GACF,WAAW,CAAC,cAAc,CAAC,GAC3B,cAAc,GACd,IAAI,CAAC,OAAO,cAAc,EAAE,MAAM,OAAO,cAAc,CAAC,GACxD,IAAI,CAAC,OAAO,UAAU,EAAE,MAAM,OAAO,UAAU,CAAC,CAAC;AAEnD,MAAM,MAAM,eAAe,GAAG,OAAO,wBAAwB,CAAC"}

package/dist-types/components/menu/index.d.ts

@@ -1,3 +0,0 @@
-export { LionMenu } from "./src/LionMenu.js";
-export { InteractiveListMixin } from "./src/InteractiveListMixin.js";
-//# sourceMappingURL=index.d.ts.map

package/dist-types/components/menu/index.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../components/menu/index.js"],"names":[],"mappings":""}

package/dist-types/components/menu/lion-menu-overlay.d.ts

@@ -1,2 +0,0 @@
-export {};
-//# sourceMappingURL=lion-menu-overlay.d.ts.map

package/dist-types/components/menu/lion-menu-overlay.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"lion-menu-overlay.d.ts","sourceRoot":"","sources":["../../../components/menu/lion-menu-overlay.js"],"names":[],"mappings":""}

package/dist-types/components/menu/lion-menu.d.ts

@@ -1,2 +0,0 @@
-export {};
-//# sourceMappingURL=lion-menu.d.ts.map

package/dist-types/components/menu/lion-menu.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"lion-menu.d.ts","sourceRoot":"","sources":["../../../components/menu/lion-menu.js"],"names":[],"mappings":""}

package/dist-types/components/menu/lion-spinbutton.d.ts

@@ -1,2 +0,0 @@
-export {};
-//# sourceMappingURL=lion-spinbutton.d.ts.map

package/dist-types/components/menu/lion-spinbutton.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"lion-spinbutton.d.ts","sourceRoot":"","sources":["../../../components/menu/lion-spinbutton.js"],"names":[],"mappings":""}

package/dist-types/components/menu/lion-toolbar.d.ts

@@ -1,2 +0,0 @@
-export {};
-//# sourceMappingURL=lion-toolbar.d.ts.map

package/dist-types/components/menu/lion-toolbar.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"lion-toolbar.d.ts","sourceRoot":"","sources":["../../../components/menu/lion-toolbar.js"],"names":[],"mappings":""}

package/dist-types/components/menu/lion-tree.d.ts

@@ -1,2 +0,0 @@
-export {};
-//# sourceMappingURL=lion-tree.d.ts.map

package/dist-types/components/menu/lion-tree.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"lion-tree.d.ts","sourceRoot":"","sources":["../../../components/menu/lion-tree.js"],"names":[],"mappings":""}