Skip to content

Stager scene for Property Editor #8573

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 10 commits into from
Dec 4, 2024
Merged

Conversation

elliette
Copy link
Member

Work towards #1948

This PR:

  • creates a Stager scene for the Property Editor, so that the Property Editor is in its own side panel of the mock editor
  • when the Stager scene is first run, shows a text input for the DTD URI. This allows the DTD URI to be specified during development

Follow-up:

  • connecting the Property Editor to the provided DTD URI

@elliette elliette requested a review from a team as a code owner November 28, 2024 00:13
@elliette elliette requested review from kenzieschmoll and removed request for a team November 28, 2024 00:13
final GlobalKey<FormState> formKey;

// We assume a DTD is available on 8500. There's a VS Code task that
// launches this as part of the standalone_ui/editor_sidebar config.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I guess this should say standalone_ui/property_editor_sidebar config?

Is the intention that the mock editor will have the ability to send fake editor events, or that you'd just always use this with a real IDE and connect to DTD that it spawned (if the latter, the DTD being spawned on 8500 is probably pointless?).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking it might be useful to send fake editor events eventually (to simulate clicking on a widget) but currently I'm just using a real IDE.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm this file keeps being generated (I'm not sure what triggers it). I've been manually deleting it but it looks like I missed it in this latest commit. @kenzieschmoll this is related to DevTools extensions, right? I can delete it for now, but I want to figure out what is creating it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I would recommend deleting it for now. I think this might be related to switching to workspaces. Feel free to file a bug and I will take a look.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good, removed and opened #8589

),
return Align(
alignment: Alignment.topCenter,
child: Expanded(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Expanded should only be used as a direct child of a flex widget like Column or Row

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops thanks, removed the expanded!

Copy link
Member

@kenzieschmoll kenzieschmoll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm with one comment

@elliette elliette merged commit 6911ac1 into flutter:master Dec 4, 2024
24 checks passed
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants