mirror of
https://github.com/GraphiteEditor/Graphite.git
synced 2026-10-04 00:38:12 +08:00
* Make `tauri build` just work * Move folder: frontend/wasm -> wasm * Create SvelteKit project with 'npx create-svelte' * Move wasm-communication into seperate npm package * Use wasm-pack directly and pack package.json * Got it to work * Add primitive build script for wasm npm module * Fix wasm build script (python) * Clean up glue code * Rewrite wasm build script in node.js * Add serde-reflection to trace types * Add traced types * Generate typescript (.d.ts) from Rust types * Update .d.ts * Finalize TS types * Add script to update .d.ts * Add watch command to build wasm-bindgen * Make wasm work again * Add sass; fix build script for windows * Describe requirement for wasm-pack * Add license * Copy and reorganize vue components * translate LayoutCol.vue * Split app.scss into pieces * Translate LayoutRow.svelte * Rename scss files * Fix compile issues on Windows * WIP port TitleBar * Support classes for LayoutCol/Row * Restructure based on Vue codebase * Port all components in window folder * Port FloatingMenu * Port Document panel component * Update readme after folder move * Update typegen: print discriminant by default * Update typegen: Merge from branch 'tailwind' 4f14fedb Fixes bigint & bytes * Made Vue/webpack/eslint to accept wasm package at new location This is quite a hack. Those two packages are both named the same. Yes, it's an npm package inside another npm package. - frontend/src/wasm-communication/ - frontend-svelte/glue/ 'wasm/pkg/index.js' imports the correct one registered when linking. * Port LayerTree * Port NodeGraph * Port Properties * Port components in /floating-menus * Finish porting all Vue -> Svelte components * Change import prefix * Revert type generation * Revert moved wasm folder * Revert all of @locriacyber's work on this branch - Remove Vite and restore Webpack - Remove SvelteKit - Remove everything except the components I ported to Svelte - Restore all frontend files from Vue code, now altered for Svelte * Convert Vue's 'reactive' and 'provide' to Svelte's stores and contexts * Fix event emitting and bi-di data flow * Undo removal of 'update:' events * Fix 'update:' event dispatching * Fix usage in parent of bi-di component props * Fix component typing, more progress towards no errors * The page builds and opens! * Add loading spinner and remove postcss dependency * Make the basics of document editing work * Fix rebase history Co-authored-by: Locria Cyber <74560659+locriacyber@users.noreply.github.com>
72 lines
1.7 KiB
Svelte
72 lines
1.7 KiB
Svelte
<script lang="ts">
|
|
import { type IconName } from "@/utility-functions/icons";
|
|
|
|
import FloatingMenu from "@/components/layout/FloatingMenu.svelte";
|
|
import LayoutRow from "@/components/layout/LayoutRow.svelte";
|
|
import IconButton from "@/components/widgets/buttons/IconButton.svelte";
|
|
|
|
export let icon: IconName = "DropdownArrow";
|
|
export let tooltip: string | undefined = undefined;
|
|
export let disabled = false;
|
|
// Callbacks
|
|
export let action: (() => void) | undefined = undefined;
|
|
|
|
let open = false;
|
|
|
|
function onClick() {
|
|
open = true;
|
|
action?.();
|
|
}
|
|
</script>
|
|
|
|
<LayoutRow class="popover-button">
|
|
<IconButton classes={{ open }} {disabled} action={() => onClick()} icon={icon || "DropdownArrow"} size={16} {tooltip} data-floating-menu-spawner />
|
|
<FloatingMenu {open} on:open={({ detail }) => (open = detail)} type="Popover" direction="Bottom">
|
|
<slot />
|
|
</FloatingMenu>
|
|
</LayoutRow>
|
|
|
|
<style lang="scss" global>
|
|
.popover-button {
|
|
position: relative;
|
|
width: 16px;
|
|
height: 24px;
|
|
flex: 0 0 auto;
|
|
|
|
.floating-menu {
|
|
left: 50%;
|
|
bottom: 0;
|
|
}
|
|
|
|
.icon-button.icon-button {
|
|
width: 100%;
|
|
height: 100%;
|
|
padding: 0;
|
|
border: none;
|
|
border-radius: 2px;
|
|
background: var(--color-1-nearblack);
|
|
fill: var(--color-e-nearwhite);
|
|
|
|
&:hover,
|
|
&.open {
|
|
background: var(--color-6-lowergray);
|
|
fill: var(--color-f-white);
|
|
}
|
|
|
|
&.disabled {
|
|
background: var(--color-2-mildblack);
|
|
fill: var(--color-8-uppergray);
|
|
}
|
|
}
|
|
|
|
// TODO: Refactor this and other complicated cases dealing with joined widget margins and border-radius by adding a single standard set of classes: joined-first, joined-inner, and joined-last
|
|
div[class*="-input"] + & {
|
|
margin-left: 1px;
|
|
|
|
.icon-button {
|
|
border-radius: 0 2px 2px 0;
|
|
}
|
|
}
|
|
}
|
|
</style>
|