├── Github-header.png ├── .github └── ISSUE_TEMPLATE │ ├── feature_request.md │ └── bug_report.md └── README.md /Github-header.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bryntum/support/HEAD/Github-header.png -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest an idea or enhancement for the project 4 | title: "[FEATURE] " 5 | labels: feature request 6 | assignees: '' 7 | --- 8 | 9 | ### Summary 10 | A clear and concise description of the feature you’d like to see. 11 | 12 | ### Problem Statement 13 | What problem does this feature solve? Why is it important? 14 | 15 | ### Proposed Solution 16 | Describe the solution you’d like, including any details on how it should work. 17 | 18 | ### Alternatives Considered 19 | List any alternative solutions or workarounds you’ve tried or considered. 20 | 21 | ### Additional Context 22 | Add any other context, mockups, or references that might help us understand the request. -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Report a problem to help us improve 4 | title: "[BUG] " 5 | labels: bug 6 | assignees: '' 7 | --- 8 | 9 | ### Description 10 | A clear and concise description of the issue. 11 | 12 | ### Steps to Reproduce 13 | Reproduce the issue in one of our [official demos](https://bryntum.com/examples) and describe the exact steps: 14 | 15 | 1. Go to '...' 16 | 2. Click on '...' 17 | 3. Scroll down to '...' 18 | 4. See the error 19 | 20 | If the issue cannot be reproduced in our demos, please provide a **minimal reproducible test case** (e.g. CodeSandbox, GitHub repo, or zipped project). Bug reports with clear reproduction steps or a test case are more likely to be fixed earlier than those without. 21 | 22 | ### Expected Behavior 23 | What you expected to happen. 24 | 25 | ### Actual Behavior 26 | What actually happened. 27 | 28 | ### Screenshots / Logs 29 | If applicable, add screenshots or log output to help explain your problem. 30 | 31 | ### Environment 32 | - OS: [e.g. Windows 10, macOS 13] 33 | - Browser: [e.g. Chrome 118, Firefox 120] 34 | - Bryntum Version: [e.g. v6.3.2] 35 | - Other relevant details 36 | 37 | ### Additional Context 38 | Add any other context about the problem here. -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ![Bryntum](./Github-header.png) 2 | 3 | # What's Bryntum? 4 | 5 | Bryntum is a Swedish software company creating advanced JavaScript UI components for enterprise-grade web applications. Founded by a team of passionate web developers, Bryntum specializes in providing cutting-edge scheduling, resource management, and data visualization solutions for modern front-end frameworks. Learn more about our products below: 6 | 7 | * Grid 8 | * Scheduler 9 | * Scheduler Pro 10 | * Gantt 11 | * Calendar 12 | * Kanban Task Board 13 | 14 | ## Bryntum support repo 15 | This repo is an issues-only repository for the Bryntum JS library. If you find a bug, have suggestions for improvements, or want to request a new feature, please visit our official **[Bryntum Forum](https://forum.bryntum.com/)**. Here’s what to do: 16 | 17 | 1. **Search the Forum** 18 | - Before posting, see if your issue or suggestion has already been discussed. 19 | 20 | 2. **Create a New Topic** 21 | - If you can’t find an existing thread, create a new one. 22 | - Provide a clear and concise title that summarizes your bug or feature request. 23 | 24 | 3. **Provide Details** 25 | - **For Bug Reports**: 26 | - Steps to reproduce the issue 27 | - The version of Bryntum library and browser/environment 28 | - Code snippets or test cases (if possible) 29 | - **For Feature Requests**: 30 | - A brief description of the feature 31 | - A use case or example showing its benefits 32 | 33 | 4. **Engage with the Community** 34 | - Check back often to respond to any follow-up questions from Bryntum’s team or other community members. 35 | 36 | ## License 37 | The Bryntum JS library is distributed under a commercial license. See Bryntum’s [license terms](//bryntum.com/licensing/) for additional information. 38 | 39 | ## Contact 40 | If you have any questions, feel free to reach out to us through our [Contact form](//bryntum.com/contact). 41 | 42 | ## Build Statuses 43 | 44 | For build statuses for our nightly builds, see our [Build status](//dev.bryntum.com/teamcity) page. 45 | 46 | 47 | _Thank you for using Bryntum! We’re excited to see what you’ll build with our tools._ 48 | --------------------------------------------------------------------------------