xd-to-flutter-plugin

xd-to-flutter-plugin copied to clipboard

After an unexpectedly long hiatus, we now have a long term plan with Adobe for keeping the plugin updated. This will include bug fixes, feature updates, and working with the community to integrate pull requests.

As a first step, I'll be carrying out an issue triage over the next week or two: following up with questions, adding labels, doing some internal testing, and starting to assemble a prioritized list of issues to tackle. Once that's done, I will shift to investigating new XD features and APIs that have been added since the v1.0.0 plugin release, to see if there's anything we should add. Those will be added here as issues where it makes sense, and similarly prioritized in my internal list.

Once that's complete, I'll start putting together the next milestone or two, and the real work will start. If you want to help out, please feel free to review and update issues, suggest features (as new issues), or submit pull requests.

Things will likely start out slow as I ramp back up and make my way through the backlog, but should pick up steam over the next few weeks. The winter holidays will be a bit of a damper, but I'm hopeful that we can begin the new year with some momentum.

Thank you for your patience.

PS. I'll likely add comments to this issue to capture a few thoughts. Maybe a touch unorthodox, but I want to keep things open.

Note to self: New features to investigate:

• padding
• component states
• hovers
• plugin drag and drop (explore potential use cases)
• anchor links
• stacks
• scroll groups
• design tokens
• nested components
• 3d transforms
• auto height text

Note: "master components" have been renamed to "main components".

First pass on issues complete - focused on answering questions, and requesting info where needed. The next sweep will be on attempting to reproduce open issues and fix as appropriate, starting with higher quality issue reports (ie. those with more information).

Could the example be updated to show more interactions like Tap? One solid example that demonstrates what is working is a big help considering not a lot is being published in the internet (ie. YouTube) about this plugin and its use.

For rapid prototyping this is simply amazing. It closes the loop on fail fast, fail often..

Thx, Johnny

Could the example be updated to show more interactions like Tap?

The CampVibes example has two tap interactions: The "Gear Guide" button, and the "<" (back) button. Are you looking for something else?

I've put together the first two milestones. They may shift a bit as I dig into things.

The biggest things people can do to help is to provide useful information with issues. Almost all our reports are just "I got this error", which can be very time consuming to isolate without a sample file or repro steps.

I've tentatively completed all of the v1.0.1 update objectives. It mostly focuses on bug fixes, but includes a couple minor feature updates, so I may rename to v1.1.

Hoping to complete testing and prepare a build before the holidays, then focus on new features in the new year.

Any updates on the progress @gskinner ?

Sorry for the wait, have some fresh new updates!

v1.1 shipped in mid-February focused mostly on bug fixes

v2.0 of both the plugin and the adobe_xd package should ship in the next week or two

• support for XD Stacks
• support for XD padding & background elements
• substantial refactor of layout code to support the above and make future changes simpler
• support for null safety in both the adobe_xd package & the plugin output
• improved handling of pubspec.yaml checks, including checking SDK versions
• updated to work with the UXP Developer Tool
• more fixes

Another quick update.

v2.0 shipped in late April with the features listed above.

v3.0 should ship in the next week or so with a focus on developer oriented feature additions:

• data parameters for repeat grids
• group export modes: export inline, export as build method, export as builder param, replace with custom code
• added scroll bars for all scrolling elements
• more fixes (as always)

Still assembling a plan for v4.0, but I'd like to start looking into two things:

• further optimizing layout output (ex. identifying specific layout scenarios where simpler Widgets can be used)
• support for more interactive elements, like input text fields. This one is a bit tricky, since it also necessitates a mechanism for wiring business logic to the inputs.