Bug 485946 - Code completion for port references in a connector should show only relevant ports
Summary: Code completion for port references in a connector should show only relevant ...
Status: NEW
Alias: None
Product: Papyrus-rt
Classification: Modeling
Component: textual (show other bugs)
Version: 0.7.2   Edit
Hardware: All All
: P3 normal
Target Milestone: Future   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-15 11:37 EST by Ernesto Posse CLA
Modified: 2016-10-31 12:46 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ernesto Posse CLA 2016-01-15 11:37:37 EST
When typing a reference to a port in a connector, code completion should show only relevant ports. E.g.

model M
{
    protocol P1 {}
    protocol P2 {}
    capsule C1 { port p1 : P1; }
    capsule C2 { conjugate port p2 : P2; }
    capsule C3 { port q1 : P2; conjugate port q2 : P1; }
    capsule Top
    {
        part c1 : C1;
        part c2 : C2;
        part c3 : C3;
        connect <source> to <target>; // (*)
    }
}

when typing <source> in line (*), it should show only the following options:

c1.p1
c2.p2
c3.q1
c3.q2

(and no ports from any other capsule part in another capsule).

Then, once a port is selected, typing <target> should show only ports that can be connected, namely ports typed by the same protocol which have the dual conjugation, and enough replication factor.

To account for the replication factor we need to take into account both the relevant part's replication factor as well as the port's replication factor.
Comment 1 Simon Redding CLA 2016-02-05 16:29:31 EST
Does not gate the June release 1.0 Papyrus-RT release
Comment 2 Charles Rivet CLA 2016-10-31 12:01:28 EDT
Important feature for user-friendly behaviour modeling.
Moving to 0.9.0
Comment 3 Ernesto Posse CLA 2016-10-31 12:06:01 EDT
(In reply to Charles Rivet from comment #2)
> Important feature for user-friendly behaviour modeling.
> Moving to 0.9.0

This doesn't make sense: textual is not part of 0.9.0.
Comment 4 Charles Rivet CLA 2016-10-31 12:46:39 EDT
Missed the "textual" part...
Textual support is handled by MVP6 (Textually Ployglot!), which is currently not assigned to a release.
Moving to Future