Skip to content

Forge-changes#60

Open
th3w1zard1 wants to merge 44 commits intoKobaltBlu:masterfrom
th3w1zard1:forge-changes
Open

Forge-changes#60
th3w1zard1 wants to merge 44 commits intoKobaltBlu:masterfrom
th3w1zard1:forge-changes

Conversation

@th3w1zard1
Copy link
Copy Markdown
Contributor

add ARE, IFO, DLG, and a few other editors and features

Nonfunctional (TODO):

  • Load from Module

Untested:

  • Save to RIM/ERF

th3w1zard1 and others added 30 commits January 4, 2026 23:02
- Add .editorconfig for consistent code formatting across editors
- Add .prettierrc with project code style rules
- Add .prettierignore to exclude generated files
- Add .markdownlint.json to configure markdown linting rules

These configuration files establish consistent formatting standards
for the project and improve code quality tooling.
- Update .eslintrc.yml with TypeScript support and improved rules
- Add .eslintignore to exclude generated files
- Configure TypeScript ESLint parser and plugin
- Add import ordering and code quality rules
- Improve TypeScript-specific linting rules
…ter project management

- Added entries for build outputs, logs, runtime data, coverage, documentation, IDE configurations, OS-specific files, environment variables, and temporary files.
- Removed obsolete entries to streamline the ignore list.
- Expanded .gitignore to include additional files and directories for better exclusion of build outputs, logs, and temporary files.
- Added .nvmrc file to specify Node.js version 18 for consistent development environment.
- Update .eslintrc.yml with TypeScript support and improved rules
- Configure TypeScript ESLint parser and plugin
- Add import ordering and code quality rules
- Improve TypeScript-specific linting rules
- Update documentation index and quick reference
- Add bug report template with structured fields
- Add feature request template for new features
- Add pull request template to standardize submissions
- Improve issue tracking and PR quality
- Add extensions.json with recommended VS Code extensions
- Improve developer experience with consistent tooling
- Include ESLint, Prettier, TypeScript, Jest, and Tailwind CSS extensions
- Establish community standards and guidelines
- Define expected behavior for contributors
- Provide enforcement guidelines
- Create welcoming and inclusive environment
- Add detailed contribution guide for new contributors
- Document development setup and workflow
- Define coding standards and best practices
- Include testing requirements and PR process
- Provide issue reporting guidelines
- Add detailed setup guide for all platforms
- Document system requirements and prerequisites
- Include step-by-step installation instructions
- Provide troubleshooting section
- Cover Windows, macOS, and Linux setup
- Document directory organization and structure
- Describe key components and modules
- Explain build configuration files
- Include file naming conventions
- Provide overview of core systems
- Expand getting started section with prerequisites and quick start
- Add detailed available scripts documentation
- Include development workflow guide
- Add project structure overview
- Add contributing and getting help sections
- Add documentation links section
- Improve markdown formatting and spacing
- Fix trailing whitespace and line breaks
- Improve section organization and readability
The Tailwind CSS extension recommendation should be removed as it would not provide any value to contributors and could create confusion about which CSS framework is actually being used.

Co-authored-by: Copilot <[email protected]>
The rmdir /s command requires the /q flag to suppress confirmation prompts in automated scripts.

Co-authored-by: Copilot <[email protected]>
- Consolidated and renamed various build and start scripts for better clarity and organization.
- Introduced new scripts for debugging and serving both Electron and web applications.
- Enhanced the clean and rebuild processes to streamline development workflow.
- Introduced a comprehensive plan for the Holocron Toolset's full implementation in KotOR.js Forge, detailing an extensive file tree and approximately 80 todos.
- Each todo item outlines specific tasks related to various editors and functionalities, ensuring thorough documentation and tracking of progress.
…lity and functionality

- Simplified the extraction of file extensions in GameInitializer by introducing a variable for clarity.
- Enhanced MenuItem component to ensure safe access to properties and improved event handling.
- Updated event listeners in ApplicationWindow and LauncherWindow to remove unnecessary event parameters.
- Refined promise handling in GameFileSystem to improve error management and streamline directory checks.
Format TXI object values before rendering. Font textures use properties
like upperleftcoords and lowerrightcoords that are arrays of {x,y,z}
objects. React cannot render plain objects as children, which caused
"Objects are not valid as a React child" when opening fnt_credits.tpc.

Add formatTxiValue() to convert objects/arrays to displayable strings
instead of rendering them directly.
export * from "./resource/DLGObject";
export * from "./resource/DLGNode";
(with DLGObject before DLGNode since DLGNode depends on DLGObject).
After this, opening a .dlg in the DLG editor should work without the "Cannot read properties of undefined (reading 'FromGFFObject')" error.
@th3w1zard1
Copy link
Copy Markdown
Contributor Author

Please let me know if you'd like this broken down into smaller prs :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant