commit 83906ac9400687db22f305dbc402e6bbe81c69bd Author: talksik Date: Thu Mar 27 12:00:38 2025 -0700 feat: initial commit (migrate from old flowy monorepo) diff --git a/.qmlls.ini b/.qmlls.ini new file mode 100644 index 0000000..c46ca4e --- /dev/null +++ b/.qmlls.ini @@ -0,0 +1,5 @@ +[General] +buildDir="/Users/talksik/Documents/code/flowy/src/qt/computerdaemon/release-x86_64-1.0.1/designsystem" +no-cmake-calls=false +docDir=/Users/talksik/Qt/Docs/Qt-6.8.2 +importPaths="/Users/talksik/Qt/6.8.2/macos/qml" diff --git a/AppIcon.qml b/AppIcon.qml new file mode 100644 index 0000000..3c7a8fd --- /dev/null +++ b/AppIcon.qml @@ -0,0 +1,28 @@ +import QtQuick +import QtQuick.Controls.Basic + +Item { + id: item + required property string source + property color color: "white" + required property int iconHeight + required property int iconWidth + property var onClicked + + height: item.iconHeight + width: item.iconWidth + + Button { + anchors.centerIn: parent + background: Rectangle { + color: "transparent" + } + // FIX: onClicked doesn't work + onClicked: if (item.onClicked) item.onClicked() + icon.source: item.source + icon.width: item.iconWidth + icon.height: item.iconHeight + icon.color: item.color + enabled: item.onClicked ? true : false + } +} diff --git a/AppText.qml b/AppText.qml new file mode 100644 index 0000000..6d2b2a2 --- /dev/null +++ b/AppText.qml @@ -0,0 +1,7 @@ +import QtQuick +import QtQuick.Controls.Basic + +Text { + color: palette.text + font.family: Fonts.plusJakartaSans +} diff --git a/CMakeLists.txt b/CMakeLists.txt new file mode 100644 index 0000000..df0f31e --- /dev/null +++ b/CMakeLists.txt @@ -0,0 +1,108 @@ +cmake_minimum_required(VERSION 3.16) +set(CMAKE_AUTOMOC ON) +set(CMAKE_CXX_STANDARD_REQUIRED ON) +set(QT_QML_OUTPUT_DIRECTORY "${CMAKE_BINARY_DIR}/designsystem") + +project(designsystem VERSION 0.1 LANGUAGES CXX) + +find_package(Qt6 6.2 COMPONENTS Quick REQUIRED) + +qt_add_library(designsystem STATIC) + +set(plain_qml_files + AppText.qml + AppIcon.qml +) +set(qml_singletons + Fonts.qml + Theme.qml +) +set_source_files_properties(${qml_singletons} + PROPERTIES QT_QML_SINGLETON_TYPE TRUE) +set(icons + icons/wifi-medium-duotone.svg + icons/cloud-check-duotone.svg + icons/layout-duotone.svg + icons/person-simple-run-duotone.svg + icons/pen-duotone.svg + icons/binoculars-duotone.svg + icons/magic-wand-duotone.svg + icons/list-duotone.svg + icons/broom-duotone.svg + icons/terminal-duotone.svg + icons/caret-down-duotone.svg + icons/caret-up-duotone.svg + icons/caret-right-duotone.svg + icons/caret-left-duotone.svg + icons/navigation-arrow-duotone.svg + icons/plus-duotone.svg + icons/split-vertical-duotone.svg + icons/split-horizontal-duotone.svg + icons/x-circle-duotone.svg + icons/tag-chevron-duotone.svg + icons/flying-saucer-duotone.svg + icons/arrow-fat-left-duotone.svg + icons/arrow-fat-right-duotone.svg + icons/arrow-fat-up-duotone.svg + icons/arrow-fat-down-duotone.svg + icons/book-open-text-duotone.svg + icons/star-duotone.svg + icons/bookmark-duotone.svg + icons/book-duotone.svg + icons/bookmarks-duotone.svg + icons/file-plus-duotone.svg + icons/magnifying-glass-minus-duotone.svg + icons/magnifying-glass-plus-duotone.svg + icons/stack-duotone.svg + icons/squares-four-duotone.svg + icons/speaker-high-duotone.svg + icons/speaker-low-duotone.svg + icons/speaker-x-duotone.svg + icons/mouse-scroll-duotone.svg + icons/camera-duotone.svg + icons/selection-all-duotone.svg + icons/command-duotone.svg + icons/file-magnifying-glass-duotone.svg + icons/folder-open-duotone.svg + icons/flower-lotus-duotone.svg + icons/git-branch-duotone.svg + icons/trash-duotone.svg + icons/arrows-out-duotone.svg + icons/arrows-out-line-horizontal-duotone.svg + icons/arrows-out-line-vertical-duotone.svg + icons/sidebar-duotone.svg + icons/yin-yang-duotone.svg + + icons/apple-logo-duotone.svg + app-icons/safari.svg + app-icons/vs-code.svg + app-icons/ghostty.png + logos/FLOWY-4.svg + logos/FLOWY-5.svg + logos/FLOWY-6.svg +) +set(fonts + fonts/dotrice/Dotrice-Regular.otf + fonts/dotrice/Dotrice-Bold.otf + fonts/dotrice/Dotrice-Expanded.otf + fonts/dotrice/Dotrice-Condensed.otf + fonts/dotrice/Dotrice-Bold-Condensed.otf + fonts/dotrice/Dotrice-Bold-Expanded.otf + fonts/Plus_Jakarta_Sans/PlusJakartaSans-Italic-VariableFont_wght.ttf + fonts/Plus_Jakarta_Sans/PlusJakartaSans-VariableFont_wght.ttf +) + +qt_add_qml_module(designsystem + URI DesignSystem + RESOURCE_PREFIX /live.flowy/imports + VERSION 1.0 + QML_FILES ${plain_qml_files} ${qml_singletons} + RESOURCES ${icons} ${fonts} +) +target_link_libraries(designsystem + PRIVATE + Qt6::Quick +) + +target_compile_definitions(designsystem + PRIVATE $<$,$>:QT_QML_DEBUG>) diff --git a/CMakeLists.txt.user b/CMakeLists.txt.user new file mode 100644 index 0000000..91b7b51 --- /dev/null +++ b/CMakeLists.txt.user @@ -0,0 +1,460 @@ + + + + + + EnvironmentId + {1354daad-1138-41d2-985c-27357b7ee48a} + + + ProjectExplorer.Project.ActiveTarget + 0 + + + ProjectExplorer.Project.EditorSettings + + true + false + true + + Cpp + + CppGlobal + + + + QmlJS + + QmlJSGlobal + + + 2 + UTF-8 + false + 4 + false + 0 + 80 + true + true + 1 + 0 + false + true + false + 2 + true + true + 0 + 8 + true + false + 1 + true + true + true + *.md, *.MD, Makefile + false + true + true + + + + ProjectExplorer.Project.PluginSettings + + + true + false + true + true + true + true + + false + + + 0 + true + + true + true + Builtin.DefaultTidyAndClazy + 5 + true + + + + true + + + + + ProjectExplorer.Project.Target.0 + + Desktop + Qt 6.8.2 for macOS + Qt 6.8.2 for macOS + qt.qt6.682.clang_64_kit + 0 + 0 + 0 + + Debug + 2 + false + + -DCMAKE_BUILD_TYPE:STRING=Debug +-DCMAKE_PREFIX_PATH:PATH=%{Qt:QT_INSTALL_PREFIX} +-DCMAKE_C_COMPILER:FILEPATH=%{Compiler:Executable:C} +-DCMAKE_CXX_FLAGS_INIT:STRING=%{Qt:QML_DEBUG_FLAG} +-DCMAKE_PROJECT_INCLUDE_BEFORE:FILEPATH=%{BuildConfig:BuildDirectory:NativeFilePath}/.qtc/package-manager/auto-setup.cmake +-DCMAKE_COLOR_DIAGNOSTICS:BOOL=ON +-DCMAKE_CXX_COMPILER:FILEPATH=%{Compiler:Executable:Cxx} +-DCMAKE_GENERATOR:STRING=Ninja +-DQT_QMAKE_EXECUTABLE:FILEPATH=%{Qt:qmakeExecutable} + 0 + /Users/talksik/Documents/code/flowy/src/qt/designsystem/build/Qt_6_8_2_for_macOS-Debug + + + + + all + + false + + true + Build + CMakeProjectManager.MakeStep + + 1 + Build + Build + ProjectExplorer.BuildSteps.Build + + + + + + clean + + false + + true + Build + CMakeProjectManager.MakeStep + + 1 + Clean + Clean + ProjectExplorer.BuildSteps.Clean + + 2 + false + + false + + Debug + CMakeProjectManager.CMakeBuildConfiguration + + + Release + 2 + false + + -DCMAKE_BUILD_TYPE:STRING=Release +-DCMAKE_PREFIX_PATH:PATH=%{Qt:QT_INSTALL_PREFIX} +-DCMAKE_C_COMPILER:FILEPATH=%{Compiler:Executable:C} +-DCMAKE_CXX_FLAGS_INIT:STRING=%{Qt:QML_DEBUG_FLAG} +-DCMAKE_PROJECT_INCLUDE_BEFORE:FILEPATH=%{BuildConfig:BuildDirectory:NativeFilePath}/.qtc/package-manager/auto-setup.cmake +-DCMAKE_COLOR_DIAGNOSTICS:BOOL=ON +-DCMAKE_CXX_COMPILER:FILEPATH=%{Compiler:Executable:Cxx} +-DCMAKE_GENERATOR:STRING=Ninja +-DQT_QMAKE_EXECUTABLE:FILEPATH=%{Qt:qmakeExecutable} + /Users/talksik/Documents/code/flowy/src/qt/designsystem/build/Qt_6_8_2_for_macOS-Release + + + + + all + + false + + true + CMakeProjectManager.MakeStep + + 1 + Build + Build + ProjectExplorer.BuildSteps.Build + + + + + + clean + + false + + true + CMakeProjectManager.MakeStep + + 1 + Clean + Clean + ProjectExplorer.BuildSteps.Clean + + 2 + false + + false + + Release + CMakeProjectManager.CMakeBuildConfiguration + + + RelWithDebInfo + 2 + false + + -DCMAKE_BUILD_TYPE:STRING=RelWithDebInfo +-DCMAKE_PREFIX_PATH:PATH=%{Qt:QT_INSTALL_PREFIX} +-DCMAKE_C_COMPILER:FILEPATH=%{Compiler:Executable:C} +-DCMAKE_CXX_FLAGS_INIT:STRING=%{Qt:QML_DEBUG_FLAG} +-DCMAKE_PROJECT_INCLUDE_BEFORE:FILEPATH=%{BuildConfig:BuildDirectory:NativeFilePath}/.qtc/package-manager/auto-setup.cmake +-DCMAKE_COLOR_DIAGNOSTICS:BOOL=ON +-DCMAKE_CXX_COMPILER:FILEPATH=%{Compiler:Executable:Cxx} +-DCMAKE_GENERATOR:STRING=Ninja +-DQT_QMAKE_EXECUTABLE:FILEPATH=%{Qt:qmakeExecutable} + /Users/talksik/Documents/code/flowy/src/qt/designsystem/build/Qt_6_8_2_for_macOS-RelWithDebInfo + + + + + all + + false + + true + CMakeProjectManager.MakeStep + + 1 + Build + Build + ProjectExplorer.BuildSteps.Build + + + + + + clean + + false + + true + CMakeProjectManager.MakeStep + + 1 + Clean + Clean + ProjectExplorer.BuildSteps.Clean + + 2 + false + + false + + Release with Debug Information + CMakeProjectManager.CMakeBuildConfiguration + + + RelWithDebInfo + 2 + false + + -DCMAKE_BUILD_TYPE:STRING=RelWithDebInfo +-DCMAKE_PREFIX_PATH:PATH=%{Qt:QT_INSTALL_PREFIX} +-DCMAKE_C_COMPILER:FILEPATH=%{Compiler:Executable:C} +-DCMAKE_CXX_FLAGS_INIT:STRING=%{Qt:QML_DEBUG_FLAG} +-DCMAKE_PROJECT_INCLUDE_BEFORE:FILEPATH=%{BuildConfig:BuildDirectory:NativeFilePath}/.qtc/package-manager/auto-setup.cmake +-DCMAKE_COLOR_DIAGNOSTICS:BOOL=ON +-DCMAKE_CXX_COMPILER:FILEPATH=%{Compiler:Executable:Cxx} +-DCMAKE_GENERATOR:STRING=Ninja +-DQT_QMAKE_EXECUTABLE:FILEPATH=%{Qt:qmakeExecutable} + 0 + /Users/talksik/Documents/code/flowy/src/qt/designsystem/build/Qt_6_8_2_for_macOS-Profile + + + + + all + + false + + true + CMakeProjectManager.MakeStep + + 1 + Build + Build + ProjectExplorer.BuildSteps.Build + + + + + + clean + + false + + true + CMakeProjectManager.MakeStep + + 1 + Clean + Clean + ProjectExplorer.BuildSteps.Clean + + 2 + false + + false + + Profile + CMakeProjectManager.CMakeBuildConfiguration + + + MinSizeRel + 2 + false + + -DCMAKE_BUILD_TYPE:STRING=MinSizeRel +-DCMAKE_PREFIX_PATH:PATH=%{Qt:QT_INSTALL_PREFIX} +-DCMAKE_C_COMPILER:FILEPATH=%{Compiler:Executable:C} +-DCMAKE_CXX_FLAGS_INIT:STRING=%{Qt:QML_DEBUG_FLAG} +-DCMAKE_PROJECT_INCLUDE_BEFORE:FILEPATH=%{BuildConfig:BuildDirectory:NativeFilePath}/.qtc/package-manager/auto-setup.cmake +-DCMAKE_COLOR_DIAGNOSTICS:BOOL=ON +-DCMAKE_CXX_COMPILER:FILEPATH=%{Compiler:Executable:Cxx} +-DCMAKE_GENERATOR:STRING=Ninja +-DQT_QMAKE_EXECUTABLE:FILEPATH=%{Qt:qmakeExecutable} + /Users/talksik/Documents/code/flowy/src/qt/designsystem/build/Qt_6_8_2_for_macOS-MinSizeRel + + + + + all + + false + + true + CMakeProjectManager.MakeStep + + 1 + Build + Build + ProjectExplorer.BuildSteps.Build + + + + + + clean + + false + + true + CMakeProjectManager.MakeStep + + 1 + Clean + Clean + ProjectExplorer.BuildSteps.Clean + + 2 + false + + false + + Minimum Size Release + CMakeProjectManager.CMakeBuildConfiguration + + 5 + + + 0 + Deploy + Deploy + ProjectExplorer.BuildSteps.Deploy + + 1 + + false + ProjectExplorer.DefaultDeployConfiguration + + + + + + + + + false + + true + ApplicationManagerPlugin.Deploy.CMakePackageStep + + + install-package --acknowledge + true + Install Application Manager package + ApplicationManagerPlugin.Deploy.InstallPackageStep + + + + + + + + 2 + Deploy + Deploy + ProjectExplorer.BuildSteps.Deploy + + 1 + + false + ApplicationManagerPlugin.Deploy.Configuration + + 2 + + true + true + 0 + true + + 2 + + false + -e cpu-cycles --call-graph dwarf,4096 -F 250 + + ProjectExplorer.CustomExecutableRunConfiguration + + false + true + true + + 1 + + + + ProjectExplorer.Project.TargetCount + 1 + + + ProjectExplorer.Project.Updater.FileVersion + 22 + + + Version + 22 + + diff --git a/Fonts.qml b/Fonts.qml new file mode 100644 index 0000000..4ad6766 --- /dev/null +++ b/Fonts.qml @@ -0,0 +1,27 @@ +pragma Singleton + +import QtQuick + +Item { + property alias dotrice: dotrice.font.family + property alias dotriceBold: dotriceBold.font.family + property alias dotriceCondensed: dotriceCondensed.font.family + property alias plusJakartaSans: plusJakartaSans.font.family + + FontLoader { + id: dotrice + source: "qrc:/live.flowy/imports/DesignSystem/fonts/dotrice/Dotrice-Regular.otf" + } + FontLoader { + id: dotriceBold + source: "qrc:/live.flowy/imports/DesignSystem/fonts/dotrice/Dotrice-Bold.otf" + } + FontLoader { + id: dotriceCondensed + source: "qrc:/live.flowy/imports/DesignSystem/fonts/dotrice/Dotrice-Condensed.otf" + } + FontLoader { + id: plusJakartaSans + source: "qrc:/live.flowy/imports/DesignSystem/fonts/Plus_Jakarta_Sans/PlusJakartaSans-VariableFont_wght.ttf" + } +} diff --git a/Theme.qml b/Theme.qml new file mode 100644 index 0000000..03f5ced --- /dev/null +++ b/Theme.qml @@ -0,0 +1,13 @@ +pragma Singleton + +import QtQuick + +// based on https://colorhunt.co/palette/181c143c3d37697565ecdfcc +Item { + property color background: "#181C14" + property color card: "#232421" + property color accent: "#697565" + property color muted: "#A0A0A0" + property color foreground: "#ECDFCC" + property color softBorder: "#282926" +} diff --git a/app-icons/ghostty.png b/app-icons/ghostty.png new file mode 100644 index 0000000..5258e20 Binary files /dev/null and b/app-icons/ghostty.png differ diff --git a/app-icons/safari.svg b/app-icons/safari.svg new file mode 100644 index 0000000..f5ac6c2 --- /dev/null +++ b/app-icons/safari.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/app-icons/vs-code.svg b/app-icons/vs-code.svg new file mode 100644 index 0000000..ab47f5a --- /dev/null +++ b/app-icons/vs-code.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/fonts/Plus_Jakarta_Sans/OFL.txt b/fonts/Plus_Jakarta_Sans/OFL.txt new file mode 100644 index 0000000..76770dd --- /dev/null +++ b/fonts/Plus_Jakarta_Sans/OFL.txt @@ -0,0 +1,93 @@ +Copyright 2020 The Plus Jakarta Sans Project Authors (https://github.com/tokotype/PlusJakartaSans) + +This Font Software is licensed under the SIL Open Font License, Version 1.1. +This license is copied below, and is also available with a FAQ at: +https://openfontlicense.org + + +----------------------------------------------------------- +SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007 +----------------------------------------------------------- + +PREAMBLE +The goals of the Open Font License (OFL) are to stimulate worldwide +development of collaborative font projects, to support the font creation +efforts of academic and linguistic communities, and to provide a free and +open framework in which fonts may be shared and improved in partnership +with others. + +The OFL allows the licensed fonts to be used, studied, modified and +redistributed freely as long as they are not sold by themselves. The +fonts, including any derivative works, can be bundled, embedded, +redistributed and/or sold with any software provided that any reserved +names are not used by derivative works. The fonts and derivatives, +however, cannot be released under any other type of license. The +requirement for fonts to remain under this license does not apply +to any document created using the fonts or their derivatives. + +DEFINITIONS +"Font Software" refers to the set of files released by the Copyright +Holder(s) under this license and clearly marked as such. This may +include source files, build scripts and documentation. + +"Reserved Font Name" refers to any names specified as such after the +copyright statement(s). + +"Original Version" refers to the collection of Font Software components as +distributed by the Copyright Holder(s). + +"Modified Version" refers to any derivative made by adding to, deleting, +or substituting -- in part or in whole -- any of the components of the +Original Version, by changing formats or by porting the Font Software to a +new environment. + +"Author" refers to any designer, engineer, programmer, technical +writer or other person who contributed to the Font Software. + +PERMISSION & CONDITIONS +Permission is hereby granted, free of charge, to any person obtaining +a copy of the Font Software, to use, study, copy, merge, embed, modify, +redistribute, and sell modified and unmodified copies of the Font +Software, subject to the following conditions: + +1) Neither the Font Software nor any of its individual components, +in Original or Modified Versions, may be sold by itself. + +2) Original or Modified Versions of the Font Software may be bundled, +redistributed and/or sold with any software, provided that each copy +contains the above copyright notice and this license. These can be +included either as stand-alone text files, human-readable headers or +in the appropriate machine-readable metadata fields within text or +binary files as long as those fields can be easily viewed by the user. + +3) No Modified Version of the Font Software may use the Reserved Font +Name(s) unless explicit written permission is granted by the corresponding +Copyright Holder. This restriction only applies to the primary font name as +presented to the users. + +4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font +Software shall not be used to promote, endorse or advertise any +Modified Version, except to acknowledge the contribution(s) of the +Copyright Holder(s) and the Author(s) or with their explicit written +permission. + +5) The Font Software, modified or unmodified, in part or in whole, +must be distributed entirely under this license, and must not be +distributed under any other license. The requirement for fonts to +remain under this license does not apply to any document created +using the Font Software. + +TERMINATION +This license becomes null and void if any of the above conditions are +not met. + +DISCLAIMER +THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, +EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT +OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE +COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, +INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL +DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING +FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM +OTHER DEALINGS IN THE FONT SOFTWARE. diff --git a/fonts/Plus_Jakarta_Sans/PlusJakartaSans-Italic-VariableFont_wght.ttf b/fonts/Plus_Jakarta_Sans/PlusJakartaSans-Italic-VariableFont_wght.ttf new file mode 100644 index 0000000..7de3b5b Binary files /dev/null and b/fonts/Plus_Jakarta_Sans/PlusJakartaSans-Italic-VariableFont_wght.ttf differ diff --git a/fonts/Plus_Jakarta_Sans/PlusJakartaSans-VariableFont_wght.ttf b/fonts/Plus_Jakarta_Sans/PlusJakartaSans-VariableFont_wght.ttf new file mode 100644 index 0000000..bdd4985 Binary files /dev/null and b/fonts/Plus_Jakarta_Sans/PlusJakartaSans-VariableFont_wght.ttf differ diff --git a/fonts/Plus_Jakarta_Sans/README.txt b/fonts/Plus_Jakarta_Sans/README.txt new file mode 100644 index 0000000..6ac7707 --- /dev/null +++ b/fonts/Plus_Jakarta_Sans/README.txt @@ -0,0 +1,77 @@ +Plus Jakarta Sans Variable Font +=============================== + +This download contains Plus Jakarta Sans as both variable fonts and static fonts. + +Plus Jakarta Sans is a variable font with this axis: + wght + +This means all the styles are contained in these files: + PlusJakartaSans-VariableFont_wght.ttf + PlusJakartaSans-Italic-VariableFont_wght.ttf + +If your app fully supports variable fonts, you can now pick intermediate styles +that aren’t available as static fonts. Not all apps support variable fonts, and +in those cases you can use the static font files for Plus Jakarta Sans: + static/PlusJakartaSans-ExtraLight.ttf + static/PlusJakartaSans-Light.ttf + static/PlusJakartaSans-Regular.ttf + static/PlusJakartaSans-Medium.ttf + static/PlusJakartaSans-SemiBold.ttf + static/PlusJakartaSans-Bold.ttf + static/PlusJakartaSans-ExtraBold.ttf + static/PlusJakartaSans-ExtraLightItalic.ttf + static/PlusJakartaSans-LightItalic.ttf + static/PlusJakartaSans-Italic.ttf + static/PlusJakartaSans-MediumItalic.ttf + static/PlusJakartaSans-SemiBoldItalic.ttf + static/PlusJakartaSans-BoldItalic.ttf + static/PlusJakartaSans-ExtraBoldItalic.ttf + +Get started +----------- + +1. Install the font files you want to use + +2. Use your app's font picker to view the font family and all the +available styles + +Learn more about variable fonts +------------------------------- + + https://developers.google.com/web/fundamentals/design-and-ux/typography/variable-fonts + https://variablefonts.typenetwork.com + https://medium.com/variable-fonts + +In desktop apps + + https://theblog.adobe.com/can-variable-fonts-illustrator-cc + https://helpx.adobe.com/nz/photoshop/using/fonts.html#variable_fonts + +Online + + https://developers.google.com/fonts/docs/getting_started + https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Fonts/Variable_Fonts_Guide + https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/variable-fonts + +Installing fonts + + MacOS: https://support.apple.com/en-us/HT201749 + Linux: https://www.google.com/search?q=how+to+install+a+font+on+gnu%2Blinux + Windows: https://support.microsoft.com/en-us/help/314960/how-to-install-or-remove-a-font-in-windows + +Android Apps + + https://developers.google.com/fonts/docs/android + https://developer.android.com/guide/topics/ui/look-and-feel/downloadable-fonts + +License +------- +Please read the full license text (OFL.txt) to understand the permissions, +restrictions and requirements for usage, redistribution, and modification. + +You can use them in your products & projects – print or digital, +commercial or otherwise. + +This isn't legal advice, please consider consulting a lawyer and see the full +license for all details. diff --git a/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-Bold.ttf b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-Bold.ttf new file mode 100644 index 0000000..386d3a6 Binary files /dev/null and b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-Bold.ttf differ diff --git a/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-BoldItalic.ttf b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-BoldItalic.ttf new file mode 100644 index 0000000..20540d3 Binary files /dev/null and b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-BoldItalic.ttf differ diff --git a/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-ExtraBold.ttf b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-ExtraBold.ttf new file mode 100644 index 0000000..a67cafd Binary files /dev/null and b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-ExtraBold.ttf differ diff --git a/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-ExtraBoldItalic.ttf b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-ExtraBoldItalic.ttf new file mode 100644 index 0000000..c38f755 Binary files /dev/null and b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-ExtraBoldItalic.ttf differ diff --git a/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-ExtraLight.ttf b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-ExtraLight.ttf new file mode 100644 index 0000000..bb43929 Binary files /dev/null and b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-ExtraLight.ttf differ diff --git a/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-ExtraLightItalic.ttf b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-ExtraLightItalic.ttf new file mode 100644 index 0000000..15abe5d Binary files /dev/null and b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-ExtraLightItalic.ttf differ diff --git a/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-Italic.ttf b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-Italic.ttf new file mode 100644 index 0000000..dc955cf Binary files /dev/null and b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-Italic.ttf differ diff --git a/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-Light.ttf b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-Light.ttf new file mode 100644 index 0000000..215db16 Binary files /dev/null and b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-Light.ttf differ diff --git a/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-LightItalic.ttf b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-LightItalic.ttf new file mode 100644 index 0000000..ee12a1d Binary files /dev/null and b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-LightItalic.ttf differ diff --git a/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-Medium.ttf b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-Medium.ttf new file mode 100644 index 0000000..1e58066 Binary files /dev/null and b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-Medium.ttf differ diff --git a/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-MediumItalic.ttf b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-MediumItalic.ttf new file mode 100644 index 0000000..d6d28b3 Binary files /dev/null and b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-MediumItalic.ttf differ diff --git a/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-Regular.ttf b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-Regular.ttf new file mode 100644 index 0000000..1e77059 Binary files /dev/null and b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-Regular.ttf differ diff --git a/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-SemiBold.ttf b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-SemiBold.ttf new file mode 100644 index 0000000..49817ef Binary files /dev/null and b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-SemiBold.ttf differ diff --git a/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-SemiBoldItalic.ttf b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-SemiBoldItalic.ttf new file mode 100644 index 0000000..8399e98 Binary files /dev/null and b/fonts/Plus_Jakarta_Sans/static/PlusJakartaSans-SemiBoldItalic.ttf differ diff --git a/fonts/dotrice/Dotrice-Bold-Condensed.otf b/fonts/dotrice/Dotrice-Bold-Condensed.otf new file mode 100644 index 0000000..07c4b8d Binary files /dev/null and b/fonts/dotrice/Dotrice-Bold-Condensed.otf differ diff --git a/fonts/dotrice/Dotrice-Bold-Expanded.otf b/fonts/dotrice/Dotrice-Bold-Expanded.otf new file mode 100644 index 0000000..8ba1d39 Binary files /dev/null and b/fonts/dotrice/Dotrice-Bold-Expanded.otf differ diff --git a/fonts/dotrice/Dotrice-Bold.otf b/fonts/dotrice/Dotrice-Bold.otf new file mode 100644 index 0000000..ea22c6f Binary files /dev/null and b/fonts/dotrice/Dotrice-Bold.otf differ diff --git a/fonts/dotrice/Dotrice-Condensed.otf b/fonts/dotrice/Dotrice-Condensed.otf new file mode 100644 index 0000000..b423e14 Binary files /dev/null and b/fonts/dotrice/Dotrice-Condensed.otf differ diff --git a/fonts/dotrice/Dotrice-Expanded.otf b/fonts/dotrice/Dotrice-Expanded.otf new file mode 100644 index 0000000..1f075d7 Binary files /dev/null and b/fonts/dotrice/Dotrice-Expanded.otf differ diff --git a/fonts/dotrice/Dotrice-Regular.otf b/fonts/dotrice/Dotrice-Regular.otf new file mode 100644 index 0000000..ffaa462 Binary files /dev/null and b/fonts/dotrice/Dotrice-Regular.otf differ diff --git a/fonts/dotrice/FONTLOG.txt b/fonts/dotrice/FONTLOG.txt new file mode 100644 index 0000000..2037bf2 --- /dev/null +++ b/fonts/dotrice/FONTLOG.txt @@ -0,0 +1,24 @@ +FONTLOG for Dotrice + +This file provides detailed information on the Dotrice Font Software. +This information should be distributed along with the Dotrice fonts +and any derivative works. + +Basic Font Information + +Designed to look like an old EPSON FX-80 printer. + +ChangeLog + +2011-06-01 (Paul Flo Williams) Dotrice Version 1.001 +- Initial release for Open Font Library. This release doesn't include + the oblique style (because I haven't finished it), Dotrice Worn or + Dotrice Touch, or the build scripts, because they are currently too + messy. + +Acknowledgements + +N: Paul Flo Williams +E: paul@frixxon.co.uk +W: http://hisdeedsaredust.com/ +D: Designer - original glyphs diff --git a/fonts/dotrice/OFL-FAQ.txt b/fonts/dotrice/OFL-FAQ.txt new file mode 100644 index 0000000..b966864 --- /dev/null +++ b/fonts/dotrice/OFL-FAQ.txt @@ -0,0 +1,536 @@ +OFL FAQ - Frequently Asked Questions about the SIL Open Font License (OFL) +Version 1.1-update1 - 31 March 2009 +(See http://scripts.sil.org/OFL for updates) + + +1 ABOUT USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL + +1.1 Can I use the fonts in any publication, even embedded in the file? +Yes. You may use them like most other fonts, but unlike some fonts you may +include an embedded subset of the fonts in your document. Such use does not +require you to include this license or other files (listed in OFL condition 2), +nor does it require any type of acknowledgement within the publication. Some +mention of the font name within the publication information (such as in a +colophon) is usually appreciated. If you wish to include the complete font as a +separate file, you should distribute the full font package, including all +existing acknowledgements, and comply with the OFL conditions. Of course, +referencing or embedding an OFL font in any document does not change the +license of the document itself. The requirement for fonts to remain under the +OFL does not apply to any document created using the fonts and their +derivatives. Similarly, creating any kind of graphic using a font under OFL +does not make the resulting artwork subject to the OFL. + +1.2 Can I make web pages using these fonts? +Yes! Go ahead! Using CSS (Cascading Style Sheets) is recommended. Direct usage +of fonts retrieved from a remote server - also referred to as font linking - +using cross-platform open standards like @font-face is encouraged. This is +considered to be use and distribution for which the OFL explicitly grants +permission. The font file itself is not embedded in the webpage but referenced +through a web address (i.e. a URI regardless of file format or access protocol) +which will cause the browser to retrieve and use the corresponding font to +render the webpage. This usage scenario is different from font embedding within +a document (i.e. a PDF) where the font or some of its elements become part of +the document. Note that embedding in a document is also permitted by the +license as indicated in 1.1. (See 1.10 for details related to URL-based access +restrictions methods or DRM mechanisms). + +1.3 Can I make the fonts available to others from my web site? +Yes, as long as you meet the conditions of the license (do not sell by itself, +include the necessary files, include the necessary copyright and license +information, rename Modified Versions, do not abuse the Author(s)' name(s) and +do not sublicense). In the case where you are hosting fonts to be served on the +web, make sure the file contains the needed copyright notice(s) and licensing +information in its metadata. Please double-check the accuracy of every field to +prevent contradictory information. If you are making the font available for use +via the @font-face open standard, putting this information in the standard font +metadata fields is sufficient. Other font formats, including EOT and proposed +superior alternatives, already provide fields for this information. + +1.4 Can the fonts be included with Free/Libre and Open Source Software +collections such as GNU/Linux and BSD distributions? +Yes! Fonts licensed under the OFL can be freely aggregated with software under +FLOSS (Free/Libre and Open Source Software) licenses. Since fonts are much more +useful aggregated to than merged with existing software, possible +incompatibility with existing software licenses is not a problem. You can also +repackage the fonts and the accompanying components in a .rpm or .deb package +and include them in distro CD/DVDs and online repositories. + +1.5 I want to distribute the fonts with my program. Does this mean my program +also has to be free/libre and open source software? +No. Only the portions based on the Font Software are required to be released +under the OFL. The intent of the license is to allow aggregation or bundling +with software under restricted licensing as well. + +1.6 Can I include the fonts on a CD of freeware or commercial fonts? +Yes, as long some other font or software is also on the disk, so the OFL font +is not sold by itself. + +1.7 Can I sell a software package that includes these fonts? +Yes, you can do this with both the Original Version and a Modified Version. +Examples of bundling made possible by the OFL would include: word processors, +design and publishing applications, training and educational software, +edutainment software, etc. + +1.8 Why won't the OFL let me sell the fonts alone? +The intent is to keep people from making money by simply redistributing the +fonts. The only people who ought to profit directly from the fonts should be +the original authors, and those authors have kindly given up potential direct +income to distribute their fonts under the OFL. Please honor and respect their +contribution! + +1.9 I've come across a font released under the OFL. How can I easily get more +information about the Original Version? How can I know where it stands compared +to the Original Version or other Modified Versions? +Consult the copyright statement(s) in the license for ways to contact the +original authors. Consult the FONTLOG for information on how the font differs +from the Original Version, and get in touch with the various contributors via +the information in the acknowledgment section. Please consider using the +Original Versions of the fonts whenever possible. + +1.10 What do you mean in condition 4? Can you provide examples of abusive +promotion / endorsement / advertisement vs. normal acknowledgement? +The intent is that the goodwill and reputation of the author(s) should not be +used in a way that makes it sound like the original author(s) endorse or +approve of a specific Modified Version or software bundle. For example, it +would not be right to advertise a word processor by naming the author(s) in a +listing of software features, or to promote a Modified Version on a web site by +saying "designed by ...". However, it would be appropriate to acknowledge the +author(s) if your software package has a list of people who deserve thanks. We +realize that this can seem to be a gray area, but the standard used to judge an +acknowledgement is that if the acknowledgement benefits the author(s) it is +allowed, but if it primarily benefits other parties, or could reflect poorly on +the author(s), then it is not. + +1.11 Can Font Software released under the OFL be subject to URL-based access +restrictions methods or DRM mechanisms? +Yes, but these issues are out-of-scope for the OFL. The license itself neither +encourages their use nor prohibits them since such mechanisms are not +implemented in the components of the Font Software but through external +software. Such restrictions are put in place for many different purposes +corresponding to various usage scenarios. One common example is to limit +potentially dangerous cross-site scripting attacks. However, in the spirit of +libre/open fonts and unrestricted writing systems, we strongly encourage open +sharing and reuse of OFL fonts, and the establishment of an environment where +such restrictions are unnecessary. Note that whether you wish to use such +mechanisms or you prefer not to, you must still abide by the rules set forth by +the OFL when using fonts released by their authors under this license. +Derivative fonts must be licensed under the OFL, even if they are part of a +service for which you charge fees and/or for which access to source code is +restricted. You may not sell the fonts on their own - they must be part of a +larger software package or bundle. For example, even if the OFL font is +distributed in a software package or via an online service using a DRM +mechanism, the user would still have the right to extract that font, use, +study, modify and redistribute it under the OFL. + +1.12 What about distributing fonts with a document? Within a compressed folder +structure like an OpenDocument file (.odt) for example? Is it redistribution, +bundling or embedding? +The vast majority of the time, documents circulated in electronic form +reference a font name which will match the corresponding font on the target +system but do not carry the font within themselves. There may, however, be some +cases where you need to bundle a font with the document. Certain document +formats may allow the inclusion of an unmodified font within their file +structure which consists of a compressed folder containing the various +resources forming the document (such as pictures and thumbnails). Including +fonts within such a structure is understood as being different from embedding +but rather similar to bundling (or mere aggregation) for which the licensing +makes explicit provision. In this case the font is conveyed unchanged whereas +embedding a font transforms it from the original format. The OFL does not allow +anyone to extract the font from such a structure to then redistribute it under +another license. The explicit permission to redistribute and embed does not +cancel the requirement for the Font Software to remain under the license chosen +by its Author(s). + +1.13 If OFL fonts are extracted from a document in which they are embedded +(such as a PDF file), what can be done with them? Is this a risk to Author(s)? +The few utilities that can extract fonts embedded in a PDF will only output +limited amounts of outlines - not a complete font. To create a working font +from this method is much more difficult than finding the source of the original +OFL font. So there is little chance that an OFL font would be extracted and +redistributed inappropriately through this method. Even so, copyright laws +address any misrepresentation of authorship. All Font Software released under +the OFL and marked as such by the Author(s) is intended to remain under this +license regardless of the distribution method, and cannot be redistributed +under any other license. We strongly discourage any font extraction - we +recommend directly using the font sources instead - but if you extract font +outlines from a document please be considerate, use your common sense and +respect the work of the Author(s) and the licensing model. + +1.14 What about sharing OFL fonts with friends on a CD, DVD or USB stick? +You are very welcome to share open fonts with friends, family and colleagues on +such removable media. Please make sure that you share and share-alike as much +as possible from what the Author(s) released and that you don't strip away +useful information which may not be present in the binary font files +themselves. Just remember that in the case where you sell the font, it has to +come bundled with software. + + +2 ABOUT MODIFYING OFL LICENSED FONTS + +2.1 Can I change the fonts? Are there any limitations to what things I can and +cannot change? +You are allowed to change anything, as long as such changes do not violate the +terms of the license. In other words, you are not allowed to remove the +copyright statement(s) from the font, but you could add additional information +into it that covers your contribution. + +2.2 I have a font that needs a few extra glyphs - can I take them from an OFL +licensed font and copy them into mine? +Yes, but if you distribute that font to others it must be under the OFL, and +include the information mentioned in condition 2 of the license. + +2.3 Can I charge people for my additional work? In other words, if I add a +bunch of special glyphs and/or OpenType/Graphite code, can I sell the enhanced +font? +Not by itself. Derivative fonts must be released under the OFL and cannot be +sold by themselves. It is permitted, however, to include them in a larger +software package (such as text editors, office suites or operating systems), +even if the larger package is sold. In that case, you are strongly encouraged, +but not required, to also make that derived font easily and freely available +outside of the larger package. + +2.4 Can I pay someone to enhance the fonts for my use and distribution? +Yes. This is a good way to fund the further development of the fonts. Keep in +mind, however, that if the font is distributed to others it must be under the +OFL. You won't be able to recover your investment by exclusively selling the +font, but you will be making a valuable contribution to the community. Please +remember how you have benefitted from the contributions of others. + +2.5 I need to make substantial revisions to the font to make it work with my +program. It will be a lot of work, and a big investment, and I want to be sure +that it can only be distributed with my program. Can I restrict its use? +No. If you redistribute a Modified Version of the font it must be under the +OFL. You may not restrict it in any way. This is intended to ensure that all +released improvements to the fonts become available to everyone. But you will +likely get an edge over competitors by being the first to distribute a bundle +with the enhancements. Again, please remember how you have benefitted from the +contributions of others. + +2.6 Do I have to make any derivative fonts (including extended source files, +build scripts, documentation, etc.) publicly available? +No, but please do share your improvements with others. You may find that you +receive more than what you gave in return. + +2.7 Why can't I use the Reserved Font Name(s) in my derivative font names? I'd +like people to know where the design came from. +The best way to acknowledge the source of the design is to thank the original +authors and any other contributors in the files that are distributed with your +revised font (although no acknowledgement is required). The FONTLOG is a +natural place to do this. Reserved Font Name(s) ensure that the only fonts that +have the original names are the unmodified Original Versions. This allows +designers to maintain artistic integrity while allowing collaboration to +happen. It eliminates potential confusion and name conflicts. When choosing a +name be creative and avoid names that reuse almost all the same letters in the +same order or sound like the original. Keep in mind that the Copyright +Holder(s) can allow a specific trusted partner to use Reserved Font Name(s) +through a separate written agreement. + +2.8 What do you mean by "primary name as presented to the user"? Are you +referring to the font menu name? +Yes, the requirement to change the visible name used to differentiate the font +from others applies to the font menu name and other mechanisms to specify a +font in a document. It would be fine, for example, to keep a text reference to +the original fonts in the description field, in your modified source file or in +documentation provided alongside your derivative as long as no one could be +confused that your modified source is the original. But you cannot use the +Reserved Font Names in any way to identify the font to the user (unless the +Copyright Holder(s) allow(s) it through a separate agreement; see section 2.7). +Users who install derivatives ("Modified Versions") on their systems should not +see any of the original names ("Reserved Font Names") in their font menus, for +example. Again, this is to ensure that users are not confused and do not +mistake a font for another and so expect features only another derivative or +the Original Version can actually offer. Ultimately, creating name conflicts +will cause many problems for the users as well as for the designer of both the +Original and Modified versions, so please think ahead and find a good name for +your own derivative. Font substitution systems like fontconfig, or +application-level font fallback configuration within OpenOffice.org or Scribus, +will also get very confused if the name of the font they are configured to +substitute to actually refers to another physical font on the user's hard +drive. It will help everyone if Original Versions and Modified Versions can +easily be distinguished from one another and from other derivatives. The +substitution mechanism itself is outside the scope of the license. Users can +always manually change a font reference in a document or set up some kind of +substitution at a higher level but at the lower level the fonts themselves have +to respect the Reserved Font Name(s) requirement to prevent ambiguity. If a +substitution is currently active the user should be aware of it. + +2.9 Am I not allowed to use any part of the Reserved Font Names? +You may not use the words of the font names, but you would be allowed to use +parts of words, as long as you do not use any word from the Reserved Font Names +entirely. We do not recommend using parts of words because of potential +confusion, but it is allowed. For example, if "Foobar" was a Reserved Font +Name, you would be allowed to use "Foo" or "bar", although we would not +recommend it. Such an unfortunate choice would confuse the users of your fonts +as well as make it harder for other designers to contribute. + +2.10 So what should I, as an author, identify as Reserved Font Names? +Original authors are encouraged to name their fonts using clear, distinct +names, and only declare the unique parts of the name as Reserved Font Names. +For example, the author of a font called "Foobar Sans" would declare "Foobar" +as a Reserved Font Name, but not "Sans", as that is a common typographical +term, and may be a useful word to use in a derivative font name. Reserved Font +Names should also be single words. A font called "Flowing River" should have +Reserved Font Names "Flowing" and "River", not "Flowing River". + +2.11 Do I, as an author, have to identify any Reserved Font Names? +No, but we strongly encourage you to do so. This is to avoid confusion between +your work and Modified versions. You may, however, give certain trusted parties +the right to use any of your Reserved Font Names through separate written +agreements. For example, even if "Foobar" is a RFN, you could write up an +agreement to give company "XYZ" the right to distribute a modified version with +a name that includes "Foobar". This allows for freedom without confusion. + +2.12 Are any names (such as the main font name) reserved by default? +No. That is a change to the license as of version 1.1. If you want any names to +be Reserved Font Names, they must be specified after the copyright statement(s). + +2.13 What is this FONTLOG thing exactly? +It has three purposes: 1) to provide basic information on the font to users and +other developers, 2) to document changes that have been made to the font or +accompanying files, either by the original authors or others, and 3) to provide +a place to acknowledge the authors and other contributors. Please use it! See +below for details on how changes should be noted. + +2.14 Am I required to update the FONTLOG? +No, but users, designers and other developers might get very frustrated at you +if you don't! People need to know how derivative fonts differ from the +original, and how to take advantage of the changes, or build on them. + + +3 ABOUT THE FONTLOG + +The FONTLOG can take a variety of formats, but should include these four +sections: + +3.1 FONTLOG for +This file provides detailed information on the Font Software. +This information should be distributed along with the fonts +and any derivative works. + +3.2 Basic Font Information +(Here is where you would describe the purpose and brief specifications for the +font project, and where users can find more detailed documentation. It can also +include references to how changes can be contributed back to the Original +Version. You may also wish to include a short guide to the design, or a +reference to such a document.) + +3.3 ChangeLog +(This should list both major and minor changes, most recent first. Here are +some examples:) + +7 February 2007 (Pat Johnson) Version 1.3 +- Added Greek and Cyrillic glyphs +- Released as "" + +7 March 2006 (Fred Foobar) Version 1.2 +- Tweaked contextual behaviours +- Released as "" + +1 Feb 2005 (Jane Doe) Version 1.1 +- Improved build script performance and verbosity +- Extended the smart code documentation +- Corrected minor typos in the documentation +- Fixed position of combining inverted breve below (U+032F) +- Added OpenType/Graphite smart code for Armenian +- Added Armenian glyphs (U+0531 -> U+0587) +- Released as "" + +1 Jan 2005 (Joe Smith) Version 1.0 +- Initial release of font "" + +3.4 Acknowledgements +(Here is where contributors can be acknowledged. + +If you make modifications be sure to add your name (N), email (E), web-address +(W) and description (D). This list is sorted by last name in alphabetical +order.) + +N: Jane Doe +E: jane@university.edu +W: http://art.university.edu/projects/fonts +D: Contributor - Armenian glyphs and code + +N: Fred Foobar +E: fred@foobar.org +W: http://foobar.org +D: Contributor - misc Graphite fixes + +N: Pat Johnson +E: pat@fontstudio.org +W: http://pat.fontstudio.org +D: Designer - Greek & Cyrillic glyphs based on Roman design + +N: Tom Parker +E: tom@company.com +W: http://www.company.com/tom/projects/fonts +D: Engineer - original smart font code + +N: Joe Smith +E: joe@fontstudio.org +W: http://joe.fontstudio.org +D: Designer - original Roman glyphs + +(Original authors can also include information here about their organization.) + + +4 ABOUT MAKING CONTRIBUTIONS + +4.1 Why should I contribute my changes back to the original authors? +It would benefit many people if you contributed back to what you've received. +Providing your contributions and improvements to the fonts and other components +(data files, source code, build scripts, documentation, etc.) could be a +tremendous help and would encourage others to contribute as well and 'give +back', which means you will have an opportunity to benefit from other people's +contributions as well. Sometimes maintaining your own separate version takes +more effort than merging back with the original. Be aware that any +contributions, however, must be either your own original creation or work that +you own, and you may be asked to affirm that clearly when you contribute. + +4.2 I've made some very nice improvements to the font, will you consider +adopting them and putting them into future Original Versions? +Most authors would be very happy to receive such contributions. Keep in mind +that it is unlikely that they would want to incorporate major changes that +would require additional work on their end. Any contributions would likely need +to be made for all the fonts in a family and match the overall design and +style. Authors are encouraged to include a guide to the design with the fonts. +It would also help to have contributions submitted as patches or clearly marked +changes (the use of smart source revision control systems like subversion, svk, +mercurial, git or bzr is a good idea). Examples of useful contributions are bug +fixes, additional glyphs, stylistic alternates (and the smart font code to +access them) or improved hinting. + +4.3 How can I financially support the development of OFL fonts? +It is likely that most authors of OFL fonts would accept financial +contributions - contact them for instructions on how to do this. Such +contributions would support future development. You can also pay for others to +enhance the fonts and contribute the results back to the original authors for +inclusion in the Original Version. + + +5 ABOUT THE LICENSE + +5.1 I see that this is version 1.1 of the license. Will there be later changes? +Version 1.1 is the first minor revision of the OFL. We are confident that +version 1.1 will meet most needs, but are open to future improvements. Any +revisions would be for future font releases, and previously existing licenses +would remain in effect. No retroactive changes are possible, although the +Copyright Holder(s) can re-release the font under a revised OFL. All versions +will be available on our web site: http://scripts.sil.org/OFL. + +5.2 Can I use the SIL Open Font License for my own fonts? +Yes! We heartily encourage anyone to use the OFL to distribute their own +original fonts. It is a carefully constructed license that allows great freedom +along with enough artistic integrity protection for the work of the authors as +well as clear rules for other contributors and those who redistribute the +fonts. Some additional information about using the OFL is included at the end +of this FAQ. + +5.3 Does this license restrict the rights of the Copyright Holder(s)? +No. The Copyright Holder(s) still retain(s) all the rights to their creation; +they are only releasing a portion of it for use in a specific way. For example, +the Copyright Holder(s) may choose to release a 'basic' version of their font +under the OFL, but sell a restricted 'enhanced' version. Only the Copyright +Holder(s) can do this. + +5.4 Is the OFL a contract or a license? +The OFL is a license and not a contract and so does not require you to sign it +to have legal validity. By using, modifying and redistributing components under +the OFL you indicate that you accept the license. + +5.5 How about translating the license and the FAQ into other languages? +SIL certainly recognises the need for people who are not familiar with English +to be able to understand the OFL and this FAQ better in their own language. +Making the license very clear and readable is a key goal of the OFL. + +If you are an experienced translator, you are very welcome to help by +translating the OFL and its FAQ so that designers and users in your language +community can understand the license better. But only the original English +version of the license has legal value and has been approved by the community. +Translations do not count as legal substitutes and should only serve as a way +to explain the original license. SIL - as the author and steward of the license +for the community at large - does not approve any translation of the OFL as +legally valid because even small translation ambiguities could be abused and +create problems. + +We give permission to publish unofficial translations into other languages +provided that they comply with the following guidelines: + +- put the following disclaimer in both English and the target language stating +clearly that the translation is unofficial: + +"This is an unofficial translation of the SIL Open Font License into $language. +It was not published by SIL International, and does not legally state the +distribution terms for fonts that use the OFL. A release under the OFL is only +valid when using the original English text. + +However, we recognize that this unofficial translation will help users and +designers not familiar with English to understand the SIL OFL better and make +it easier to use and release font families under this collaborative font design +model. We encourage designers who consider releasing their creation under the +OFL to read the FAQ in their own language if it is available. + +Please go to http://scripts.sil.org/OFL for the official version of the license +and the accompanying FAQ." + +- keep your unofficial translation current and update it at our request if +needed, for example if there is any ambiguity which could lead to confusion. + +If you start such a unofficial translation effort of the OFL and its +accompanying FAQ please let us know, thank you. + + +6 ABOUT SIL INTERNATIONAL + +6.1 Who is SIL International and what does it do? +SIL International is a worldwide faith-based education and development +organization (NGO) that studies, documents, and assists in developing the +world's lesser-known languages through literacy, linguistics, translation, and +other academic disciplines. SIL makes its services available to all without +regard to religious belief, political ideology, gender, race, or ethnic +background. SIL's members and volunteers share a Christian commitment. + +6.2 What does this have to do with font licensing? +The ability to read, write, type and publish in one's own language is one of +the most critical needs for millions of people around the world. This requires +fonts that are widely available and support lesser-known languages. SIL +develops - and encourages others to develop - a complete stack of writing +systems implementation components available under open licenses. This open +stack includes input methods, smart fonts, smart rendering libraries and smart +applications. There has been a need for a common open license that is +specifically applicable to fonts and related software (a crucial component of +this stack) so SIL developed the SIL Open Font License with the help of the +FLOSS community. + +6.3 How can I contact SIL? +Our main web site is: http://www.sil.org/ +Our site about complex scripts is: http://scripts.sil.org/ +Information about this license (including contact email information) is at: +http://scripts.sil.org/OFL + + +7 ABOUT USING THE OFL FOR YOUR ORIGINAL FONTS + +If you want to release your fonts under the OFL, you only need to do the +following: + +7.1 Put your copyright and reserved font names information in the beginning of +the main OFL file (simply use the dedicated placeholders). +7.2 Put your copyright and the OFL references in your various font files (such +as in the copyright, license and description fields) and in your other +components (build scripts, glyph databases, documentation, rendering samples, +etc). Accurate metadata in your font files is beneficial to you as an +increasing number of applications are exposing this information to the user. +For example, clickable links can bring users back to your website and let them +know about other work you have done or services you provide. Depending on the +format of your fonts and sources, you can use template human-readable headers +or machine-readable metadata. +7.3 Write an initial FONTLOG for your font and include it in the release +package. +7.4 Include the OFL license file in your release package. +7.5 We also highly recommend you include the relevant practical documentation +on the license by putting the OFL-FAQ in your package. +7.6 If you wish, you can use the OFL Graphics on your web page. + +That's all. If you have any more questions please get in touch with us. + + diff --git a/fonts/dotrice/OFL.txt b/fonts/dotrice/OFL.txt new file mode 100644 index 0000000..c1f8592 --- /dev/null +++ b/fonts/dotrice/OFL.txt @@ -0,0 +1,94 @@ +Copyright (c) 2010, Paul Flo Williams (paul@frixxon.co.uk), +with Reserved Font Name Dotrice. + +This Font Software is licensed under the SIL Open Font License, Version 1.1. +This license is copied below, and is also available with a FAQ at: +http://scripts.sil.org/OFL + + +----------------------------------------------------------- +SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007 +----------------------------------------------------------- + +PREAMBLE +The goals of the Open Font License (OFL) are to stimulate worldwide +development of collaborative font projects, to support the font creation +efforts of academic and linguistic communities, and to provide a free and +open framework in which fonts may be shared and improved in partnership +with others. + +The OFL allows the licensed fonts to be used, studied, modified and +redistributed freely as long as they are not sold by themselves. The +fonts, including any derivative works, can be bundled, embedded, +redistributed and/or sold with any software provided that any reserved +names are not used by derivative works. The fonts and derivatives, +however, cannot be released under any other type of license. The +requirement for fonts to remain under this license does not apply +to any document created using the fonts or their derivatives. + +DEFINITIONS +"Font Software" refers to the set of files released by the Copyright +Holder(s) under this license and clearly marked as such. This may +include source files, build scripts and documentation. + +"Reserved Font Name" refers to any names specified as such after the +copyright statement(s). + +"Original Version" refers to the collection of Font Software components as +distributed by the Copyright Holder(s). + +"Modified Version" refers to any derivative made by adding to, deleting, +or substituting -- in part or in whole -- any of the components of the +Original Version, by changing formats or by porting the Font Software to a +new environment. + +"Author" refers to any designer, engineer, programmer, technical +writer or other person who contributed to the Font Software. + +PERMISSION & CONDITIONS +Permission is hereby granted, free of charge, to any person obtaining +a copy of the Font Software, to use, study, copy, merge, embed, modify, +redistribute, and sell modified and unmodified copies of the Font +Software, subject to the following conditions: + +1) Neither the Font Software nor any of its individual components, +in Original or Modified Versions, may be sold by itself. + +2) Original or Modified Versions of the Font Software may be bundled, +redistributed and/or sold with any software, provided that each copy +contains the above copyright notice and this license. These can be +included either as stand-alone text files, human-readable headers or +in the appropriate machine-readable metadata fields within text or +binary files as long as those fields can be easily viewed by the user. + +3) No Modified Version of the Font Software may use the Reserved Font +Name(s) unless explicit written permission is granted by the corresponding +Copyright Holder. This restriction only applies to the primary font name as +presented to the users. + +4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font +Software shall not be used to promote, endorse or advertise any +Modified Version, except to acknowledge the contribution(s) of the +Copyright Holder(s) and the Author(s) or with their explicit written +permission. + +5) The Font Software, modified or unmodified, in part or in whole, +must be distributed entirely under this license, and must not be +distributed under any other license. The requirement for fonts to +remain under this license does not apply to any document created +using the Font Software. + +TERMINATION +This license becomes null and void if any of the above conditions are +not met. + +DISCLAIMER +THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, +EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT +OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE +COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, +INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL +DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING +FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM +OTHER DEALINGS IN THE FONT SOFTWARE. diff --git a/icons/apple-logo-duotone.svg b/icons/apple-logo-duotone.svg new file mode 100644 index 0000000..3129c40 --- /dev/null +++ b/icons/apple-logo-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/arrow-circle-down-duotone.svg b/icons/arrow-circle-down-duotone.svg new file mode 100644 index 0000000..b57bcb2 --- /dev/null +++ b/icons/arrow-circle-down-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/arrow-circle-left-duotone.svg b/icons/arrow-circle-left-duotone.svg new file mode 100644 index 0000000..90fb07f --- /dev/null +++ b/icons/arrow-circle-left-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/arrow-circle-right-duotone.svg b/icons/arrow-circle-right-duotone.svg new file mode 100644 index 0000000..1773146 --- /dev/null +++ b/icons/arrow-circle-right-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/arrow-circle-up-duotone.svg b/icons/arrow-circle-up-duotone.svg new file mode 100644 index 0000000..92197c4 --- /dev/null +++ b/icons/arrow-circle-up-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/arrow-fat-down-duotone.svg b/icons/arrow-fat-down-duotone.svg new file mode 100644 index 0000000..5bd9167 --- /dev/null +++ b/icons/arrow-fat-down-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/arrow-fat-left-duotone.svg b/icons/arrow-fat-left-duotone.svg new file mode 100644 index 0000000..17476f3 --- /dev/null +++ b/icons/arrow-fat-left-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/arrow-fat-right-duotone.svg b/icons/arrow-fat-right-duotone.svg new file mode 100644 index 0000000..f787dad --- /dev/null +++ b/icons/arrow-fat-right-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/arrow-fat-up-duotone.svg b/icons/arrow-fat-up-duotone.svg new file mode 100644 index 0000000..766ac89 --- /dev/null +++ b/icons/arrow-fat-up-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/arrows-out-duotone.svg b/icons/arrows-out-duotone.svg new file mode 100644 index 0000000..79436f2 --- /dev/null +++ b/icons/arrows-out-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/arrows-out-line-horizontal-duotone.svg b/icons/arrows-out-line-horizontal-duotone.svg new file mode 100644 index 0000000..3862867 --- /dev/null +++ b/icons/arrows-out-line-horizontal-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/arrows-out-line-vertical-duotone.svg b/icons/arrows-out-line-vertical-duotone.svg new file mode 100644 index 0000000..17b67d0 --- /dev/null +++ b/icons/arrows-out-line-vertical-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/binoculars-duotone.svg b/icons/binoculars-duotone.svg new file mode 100644 index 0000000..6785bbb --- /dev/null +++ b/icons/binoculars-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/book-duotone.svg b/icons/book-duotone.svg new file mode 100644 index 0000000..11646af --- /dev/null +++ b/icons/book-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/book-open-text-duotone.svg b/icons/book-open-text-duotone.svg new file mode 100644 index 0000000..3611fda --- /dev/null +++ b/icons/book-open-text-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/bookmark-duotone.svg b/icons/bookmark-duotone.svg new file mode 100644 index 0000000..842e252 --- /dev/null +++ b/icons/bookmark-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/bookmarks-duotone.svg b/icons/bookmarks-duotone.svg new file mode 100644 index 0000000..8672a35 --- /dev/null +++ b/icons/bookmarks-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/broom-duotone.svg b/icons/broom-duotone.svg new file mode 100644 index 0000000..04212be --- /dev/null +++ b/icons/broom-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/camera-duotone.svg b/icons/camera-duotone.svg new file mode 100644 index 0000000..a827029 --- /dev/null +++ b/icons/camera-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/caret-down-duotone.svg b/icons/caret-down-duotone.svg new file mode 100644 index 0000000..33b444b --- /dev/null +++ b/icons/caret-down-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/caret-left-duotone.svg b/icons/caret-left-duotone.svg new file mode 100644 index 0000000..6f3bc57 --- /dev/null +++ b/icons/caret-left-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/caret-right-duotone.svg b/icons/caret-right-duotone.svg new file mode 100644 index 0000000..899a15b --- /dev/null +++ b/icons/caret-right-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/caret-up-duotone.svg b/icons/caret-up-duotone.svg new file mode 100644 index 0000000..313eb12 --- /dev/null +++ b/icons/caret-up-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/cloud-check-duotone.svg b/icons/cloud-check-duotone.svg new file mode 100644 index 0000000..3cbbbf4 --- /dev/null +++ b/icons/cloud-check-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/command-duotone.svg b/icons/command-duotone.svg new file mode 100644 index 0000000..1e51c0d --- /dev/null +++ b/icons/command-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/file-magnifying-glass-duotone.svg b/icons/file-magnifying-glass-duotone.svg new file mode 100644 index 0000000..71b99de --- /dev/null +++ b/icons/file-magnifying-glass-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/file-plus-duotone.svg b/icons/file-plus-duotone.svg new file mode 100644 index 0000000..c183fc9 --- /dev/null +++ b/icons/file-plus-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/flower-lotus-duotone.svg b/icons/flower-lotus-duotone.svg new file mode 100644 index 0000000..3452172 --- /dev/null +++ b/icons/flower-lotus-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/flying-saucer-duotone.svg b/icons/flying-saucer-duotone.svg new file mode 100644 index 0000000..1a3336b --- /dev/null +++ b/icons/flying-saucer-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/folder-open-duotone.svg b/icons/folder-open-duotone.svg new file mode 100644 index 0000000..266b396 --- /dev/null +++ b/icons/folder-open-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/git-branch-duotone.svg b/icons/git-branch-duotone.svg new file mode 100644 index 0000000..eb12218 --- /dev/null +++ b/icons/git-branch-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/layout-duotone.svg b/icons/layout-duotone.svg new file mode 100644 index 0000000..f1d6821 --- /dev/null +++ b/icons/layout-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/list-duotone.svg b/icons/list-duotone.svg new file mode 100644 index 0000000..5322efa --- /dev/null +++ b/icons/list-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/magic-wand-duotone.svg b/icons/magic-wand-duotone.svg new file mode 100644 index 0000000..ab41879 --- /dev/null +++ b/icons/magic-wand-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/magnifying-glass-minus-duotone.svg b/icons/magnifying-glass-minus-duotone.svg new file mode 100644 index 0000000..c8b218e --- /dev/null +++ b/icons/magnifying-glass-minus-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/magnifying-glass-plus-duotone.svg b/icons/magnifying-glass-plus-duotone.svg new file mode 100644 index 0000000..0bd6b4e --- /dev/null +++ b/icons/magnifying-glass-plus-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/mouse-scroll-duotone.svg b/icons/mouse-scroll-duotone.svg new file mode 100644 index 0000000..a25f3b9 --- /dev/null +++ b/icons/mouse-scroll-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/navigation-arrow-duotone.svg b/icons/navigation-arrow-duotone.svg new file mode 100644 index 0000000..3d623be --- /dev/null +++ b/icons/navigation-arrow-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/pen-duotone.svg b/icons/pen-duotone.svg new file mode 100644 index 0000000..6a0bbae --- /dev/null +++ b/icons/pen-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/person-simple-run-duotone.svg b/icons/person-simple-run-duotone.svg new file mode 100644 index 0000000..409ea37 --- /dev/null +++ b/icons/person-simple-run-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/plus-duotone.svg b/icons/plus-duotone.svg new file mode 100644 index 0000000..fa5d860 --- /dev/null +++ b/icons/plus-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/selection-all-duotone.svg b/icons/selection-all-duotone.svg new file mode 100644 index 0000000..e43d506 --- /dev/null +++ b/icons/selection-all-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/sidebar-duotone.svg b/icons/sidebar-duotone.svg new file mode 100644 index 0000000..6cdf8c3 --- /dev/null +++ b/icons/sidebar-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/speaker-high-duotone.svg b/icons/speaker-high-duotone.svg new file mode 100644 index 0000000..81cc298 --- /dev/null +++ b/icons/speaker-high-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/speaker-low-duotone.svg b/icons/speaker-low-duotone.svg new file mode 100644 index 0000000..aa13c67 --- /dev/null +++ b/icons/speaker-low-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/speaker-x-duotone.svg b/icons/speaker-x-duotone.svg new file mode 100644 index 0000000..2b82198 --- /dev/null +++ b/icons/speaker-x-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/split-horizontal-duotone.svg b/icons/split-horizontal-duotone.svg new file mode 100644 index 0000000..4526d36 --- /dev/null +++ b/icons/split-horizontal-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/split-vertical-duotone.svg b/icons/split-vertical-duotone.svg new file mode 100644 index 0000000..eeb5238 --- /dev/null +++ b/icons/split-vertical-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/squares-four-duotone.svg b/icons/squares-four-duotone.svg new file mode 100644 index 0000000..5ed88d0 --- /dev/null +++ b/icons/squares-four-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/stack-duotone.svg b/icons/stack-duotone.svg new file mode 100644 index 0000000..af1eff2 --- /dev/null +++ b/icons/stack-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/star-duotone.svg b/icons/star-duotone.svg new file mode 100644 index 0000000..058d758 --- /dev/null +++ b/icons/star-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/tag-chevron-duotone.svg b/icons/tag-chevron-duotone.svg new file mode 100644 index 0000000..418e664 --- /dev/null +++ b/icons/tag-chevron-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/terminal-duotone.svg b/icons/terminal-duotone.svg new file mode 100644 index 0000000..a97ce48 --- /dev/null +++ b/icons/terminal-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/trash-duotone.svg b/icons/trash-duotone.svg new file mode 100644 index 0000000..c7fb6aa --- /dev/null +++ b/icons/trash-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/wifi-medium-duotone.svg b/icons/wifi-medium-duotone.svg new file mode 100644 index 0000000..5435b92 --- /dev/null +++ b/icons/wifi-medium-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/x-circle-duotone.svg b/icons/x-circle-duotone.svg new file mode 100644 index 0000000..6aa88cd --- /dev/null +++ b/icons/x-circle-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/icons/yin-yang-duotone.svg b/icons/yin-yang-duotone.svg new file mode 100644 index 0000000..cac9b01 --- /dev/null +++ b/icons/yin-yang-duotone.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/logos/1024x.png b/logos/1024x.png new file mode 100644 index 0000000..b51e41c Binary files /dev/null and b/logos/1024x.png differ diff --git a/logos/1024x_macos.png b/logos/1024x_macos.png new file mode 100644 index 0000000..a4e96a5 Binary files /dev/null and b/logos/1024x_macos.png differ diff --git a/logos/FLOWY-1.svg b/logos/FLOWY-1.svg new file mode 100644 index 0000000..ea7a221 --- /dev/null +++ b/logos/FLOWY-1.svg @@ -0,0 +1,3 @@ + + + diff --git a/logos/FLOWY-2.svg b/logos/FLOWY-2.svg new file mode 100644 index 0000000..353e511 --- /dev/null +++ b/logos/FLOWY-2.svg @@ -0,0 +1,3 @@ + + + diff --git a/logos/FLOWY-3.svg b/logos/FLOWY-3.svg new file mode 100644 index 0000000..c68f618 --- /dev/null +++ b/logos/FLOWY-3.svg @@ -0,0 +1,3 @@ + + + diff --git a/logos/FLOWY-4.svg b/logos/FLOWY-4.svg new file mode 100644 index 0000000..044b26e --- /dev/null +++ b/logos/FLOWY-4.svg @@ -0,0 +1,3 @@ + + + diff --git a/logos/FLOWY-5.svg b/logos/FLOWY-5.svg new file mode 100644 index 0000000..3f5de43 --- /dev/null +++ b/logos/FLOWY-5.svg @@ -0,0 +1,3 @@ + + + diff --git a/logos/FLOWY-6.svg b/logos/FLOWY-6.svg new file mode 100644 index 0000000..fb57dde --- /dev/null +++ b/logos/FLOWY-6.svg @@ -0,0 +1,3 @@ + + + diff --git a/logos/FLOWY-7.svg b/logos/FLOWY-7.svg new file mode 100644 index 0000000..d586f12 --- /dev/null +++ b/logos/FLOWY-7.svg @@ -0,0 +1,3 @@ + + + diff --git a/logos/FLOWY.svg b/logos/FLOWY.svg new file mode 100644 index 0000000..7fbdc07 --- /dev/null +++ b/logos/FLOWY.svg @@ -0,0 +1,3 @@ + + + diff --git a/qmldir b/qmldir new file mode 100644 index 0000000..310c678 --- /dev/null +++ b/qmldir @@ -0,0 +1,3 @@ +module designsystem + +AppText 1.0 AppText.qml