- Introduced the Step5Interaction component for user interaction with report agents and simulation profiles.
- Added chat functionality to communicate with report agents and selected simulation agents.
- Implemented a survey feature to gather responses from multiple agents.
- Enhanced routing by adding a new InteractionView for seamless navigation to the interaction interface.
- Updated the router configuration to include the new interaction route.
- Improved UI elements and styles for better user experience in the interaction process.
- Added a new API for generating reports, including functions to retrieve report status, agent logs, console logs, and report details.
- Enhanced the Step3Simulation component to manage report generation with loading indicators and improved user feedback during the process.
- Introduced a new Step4Report component to display report details and logs, providing a comprehensive view of the report generation workflow.
- Updated routing to include a dedicated report view, improving navigation and user experience in the application.
- Added new API functions for closing the simulation environment and retrieving its status.
- Enhanced the SimulationRunView and SimulationView components to gracefully handle simulation termination when navigating between steps.
- Introduced logging for better user feedback during the simulation closure process, including attempts to force stop if graceful closure fails.
- Updated the simulation API to include a new 'force' parameter, allowing users to restart simulations while cleaning up previous logs.
- Enhanced the simulation status detail retrieval to include all actions and platform-specific actions for better monitoring.
- Introduced a new SimulationRunView component to manage the simulation process, providing a clear interface for users to start and monitor simulations.
- Improved the Step3Simulation component with detailed logging and progress indicators, ensuring users receive real-time updates during the simulation.
- Added new API endpoints for retrieving simulation posts and actions, enhancing the overall functionality and user engagement.
- Introduced a new API endpoint for retrieving real-time simulation configuration, allowing users to view progress and metadata during simulation generation.
- Updated frontend API service to include the new real-time configuration method.
- Enhanced Step2EnvSetup.vue to support real-time polling for configuration updates, improving user experience during simulation setup.
- Revised display logic to show detailed configuration summaries and orchestration content, enriching the simulation setup process.
- Added a new method in simulation.js for retrieving detailed run status.
- Revised descriptions in Step1GraphBuild.vue and Step2EnvSetup.vue for improved clarity on simulation processes.
- Updated titles and labels in Step2EnvSetup.vue to better reflect the initialization and setup stages.
- Enhanced styling and layout in Step2EnvSetup.vue for a more cohesive user experience.
- Adjusted descriptions in Home.vue to accurately represent the simulation workflow.
- Introduced simulation.js API for creating and managing simulations, including methods for creating, preparing, and retrieving simulation statuses.
- Added Step1GraphBuild.vue and Step2EnvSetup.vue components to facilitate the graph building and environment setup processes, enhancing user interaction and workflow.
- Updated MainView.vue to integrate new components and manage the simulation workflow, including step indicators and navigation between steps.
- Created SimulationView.vue for displaying simulation details and managing the simulation environment, improving overall user experience and functionality.
- Introduced `PROJECT_STATUS.md` to provide a comprehensive overview of the MiroFish project, detailing the current status, completed features, and future development plans.
- Added multiple documentation files in the frontend directory, including detailed descriptions of the homepage functionality, startup guide, and project completion summary.
- Implemented a structured approach to document the project's architecture, API integration, and user interaction processes, enhancing clarity for developers and users alike.
- Included a `.gitignore` file to manage ignored files and directories in the frontend project, improving project organization and cleanliness.
liyizhouAI
ghostubborn
666ghj