Skip to content

Term native is misleading and creates unnecessary confusion #3

Description

@Joebeazelman

Most developers want to create native UIs that work and operate identically to Fusion's apps UI windows and elements. Currently, the API has limitations on the functionality and presentation of third-party plugins, making them second class UIs.

The term "Native" UI in this sample means native in context of the Win32 host platform Fusion 360 is running on, not in the context of the Fusion 360 application itself. The resulting UI has limited if any utility for most plugins.

Aside from not being consistent with Fusion 360's UI, it doesn't work across other host platforms.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions