Migrated the SCSS import for the frontend directly into editor.js and
userarea.js from frontend.js, removing redundancy by consolidating style
imports. This adjustment enables more coherent management of SCSS files
and removes the need for a separate frontend bundle. Consequently,
frontend.js and its references in HTML templates were removed to clean
up the codebase and simplify the asset pipeline. These changes should
make future maintenance of CSS easier and improve load times by reducing
unnecessary scripting and network requests.
guidelines
Introduced a Security Policy in the newly added SECURITY.md file,
outlining the project's current security status, cautioning users about
its early-stage development, and providing guidance on reporting
vulnerabilities. This establishes a clear protocol for communicating and
handling security concerns, ensuring contributors and users have a
direct channel for raising security issues with the Private.coffee
security team. This move reflects a proactive approach to security and
transparency as the project evolves.
- Added FontAwesome for enriched UI iconography.
- Implemented permission checks in scene edit view to prevent
unauthorized edits.
- Adjusted scene links in the category template for direct edit access,
streamlining the user workflow.
These changes aim at both enhancing the visual elements of the interface
and strengthening the security model by ensuring that only authorized
users can edit scenes. The direct edit links in the category view
further simplify navigation, making the system more intuitive for users.
This commit represents a significant overhaul of the development and
setup processes for the Quackscape project. Key changes include the
transition from a requirements.txt-based dependency management system to
Poetry.
These updates aim to streamline the setup process
- Transitioned to Poetry for improved dependency resolution and package
management.
- Consolidated Django management commands under the quackscape-manage
script to simplify command execution and project management.
- Updated README.md to reflect the new setup procedures, emphasizing
ease of setup and the flexibility to support multiple database backends.
The shift to Poetry and the introduction of a custom management command
tool reflects an effort to modernize the project's infrastructure,
making it more accessible to contributors and easier to maintain.
Added a comprehensive Code of Conduct and Contributing Guidelines for
the Quackscape project to foster a positive community environment and
streamline the contribution process. The Code of Conduct pledges an
inclusive, harassment-free experience for all contributors, while the
Contributing Guidelines outline steps for asking questions, reporting
bugs, suggesting enhancements, and making first code contributions.
These additions aim to enhance participation clarity, ensure respectful
interactions, and encourage contributions by outlining expectations and
procedures, thus promoting a healthier, more collaborative development
atmosphere.
Introduced an MIT LICENSE file for open sourcing the project, ensuring
that users are aware of their rights to use, modify, and distribute the
software. This change underlines our commitment to the open source
community and clarifies usage terms.
Updated the README.md with detailed development setup instructions,
making it easier for new contributors to get started with the project.
The amendments include steps from cloning the repository to starting the
development server, highlighting mandatory installations and
configurations for a smooth setup.
Adjusted settings.py and settings.dist.ini for better clarity and
customization. Simplifications in settings.py improve code readability
and maintainability. The addition of settings.dist.ini allows users to
easily configure their development and production environments per their
needs without altering core configuration files.
These enhancements aim to simplify the contribution process, foster
community involvement, and ensure a transparent and flexible setup for
developers engaging with the project.
Introduced significant updates to the user interface for editing VR
scenes, adding new CSS styles for a coherent and modern look.
Implemented data tables for robust content management in the user area,
now users can easily navigate through scenes and media with DataTables
integration. Expanded the API with category retrieval capabilities,
enabling dynamic content categorization.
The editor now seamlessly integrates into the UI with a sidebar for
properties editing, improving usability. The teleportation element
creation and modification logic has been significantly refined,
including a search-enabled dropdown for destination selection, making it
more user-friendly. Added thumbnail display for scenes and media in the
user area, enhancing content overview.
This update also introduced user area templates and routes, providing a
foundational structure for user content management functionality,
including categories and individual category views.
Refactored JavaScript imports to align with the new editor CSS and
adjusted scene loading to support embedded scenes, improving the
flexibility and usability of scene components.
Removed console.log statements for x, y, and z coordinates in the
QuackscapeScene class. This cleanup reduces clutter in the console
during scene initialization, leading to a cleaner and more professional
debug output. No functional impact on scene loading.
Added a workaround to limit texture size on iOS devices to prevent
issues with rendering performance. This change introduces a detection
mechanism for iOS and caps the maximum texture size to 8192 when an iOS
device is identified.
This update introduces support for a third dimension (Z-axis) in scene
positioning and orientation, enhancing 3D scene rendering capabilities.
Changes include parsing the Z-coordinate attribute in scene elements,
updating the `loadScene` function to accommodate the new axis, and
extending the models to store this additional data. This pivotal
enhancement allows a more refined and immersive user experience by
enabling depth control in scene navigation and interactivity. The
modification paves the way for future developments in 3D scene
manipulation and interaction within the application.
Kumi