How jbenjaminhc/flutter_ide_proy works
Project type and purpose
• This is primarily a cross‐platform Flutter application (desktop, web, mobile) whose core function is a visual “widget maker” that lets users drag-and-drop UI elements, edit their properties, generate Dart code, and even live-compile/run snippets.
• In addition, there is a separate Dart “live_compilation_server” that compiles Dart widget code on the fly.
• There is also a static documentation site under docs/.
File structure
• Platform folders: android/, ios/, linux/, macos/, windows/, web/ each contain the Flutter platform integration layers.
• Application core under lib/:
– lib/ui/ (presentation pages, widgets, theme, routes, utilities)
– lib/interactors/ (orchestration/business-logic)
– lib/data/ (domain models: widget_elements, properties, code_builder, string_builder)
– lib/templates/ (built-in UI templates)
• Code-generation scripts under lib/data/widget_elements/scripts/ generate the metadata-based widget wrappers.
• Tests under test/ and test_driver/.
• live_compilation_server/: standalone Dart server project (bin, lib, windows/linux/macOS integration) that takes generated code, compiles it, and streams back results.
• docs/: static site with Gulp build, CSS/JS assets for www.widgetmaker.dev.
README for architecture insights
• Widget-Elements sub-system is the “meta-model”: a fourth tree over Flutter’s Element tree.
• Properties sub-system abstracts widget constructor arguments and provides UI controls for editing.
• Code generation: the code_builder and string_builder modules turn the in-memory widget tree into Dart source.
• Live compile: the user can see a “Play” mode where code is sent to the live_compilation_server.
Crucial details
• Major sub‐systems (UI, interactor, data model, codegen, live server, templates)
• Platform integration as consumers of the Flutter core
• Don’t omit the code-generation scripts or the docs pipeline
• Keep the focus on layering and the client-server interaction for “Play” mode