Could someone please help me removing "notes" header for notes from the element displayed on a diagram? I mean the actual word: "notes"
I guess you mean the "notes" header that is shown in the notes compartment of the element if you check the "show notes" checkbox in the "Feature and Compartment Visibility" dialog?
I'm afraid you won't be able to remove that, unless you write a shapescript to duplicate the default shape minus the "notes" header.
Another option might be to create a note element on the diagram and link that to the elements notes using "Link Note to element feature"
Additional advantage of this approach is that you can keep the text formatting in the note element, which is lost in the element compartment.
Related
This is a property in an ibd diagram using sysml1.3.
I don't know what this red letter A is in the low right corner. It's the only item that has it. I guess I have done something to get it but I don't know what and googling it has not given any answer. Can someone explain it?
It contains an attachment (Linked Document). Use Ctrl-Alt-D to view it. Use the context menu to delete (or edit) it.
I would just add that in some cases by default EA (v 14) can open document like diagrams - in full view, especially for CTRL+ALT+D shortcut (or right click on element with Linked Document and after selecting from context menu option Linked Document).
For below flows EA can open Dynamic Document tab by default, as preview next to the i.e. Element Properties, instead of Linked Document:
Start > Explore > Properties > Linked Document or
Show > Portals > Window > Document > Linked Document
Default Document tab by default instead of Linked Document
On Dynamic Document you won't find option to delete Linked Document:
Delete is not available for Dynamic Document
Just switch to the Linked Document, from hamburger select delete and that's it:
Delete is available for Linked Document
I'm new to Magnolia, and I'm making my own module.
I have a dialog box when adding a component and I want to change next fields below dynamically using a select field.
Example:
Select field with {"type 1", "type 2", ...}
IF "type 1" is selected
->show a text field below
ELSE
->show a basicUpload field below
Thanks in advance.
I believe same was already discussed here and few other places if you look over questions tagged "magnolia".
Long story short, fields are atomic, independent entities. They do not know about each other. So the only way to create such dynamic connection is over "parent" form. You need to extend form presenter and field factory (if you want select that would be SelectFieldFactory) and in there, when field is created, attach value changed or similar listener to it so when value is changed in the field, you can inform presenter to make some other field visible or hide it.
IIRC you can see example of that done in External Forms module (if you have access to enterprise code). Not sure if any of the community modules show the same.
I'm trying to create a "Quicklink" document for customizing the allowed connector types between elements. Our UML Profile already exists like below:
Big version here: http://i.stack.imgur.com/kcKQT.png
And this imports as an MDG Technology just fine.
However, when I add a "Quicklink" document to the profile and import it as an MDG Technology, I get the error "Encountered an improper argument". Those of you familiar with MDG Technologies in Sparx EA knows that there is no logging of any sort as to why it failed. Unfortunately, the documentation is just as unhelpful.
Here is my Quicklink document:
//Source Element Type,Source Stereotype Filter,Target Element Type,Target Stereotype Filter,Diagram Filter,New Element Type,New Element Stereotype,New Link Type,New Link Stereotype,New Link Direction,New Link Caption,New Link & Element Caption,Create Link,Create Element,Disallow Self Connector,Exclusive Stereotype Filter + No Inherit from Metatype,Menu Group,Complexity Level,Target Must be Parent,Embed Element,Precedes Separator LEAF,Precedes Separator GROUP,Dummy Column,
Feature,ChiFeature,Requirement,ChiRequirement,,,,Realization,,to,satisfies,,TRUE,,TRUE,TRUE,Requirement,0,,,,,,
My question is, is there any way for me to find out why the Quicklink document is invalid. Alternatively, is there someone more experienced with this that can see the issue?
In answer to your first question: no, I'm afraid not. As you note, EA is not very user-friendly when it comes to debugging extensions.
Happily, I've spotted the problem: you've got too many columns. Instead of filling in a dummy value at the end you've added an additional comma, which means an extra column. Replace that with a 0 and you should be OK. (Plus, of course, there shouldn't be a comma at the end of the comment line either.)
So try
//Source Element Type,Source Stereotype Filter,Target Element Type,Target Stereotype Filter,Diagram Filter,New Element Type,New Element Stereotype,New Link Type,New Link Stereotype,New Link Direction,New Link Caption,New Link & Element Caption,Create Link,Create Element,Disallow Self Connector,Exclusive Stereotype Filter + No Inherit from Metatype,Menu Group,Complexity Level,Target Must be Parent,Embed Element,Precedes Separator LEAF,Precedes Separator GROUP,Dummy Column
Feature,ChiFeature,Requirement,ChiRequirement,,,,Realization,,to,satisfies,,TRUE,,TRUE,TRUE,Requirement,0,,,,,0
i am not able to discover how to use the alt/combined fragment correctly in starUML,as in there is no way that i am able to provide the condition after the alt fragment appears.can any1 just list down the procedure as to how to do it or a link to some good tutorial.
If you are using StarUML 2 (Beta), you can go through these simple steps:
Add Combined fragment to your sequence diagram:
If you try to add operand(alt partition) through context menu, you'll see that there's no option to add new operand:
3.To achieve this, you can simple copy the already defined operand and paste it under Combined Fragment:
After that, simply add condition clauses in "guard" property of operands and adjust operand heights:
I had just found the steps as following.
Please refer how to set "alt combinedFragment at starUML due to I have no 10 reputation to post image.
1.create a sequence diagram.
2.add a CombinedFragment1 into diagram.
3.change the "seq CombinedFragment1 " to "alt CombinedFragment1 "
4.select the "Interaction Operand"
5.left-click at the "atl CombinedFragment1 ",you will found the one "InteractionOperand1" added into the "alt CombinedFragment1 ".
6.add the 2nd "InteractionOperand", same with step 4,step5, there will a parting line like the following.
7.set the InteractionOperand's Guard data,my is "isInit",you will found it at the alt frame.
8.add the 2nd Guard data,same with the step7.
9.move the diagram to the proper location.
while,I still have something unknown, for example, how to make the frame located at the top front and add a relationship with the "B method".
Wish it helpful to u.
Add an Interaction Operand to a Combined Fragment. When you select the Interaction Operand you should see in the Properties Inspector a 'Guard' field. You can type your condition just there.
Many thanks for your posts.
By the way, I noticed when adding a Combined Fragment from the left Pane,
that the alt keyword could be displayed as shown below,
after selecting the interactionOperator from the right pane,
NB: other useful keywords such as the "loop" one are also available from the above list
When you add a 'Combined Fragment' double click on the name on the diagram
Then you get a small icon with 3 horizontal lines to the left of the name
When you click on that you can get as much interaction operands as you wish
I need to show in a page a list of, let's say, person's properties that should be rendered more or less as follow:
name: Name
date: 1/1/2000
other: Other
Reading the doc they say:
The LABEL element may be used to attach information to controls.
So, is it the right tag to encompass the names of the properties like name, date...
even if there's not an <input> to associate with?
Nope, as per Quentin’s answer.
However, in HTML5, <dl> can be used for generic associations where <label> isn’t appropriate.
No.
It says that it can associate information with controls.
It does not say that it can associate information with anything else.
See also the newer (but draft) specification:
Some elements, not all of them form-associated, are categorized as
labelable elements. These are elements that can be associated with a
label element.
button input (if the type attribute is not in the hidden state) keygen
meter output progress select textarea
No, it is not correct to use the label element like that.
The important thing here is the meaning of may.
The LABEL element may be used to attach information to controls.
RFC 2119 (which the HTML4 spec follows) defines may:
May: This word, or the adjective "OPTIONAL", mean that an item is truly optional
So here, may does not mean the label element can be used for other purposes; it just means that it is not required to use a label element with controls.
As far as alternatives go, it depends what you want to achieve. If you are just trying to follow the spec closely, then I suggest using p and a strong element for each pair. If you want the data to be more meaningful to computers, you could consider using one of the Microformat specifications.
I partially agree with the answers so far but want to add that if you want to use labels for some reason, then I would display the property values in read-only controls, and then your labels will be valid.
I've done this using appropriate styling to differentiate the read-only controls from the functioning controls to avoid confusing your users. This was on a sequence of pages which built up the information gathered from the user in a wizard.
I have this link to W3C - the "Editor's Draft" as opposed to the link above which is the "Working Draft", which states that you can associate it with any element - as long as it's 'labelable' - even though this is a subsection of the Form section. It states earlier that a labelable element does not have to be within a form.
http://dev.w3.org/html5/spec/single-page.html#the-label-element