Is there a way to hide intermediate arrowheads in PlantUML activity diagrams? - uml

I'm trying to remove the intermediate arrowhead in the activity diagram circled in red below:
#startuml
start
repeat
:read data;
:generate diagrams;
repeat while (more data?) is (yes)
->no;
stop
#enduml
Source: PlantUML docs - Activity Diagram (new) - repeat
I've tried adding -[hidden]-> after (yes), but that hides the entire arrow which is not what I'm looking for.
Instead, I need the circled arrowhead above to be hidden.

Related

which tool can draw the diagram like this

The following diagram like this image, the draw style is special, the line is free

Full Documentation, i.e. Reference, of Android Material Themes and Styles

I have two specific and several more general questions which are all related to the availability of documentation for material theming in Android.
The general questions are the result of the specific questions.
According to the official docs [1], [2], [3], [4] and blogs [5], [6], [7] about Android Material Theming one should adopt the following theme values for branding
colorPrimary
colorPrimaryVariant
colorOnPrimary
colorSecondary
colorSecondaryVariant
colorOnSecondary
Those are also the values which are preset when one creates a new Android project with the wizard.
According to [2] one should use the Material Color Tool to pick colors, check the colors in various previews and also assess their accessibility, in particular their legibility.
After one has chosen a primary and secondary color, the tool automatically recommends a matching text color as well as a darker and lighter variant for each color.
The problems starts, when one exports the chosen colors to an android XML file.
(The link is in the upper right corner of the Tool).
The exported values are named
primaryColor
primaryLightColor
primaryDarkColor
secondaryColor
secondaryLightColor
secondaryDarkColor
primaryTextColor
secondaryTextColor
Obviously, there is a mismatch in the number and names of the attributes between what the theme expects and what the color tool exports.
Moreover, according to [6] and [8] the primary and secondary color (colorPrimary, colorSecondary) are supposed to be used as background colors (for certain elements of the UI) with foreground elements (such as text) printed on top of them (using colorOnPrimary and colorOnSecondary, resp.).
Also, [6] tells us that the secondary color should preferably be a bright complement to the primary color.
Hence, I decided for a light yellow on which black text is perfectly legible.
However, I had to find out that androidx.preference.PreferenceFragmentCompat uses the secondary color (colorSecondary) as the foreground color of the caption of preference groups on a background which is colored with colorBackground which equals white.
Obviously, a bright yellow on white background is anything but legible.
This leads me to my first two, specific questions
Question 1: How are the colors of the Material Color Picking tool supposed to be mapped onto the theme attributes?
Question 2: Is it correct that the primary and secondary color are also used as text colors on surface background or is this simply a bug in the style used by PreferenceFragmentCompat for captions?
This surprising experience led my to more general questions.
According to the official docs and my understanding views and in particular widgets are governed by styles, e.g. TextAppearance.MaterialComponents.Caption for a TextView which is used as a caption.
These styles do not assign specific values to the attributes which they define, but refer to "semantic" values which act as a placeholder such as colorPrimary and which are defined by a theme.
Then the theme assigns specific values to these semantic values, possibly using another step of indirection, e.g. by referring to named colors.
Assigning custom values to the semantically named values of a theme is supposed to be the main anchor point to adopt a theme like Theme.MaterialComponents.DayNight without the need to redefine all individual styles separately.
However, more or less by accident, I found the styles for TextView such as TextAppearance.MaterialComponents.Caption, TextAppearance.MaterialComponents.Body1.
Again, more or less by accident, I found the theme attributes colorSurface, colorError, colorBackground.
They are listed in the blog 6.
This leads to the following general questions
Question 3: Is there any reference which completely lists all styles which are already defined in by the material design library and explains
what purpose they serve
in which context they should be applied to views (aka widgets)
which subclass of View the style supports (i.e. a edit field, a radio button, etc.)
which semantic attributes of a theme the style uses for what part
Question 4: Is there any reference which completely list all semantic values which are defined by the material design library and explains
their type (i.e. a color, a font size, a dimension)
their intended purpose (e.g. should be light background color)
how they are supposed to interact with other semantic values (e.g. should contrast with color xyz, should be at least be larger than the double of size xyz)
I am thinking of a reference like a typical reference for an API.
I am not looking for the 1000th blog article which again recaps the basic attributes from above.
I already had a look at https://material.io/, but it seems that there is no such thing.

How to change color of a rectangle element in Enterprise architect Whiteboard diagram

I am new to EA, and for my high level layered architecture, I just want to draw a whiteboard diagram with few rectangles. I want to change the colour of the rectangles, However, the right click context pop for colour is not changing my rectangle colour. Any inputs on this is soo appreciated...Thanks
You can't change it. Those elements are created with the help of shape scripts. If you take for example the rounded rectangle you see that they don't regard the user color settings. You can either manipulate the shape scripts in the Whiteboard MDG yourself or ask Sparx for a new feature. (If you want to see a change in your lifetime I'd recommend the first.)
Alternatively just draw a Boundary which can be set to Solid which enables color filling.

How to change the default label positions of connectors in Enterprise Architect

I'm drawing activity diagram by Enterprise Architect 12. The diagram type is Activity under UML Behavioral. I found the positions of the labels of connectors are close to the target element as shown in the picture. It's very confusing.
How to change the default label positions to make them close to the source element as shown in picture?
Or is there any easy way to change the label of connector from Target Top Label to Source Top Label?
Better you use Guards for the label which you find in the Constraints tab. These appear in the middle label position and enclosed in square brackets. This is actually what you want to show.
For your amusement here's my original answer
There is no way to change the label position the way you want it out-of-the-box. You will need to write a script to do that.
There are two ways to accomplish such a script. The most comfortable is to use an add-in that responds to EA_OnPostNewConnector. You would then need to check whether the connector is one from a Decision to an Action and move the label accordingly.
The second one is to have a simple script (you might edit in EA's scripting window) that you run for an open diagram to scan for all Decisions in a diagram and alter the label position accordingly.
Altering the label
Once you got a connector from a Decision to an Action at hand you will need to change the label position like this:
get the according connector from DiagramLinks since it has the label position
get the element IDs from Connector.ClientID and .SupplierID and retrieve the elements with Respository.GetElementByID(<id>)
assign both elements to either decision or action by looking into the Element.Type
get the according DiagramObjects from the diagram which match the both elements (so you can get their position on the diagram)
now it's time for a little trigonometry: the position (DiagramElement.Left, .Right, .Top and .Bottom contain the appropriate coordinates) of the two elements makes out a vector at which end you calculate (I will leave you some fun) the label position where you think it should go
finally you take this coordinate and put it into the label position (see below).
The label position is stored in DiagramObject.Geometry. This is a semicolon separated string where one tag is LRT=<colon-list>;. <colon-list> itself is a colon-separated list where two are something like OX=-1:OY=-71: and represent the label position. This is a position relative to the "normal" position where the label is placed initially by EA.
So all in all: lot's of fun awaiting you :-/

HTML/CSS/JS translation - is this grid in my project? If not - do I need one to code this project?

I need to translate PSD file into HTML/CSS/JS...
Here is this project:
https://s15.postimg.org/s421pj5mj/PSD.jpg
https://s24.postimg.org/8xq87z3v9/PSD_2.jpg
QUESTION What are those 1.vertical and 2.horizontal sky-blue lines and how are they supposed to help me as for somebody who translates this PSD into HTML/CSS/JS ? Don't they seem a bit chaotic?
Despite being blue in your example, these are called "Redlines". The lines are meant to help you see the alignment, sizing, and spacing of elements.
For example, there is one center line down the very middle. You can use that to see that the "Creative Digital Solutons" text is centered, as is the the "Personal Services" text, "Responsive web" section, and "Latest project" section.
You can also see that at the very bottom of the second image, certain pieces of text in each column should line up with certain pieces in other columns.
Usually you will find a particular element or group of elements like this:
With the red lines I added you can see that the icons should all be the same width, and the left side of the icons should align with the left side of "Latest Posts".
Sometimes these redlines contain specific measurements (font: 14pt, margin: 10px, etc.), but this one doesn't, so you just have to use the lines to help you visualize
Yes it is chaotic, but that's how it goes sometimes

Resources