Skip to content

[Feature]: Generate graphical notation builders #440

Open

Description

@antoineatsoprasteria

What type of issue is this?

  • Bug report
  • Feature request

Prerequisites

  • I have written a descriptive issue title
  • I have verified that I am running the latest version of the SysML2.NET
  • I have searched open and closed issues to ensure it has not already been reported

Description

Generate one Build{Production} per graphical production (grammar from #438), returning a renderer-independent notation tree: nodes with kind, name compartment, titled compartments and rows, boundary-feature labels and nested view; edges with kind, label, and per-end role name, multiplicity and c-adornments. Text is composed from literals plus calls to the existing textual builders (BuildUsageDeclaration, BuildValuePart, BuildMultiplicityRange, …); branch choice at union productions comes from the #439 table.

Report every production unreachable from root-view. Today 13 are, likely spec errata: reference-subsetting (missing from type-relationship), metadata-def (never joins definition-node), concerns-compartment, performed-by-compartment, event-edge, among others.

Caveat: the textual builders keep a per-element ownedRelationship cursor in CursorCache. Each label needs its own TextualNotationWriterContext; sharing one across a diagram yields wrong text silently.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions