• editor/src/dispatcher.rs
  • Updated menu_bar_message_handler to include the guides_visible state from the document's guide handler.
• editor/src/messages/menu_bar/menu_bar_message_handler.rs
  • Imported GuideMessage for guide-related actions.
  • Added a guides_visible boolean field to track guide visibility.
  • Integrated a 'Guides' menu list entry with a checkbox icon to toggle guide visibility via GuideMessage::ToggleGuidesVisibility.
• editor/src/messages/portfolio/document/document_message.rs
  • Imported GuideMessage.
  • Added Guide(GuideMessage) as a child message variant to DocumentMessage.
• editor/src/messages/portfolio/document/document_message_handler.rs
  • Imported GuideMessageHandler and GuideMessageContext.
  • Added a guide_handler field to DocumentMessageHandler and initialized it with a default GuideMessageHandler.
  • Implemented message processing for DocumentMessage::Guide to delegate to the guide_handler.
  • Extended common actions with those from the guide_handler.
• editor/src/messages/portfolio/document/guide_message.rs
  • Added a new file defining the GuideMessage enum, which includes variants for creating, moving, deleting, rendering overlays, toggling visibility, and setting hovered guides.
• editor/src/messages/portfolio/document/guide_message_handler.rs
  • Added a new file defining GuideMessageHandler, responsible for managing a collection of Guide objects, their visibility, and processing GuideMessages to update guide states and trigger UI updates.
• editor/src/messages/portfolio/document/mod.rs
  • Exported the new guide_message and guide_message_handler modules.
• editor/src/messages/portfolio/document/overlays/guide_overlays.rs
  • Added a new file containing guide_overlay function to draw guide lines on the canvas, extending them to the viewport edges and highlighting hovered guides.
• editor/src/messages/portfolio/document/overlays/mod.rs
  • Exported the new guide_overlays module.
• editor/src/messages/portfolio/document/overlays/overlays_message_handler.rs
  • Imported GuideMessage.
  • Dispatched GuideMessage::GuideOverlays to render guide overlays during canvas drawing.
• editor/src/messages/portfolio/document/utility_types/guide.rs
  • Added a new file defining GuideId (a unique identifier), GuideDirection (Horizontal/Vertical), and Guide (containing ID, direction, and position) structs.
• editor/src/messages/portfolio/document/utility_types/mod.rs
  • Exported the new guide utility type module.
• frontend/src/components/panels/Document.svelte
  • Imported generateGuideId from the WASM package.
  • Added draggingGuideId and draggingGuideDirection state variables for guide drag operations.
  • Implemented getViewportElement, getGuideMousePosition, and isInRulerArea helper functions.
  • Created createGuideDragHandlers and startGuideDrag to manage pointer and keyboard events during guide dragging.
  • Implemented handleGuideDragStart to create a new guide and initiate dragging when triggered from a ruler.
  • Updated RulerInput components to listen for the guideDragStart event.
• frontend/src/components/widgets/inputs/RulerInput.svelte
  • Imported createEventDispatcher to emit custom events.
  • Added isDragging state to track active drag operations.
  • Implemented handlePointerDown to dispatch a guideDragStart event with guide direction and mouse coordinates, and capture the pointer.
  • Implemented handlePointerUp to release the pointer capture.
  • Applied pointerdown and pointerup event listeners to the ruler element, along with a dynamic cursor style.
• frontend/wasm/src/editor_api.rs
  • Imported GuideMessage, GuideDirection, and GuideId.
  • Added set_random_seed for UUID generation.
  • Added generate_guide_id to create unique identifiers for guides.
  • Added create_guide WASM function to send GuideMessage::CreateGuide to the editor.
  • Added move_guide WASM function to send GuideMessage::MoveGuide to the editor.
  • Added delete_guide WASM function to send GuideMessage::DeleteGuide to the editor.

• The pull request is titled "Guide-1" and is explicitly marked as "PR-1 out of 3", indicating it's the initial installment of a multi-part feature implementation by jsjgdh.
• No specific comments or reviews have been recorded in the provided context.

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.