feat(ui): add toolbar and popup for ThoughtPlanSketch #331

- Added a toolbar with a popup action to the ThoughtPlanSketch UI.
- Removed steps 6-8 from the plan.devin files as they are no longer necessary.

Author: phodal

core/src/main/kotlin/cc/unitmesh/devti/sketch/ui/ThoughtPlanSketchProvider.kt

@@ -3,19 +3,33 @@ package cc.unitmesh.devti.sketch.ui
 import cc.unitmesh.devti.sketch.ui.code.CodeHighlightSketch
 import cc.unitmesh.devti.sketch.ui.plan.MarkdownPlanParser
 import cc.unitmesh.devti.sketch.ui.plan.PlanItem
+import com.intellij.icons.AllIcons
 import com.intellij.lang.Language
+import com.intellij.openapi.actionSystem.ActionManager
+import com.intellij.openapi.actionSystem.AnAction
+import com.intellij.openapi.actionSystem.AnActionEvent
+import com.intellij.openapi.actionSystem.DefaultActionGroup
+import com.intellij.openapi.fileEditor.FileEditorManager
 import com.intellij.openapi.project.Project
+import com.intellij.openapi.ui.popup.JBPopup
+import com.intellij.openapi.ui.popup.JBPopupFactory
+import com.intellij.openapi.ui.popup.util.MinimizeButton
 import com.intellij.ui.components.JBCheckBox
 import com.intellij.ui.components.JBPanel
 import com.intellij.ui.components.JBScrollPane
+import com.intellij.ui.components.panels.Wrapper
 import com.intellij.util.ui.JBEmptyBorder
 import com.intellij.util.ui.JBUI
+import com.intellij.util.ui.UIUtil
 import java.awt.BorderLayout
 import java.awt.FlowLayout
+import java.awt.event.MouseAdapter
+import java.awt.event.MouseEvent
 import javax.swing.Box
 import javax.swing.BoxLayout
 import javax.swing.JComponent
 import javax.swing.JLabel
+import javax.swing.JPanel
 
 class ThoughtPlanSketchProvider : LanguageSketchProvider {
     override fun isSupported(lang: String): Boolean = lang == "plan"
@@ -43,26 +57,90 @@ class PlanSketch(
         layout = BoxLayout(this, BoxLayout.Y_AXIS)
         border = JBEmptyBorder(JBUI.insets(8))
     }
+    
+    private val actionGroup = DefaultActionGroup(createConsoleActions())
+    private val toolbar = ActionManager.getInstance().createActionToolbar("PlanSketch", actionGroup, true).apply {
+        targetComponent = panel
+    }
+    
+    private val titleLabel = JLabel("Thought Plan").apply {
+        border = JBUI.Borders.empty(0, 10)
+    }
+    
+    private val toolbarPanel = JPanel(BorderLayout()).apply {
+        add(titleLabel, BorderLayout.WEST)
+        add(toolbar.component, BorderLayout.EAST)
+    }
+    
+    private val toolbarWrapper = Wrapper(JBUI.Panels.simplePanel(toolbarPanel)).also {
+        it.border = JBUI.Borders.customLine(UIUtil.getBoundsColor(), 1, 1, 1, 1)
+    }
 
     init {
         createPlanUI()
 
         val scrollPane = JBScrollPane(contentPanel)
         panel.add(scrollPane, BorderLayout.CENTER)
+        panel.add(toolbarWrapper, BorderLayout.NORTH)
+        
         add(panel, BorderLayout.CENTER)
     }
+    
+    private fun createConsoleActions(): List<AnAction> {
+        val popupAction = object : AnAction("Popup", "Show in popup window", AllIcons.Ide.External_link_arrow) {
+            override fun displayTextInToolbar(): Boolean = true
+
+            override fun actionPerformed(e: AnActionEvent) {
+                executePopup().mouseClicked(null)
+            }
+        }
+
+        return listOf(popupAction)
+    }
+    
+    private fun executePopup(): MouseAdapter = object : MouseAdapter() {
+        override fun mouseClicked(e: MouseEvent?) {
+            var popup: JBPopup? = null
+            popup = JBPopupFactory.getInstance()
+                .createComponentPopupBuilder(panel, null)
+                .setProject(project)
+                .setResizable(true)
+                .setMovable(true)
+                .setTitle("Thought Plan")
+                .setCancelButton(MinimizeButton("Hide"))
+                .setCancelCallback {
+                    popup?.cancel()
+                    // Return the panel to its original location
+                    remove(panel)
+                    add(panel, BorderLayout.CENTER)
+                    revalidate()
+                    repaint()
+                    true
+                }
+                .setFocusable(true)
+                .setRequestFocus(true)
+                .createPopup()
+
+            val editor = FileEditorManager.getInstance(project).selectedTextEditor
+            if (editor != null) {
+                popup.showInBestPositionFor(editor)
+            } else {
+                popup.showInFocusCenter()
+            }
+        }
+    }
 
     private fun createPlanUI() {
         planItems.forEachIndexed { index, planItem ->
             val titlePanel = JBPanel<JBPanel<*>>(FlowLayout(FlowLayout.LEFT)).apply {
                 border = JBUI.Borders.empty()
             }
 
-            val titleText = if (planItem.completed) 
-                "<html><b>${index + 1}. ${planItem.title} ✓</b></html>" 
-            else 
+            val titleText = if (planItem.completed)
+                "<html><b>${index + 1}. ${planItem.title} ✓</b></html>"
+            else
                 "<html><b>${index + 1}. ${planItem.title}</b></html>"
-                
+
             val sectionLabel = JLabel(titleText)
             sectionLabel.border = JBUI.Borders.empty()
             titlePanel.add(sectionLabel)

core/src/main/resources/genius/en/code/plan.devin

@@ -47,12 +47,6 @@ Here is the rule you should follow:
 4. Propose and explain the necessary code modifications to resolve `<user.question>`, ensuring that edge cases are
    properly handled. Analyze these modifications before implementing them.
 5. Edit the source code in the repo to resolve `<user.question>`.
-6. If a script to reproduce the issue has been created, execute it again on the updated repository to confirm that
-   `<user.question>` is resolved.
-7. It is best practice to find and run tests related to the modified files to ensure no new issues have been introduced
-   and to confirm that these tests still pass.
-8. Once you have verified the solution, provide a summary of the changes made and the final status of the issue. Then
-   use the `submit` command to provide the complete response back to the user.
 
 If `<user.question>` directly contradicts any of these steps, follow the instructions from `<user.question>`
 first. Be thorough in your thinking process, so it's okay if it is lengthy.

core/src/main/resources/genius/zh/code/plan.devin

@@ -47,12 +47,6 @@ Here is the rule you should follow:
 4. Propose and explain the necessary code modifications to resolve `<user.question>`, ensuring that edge cases are
    properly handled. Analyze these modifications before implementing them.
 5. Edit the source code in the repo to resolve `<user.question>`.
-6. If a script to reproduce the issue has been created, execute it again on the updated repository to confirm that
-   `<user.question>` is resolved.
-7. It is best practice to find and run tests related to the modified files to ensure no new issues have been introduced
-   and to confirm that these tests still pass.
-8. Once you have verified the solution, provide a summary of the changes made and the final status of the issue. Then
-   use the `submit` command to provide the complete response back to the user.
 
 If `<user.question>` directly contradicts any of these steps, follow the instructions from `<user.question>`
 first. Be thorough in your thinking process, so it's okay if it is lengthy.