Added file attachment support to chat templates (#614)

app/MindWork AI Studio/Tools/DropLayers.cs

@@ -0,0 +1,11 @@
+namespace AIStudio.Tools;
+
+public static class DropLayers
+{
+    public const int ROOT = 0;
+    
+    public const int PAGES = 10;
+    public const int ASSISTANTS = 20;
+    
+    public const int DIALOGS = 100;
+}

app/MindWork AI Studio/Tools/Event.cs

@@ -34,6 +34,10 @@ public enum Event
     // RAG events:
     RAG_AUTO_DATA_SOURCES_SELECTED,
     
+    // File attachment events:
+    REGISTER_FILE_DROP_AREA,
+    UNREGISTER_FILE_DROP_AREA,
+    
     // Send events:
     SEND_TO_GRAMMAR_SPELLING_ASSISTANT,
     SEND_TO_ICON_FINDER_ASSISTANT,

app/MindWork AI Studio/Tools/Validation/FileExtensionValidation.cs

@@ -32,15 +32,16 @@ public static class FileExtensionValidation
         /// </summary>
         ATTACHING_CONTENT,
     }
-    
+
     /// <summary>
     /// Validates the file extension and sends appropriate MessageBus notifications when invalid.
     /// </summary>
     /// <param name="useCae">The validation use case.</param>
     /// <param name="filePath">The file path to validate.</param>
+    /// <param name="validateMediaFileTypes">Whether to validate media file types against provider capabilities.</param>
     /// <param name="provider">The selected provider.</param>
     /// <returns>True if valid, false if invalid (error/warning already sent via MessageBus).</returns>
-    public static async Task<bool> IsExtensionValidWithNotifyAsync(UseCase useCae, string filePath, Settings.Provider? provider = null)
+    public static async Task<bool> IsExtensionValidWithNotifyAsync(UseCase useCae, string filePath, bool validateMediaFileTypes = true, Settings.Provider? provider = null)
     {
         var ext = Path.GetExtension(filePath).TrimStart('.').ToLowerInvariant();
         if(FileTypeFilter.Executables.FilterExtensions.Contains(ext))
@@ -63,6 +64,10 @@ public static class FileExtensionValidation
                         TB("Images are not supported at this place")));
                     return false;
                 
+                // In this use case, we don't validate the provider capabilities:
+                case UseCase.ATTACHING_CONTENT when !validateMediaFileTypes:
+                    return true;
+                
                 // In this use case, we can check the provider capabilities:
                 case UseCase.ATTACHING_CONTENT when capabilities.Contains(Capability.SINGLE_IMAGE_INPUT) ||
                                                     capabilities.Contains(Capability.MULTIPLE_IMAGE_INPUT):