G_Week7,2025‐04‐16 - 24-S2-2-C-EduKATE/EduKATE_flutter GitHub Wiki

Time

16/04/2025

Attendees

Yi Wang
Siyi Liu
Dong-Jhang Wu
Rifang Zhou
Wenhui Shi
Wenjing Qi

add more if needed

Agenda

Team Stand-ups
Attend another group's Agile development sharing session and learn about their workflow
Participate in scheduled tutor and client meetings to confirm Sprint 2 goals and expectations
Conduct internal group meeting to walk through the current codebase structure.
Distribute Sprint 2 development tasks among team members.
Begin individual assigned tasks

Minutes

Team Stand-ups

Yi Wang What I did previously: Attended the Agile development sharing session held by another group to learn from their workflow and documentation structure. Participated in both the tutor and client meetings for Sprint 2 planning, helping clarify expectations and confirm deliverables. What I'm going to do next: Collaborate with Siyi Liu to improve the drag-and-connect functionality in the block interface, focusing on enhancing user interaction and reducing connection errors.
Siyi Liu What I did previously: I familiarized myself with the codebase in preparation for Sprint 2. What I'm going to do next: Next, I plan to collaborate with teammates according to our task distribution.
Dong-Jhang Wu What I did previously: Complete the remaining code refactoring. What I'm going to do next: discuss our current code progress and plan the next sprint task distribution.
Rifang Zhou What I did previously: Refer to the implementation method of repeat block in scartch. What I'm going to do next: Try to implement the repeat block by referring to the method of scartch.
Wenhui Shi What I did previously: Prepared for Sprint 2 by reviewing the codebase, writing personas, and attending meetings. What I’m going to do next: Discuss task assignments and collaborate with the team to ensure progress aligns with the project plan.
Wenjing Qi What I did previously: Attended the Agile development sharing session, gaining insights into effective workflow practices. Participated in scheduled tutor and client meetings to confirm Sprint 2 goals and expectations. What I'm going to do next: Work on modernizing the button colors for image blocks to align with the new design system. Adjust the spacing between the main workspace and the sidebar for a more compact layout. Enhance the sidebar toggle button for better visibility and usability. Reposition the action buttons ("Run", "Stop", "Upload") for improved accessibility and standardization.

Actions

Action Item	Responsible	Due Date	Status
Optimize UI interface by adding connection effects	Wenghui Shi, Wengjing Qi	Week 8	Completed
Improve dragging and connection logic for smoother operation	Siyi Liu, Yi Wang	Week 8	Completed
Develop a Repeat Block prototype in Flutter	Rifang Zhou, Dong-Jhang Wu	Week 9	Completed
Complete Sprint 1 documentation	All Team Members	Week 7	Completed

8-Hour Work Tracking

Yi Wang

During the 8-hour work period, I first joined another team’s Agile development sharing session, where I learned about their issue tracking practices, daily stand-up routine, and sprint retrospective structure. This gave me insights into how we might improve our internal documentation and team communication.

Later, I participated in our tutor and client meetings, where I assisted in confirming the goals and expected outcomes for Sprint 2. I contributed to the discussion on aligning our planned features with client priorities and clarifying how the drag-and-connect interactions could be refined.

Following the meetings, I attended our internal codebase walkthrough, during which I explored how the current block structure and connection logic are implemented. Based on the walkthrough, I collaborated with Siyi Liu to analyze the areas that need improvement in the dragging and connecting mechanics. We outlined the major pain points (e.g., imprecise alignment, unreliable snapping), and I began implementing logic adjustments to improve block interaction fluidity. I also documented the observed issues and proposed solutions in our GitLab board for better team visibility.

Siyi Liu

I started the day by attending another group’s presentation on Agile development. Their work was highlighted as an excellent example, and it gave me some helpful insights into how we might improve our own development process.After that, I joined our scheduled tutor meeting. During the session, we discussed the structure of our development phase and clarified expectations regarding our workflow, documentation, and technical planning for Sprint 2.Later in the day, we had a meeting with the client. We confirmed that our understanding of Sprint 2 goals was accurate and aligned with their expectations. This helped us move forward with clarity and confidence.Following the client meeting, our team held an internal group meeting. We walked through the current codebase together to better understand how each part functions. We also discussed what needs to be done for Sprint 2 and divided up the responsibilities. I was assigned to work on improving the drag-and-connect functionality of the block module.

Dong-Jhang Wu

So, during this week's eight hours, the first half was mainly spent reporting our progress to the client and tutor. In the second half, I focused on explaining to our team members how I refactored the code to ensure everyone understood the current structure. I also identified the higher-priority tasks, assigned them to our members, and conducted some research on the assigned work (specifically the implementation of the repeat block).

Rifang Zhou

Today's 8-hour work focused on advancing Sprint 2 planning and foundational development. Actively participated in Sprint 2 discussions, defining the core goal to enhance low-code platform basics, and took on the "basic Repeat Block implementation" task. Aligned with the team on requirements, including fixed-loop support and nested sub-blocks, and outlined a phased technical plan. Analyzed Scratch's Repeat Block logic, decomposing its UI design, loop execution, and scope management. Designed a Flutter-adapted solution with custom-drawn borders, drag-and-drop interactions, and dynamic sub-block handling, plus a logic layer for loop control and sub-block iteration. Developed a Repeat Block prototype in Flutter: built a parameterized block UI with rounded borders and input validation, created a loop controller for sub-block iteration and nesting, and validated state management to handle edge cases like invalid inputs and empty blocks. Participated in the Sprint 1 retrospective, discussed past issues with the team, updated them on the Repeat Block demo progress, and outlined next steps for engine integration and testing.

Wenhui Shi

I first attended the Group Meeting and Client Meeting with my team members. We set the overall goals and milestones for Sprint 2. In the task distribution phase, I was assigned two development tasks: adding glow effects for block selection and hover, and adding a click sound effect when selecting a block. After receiving the tasks, I spent time reading the existing project code carefully, mainly focusing on the CommandManager and DraggableBlock parts. I tried to understand how the blocks were drawn and how the interactions worked. Based on the task requirements, I planned the direction for modifying the code, including the new fields for managing states, where to add interaction responses, and how to realize the visual effects. Later, I started building the basic framework for the glow effect. I implemented the initial handling for selection and hovering.

Wenjing Qi

During the 8-hour work period, I focused on several key tasks to enhance our user interface and align with the new design guidelines:

Agile Sharing Session: Attended another group's Agile development sharing session. This provided valuable insights into their workflow and documentation practices, which I plan to incorporate into our own processes. Client and Tutor Meetings: Participated in meetings to confirm Sprint 2 goals. I contributed to discussions that clarified expectations for our development tasks moving forward.

UI Improvements: Modernized Button Colors: Updated all image block button colors to match the new design system, ensuring hover and focus states are consistent across all UI elements. Adjusted Layout Spacing: Reduced the gap between the main workspace and sidebar to create a more compact and user-friendly layout. Sidebar Toggle Button Enhancement: Increased the size of the sidebar toggle button and changed its color to black for better visibility and usability. Repositioned Action Buttons: Aligned the "Run", "Stop", and "Upload" buttons to a more logical position closer to the workspace edge, standardizing padding and margins with other UI components. Documentation: Documented the changes made in the GitLab board for better visibility and to keep the team informed of the UI enhancements.

This structured approach has helped improve our project's UI while ensuring alignment with client expectations and team goals for Sprint 2.