<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.flowcode.co.uk/wiki/index.php?action=history&amp;feed=atom&amp;title=Blueprints</id>
	<title>Blueprints - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://www.flowcode.co.uk/wiki/index.php?action=history&amp;feed=atom&amp;title=Blueprints"/>
	<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Blueprints&amp;action=history"/>
	<updated>2026-04-17T16:43:46Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.34.1</generator>
	<entry>
		<id>https://www.flowcode.co.uk/wiki/index.php?title=Blueprints&amp;diff=41951&amp;oldid=prev</id>
		<title>SteveT: Created page with &quot;__TOC__  ==Introduction==  Blueprints are a new feature introduced in Flowcode v11.0.1 which allow a simple high-level flowchart to be created within a Flowcode project.   Blu...&quot;</title>
		<link rel="alternate" type="text/html" href="https://www.flowcode.co.uk/wiki/index.php?title=Blueprints&amp;diff=41951&amp;oldid=prev"/>
		<updated>2026-02-03T15:50:01Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;__TOC__  ==Introduction==  Blueprints are a new feature introduced in Flowcode v11.0.1 which allow a simple high-level flowchart to be created within a Flowcode project.   Blu...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;__TOC__&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
&lt;br /&gt;
Blueprints are a new feature introduced in Flowcode v11.0.1 which allow a simple high-level flowchart to be created within a Flowcode project. &lt;br /&gt;
&lt;br /&gt;
Blueprints work in a similar way to normal Flowcode macros but have no code associated with them and cannot be simulated or compiled into a working program. They can be viewed as a flowchart and as pseudocode and use a subset of the normal flowchart icons.&lt;br /&gt;
&lt;br /&gt;
Typically these can be used to describe a process or workflow associated with the Flowcode project or to be the starting point for creating a new code macro.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|+ &lt;br /&gt;
|-&lt;br /&gt;
| [[File:BlueprintExample.png]] || [[File:BlueprintPseudocode.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Creating a new Blueprint==&lt;br /&gt;
&lt;br /&gt;
New Blueprints can be created via Project explorer or via the &amp;quot;New Macro&amp;quot; button in the User Macros menu.&lt;br /&gt;
&lt;br /&gt;
[[File:NewBlueprint(via project explorer).png]]&lt;br /&gt;
&lt;br /&gt;
[[File:NewBlueprint(via menu).png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When creating a new Blueprint, a Name and optional Description can be added. These can be edited later via the Project Explorer context menu.&lt;br /&gt;
&lt;br /&gt;
[[File:BlueprintDetails.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Adding icons to a Blueprint==&lt;br /&gt;
&lt;br /&gt;
Just like a normal code macro, icons can be added to a Blueprint by dragging them from either the Command Icon toolbar or from the list of Command Icons in Project Explorer.&lt;br /&gt;
&lt;br /&gt;
When adding an icon to the Blueprint, a window will be shown when details can be entered for the icon. This is limited to a displayed name and a detailed description (which will be shown as a tooltip when the mouse is hovered over the icon). Note that not all command icons will be available for inclusion in a Blueprint.&lt;br /&gt;
&lt;br /&gt;
[[File:BlueprintEditIcon.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Viewing Blueprints==&lt;br /&gt;
&lt;br /&gt;
As with normal code macros, the same Blueprint can be viewed in different ways. For Blueprints, these view types are as a flowchart or as pseudocode. Right-click the Blueprint heading tab or the entry in Project Explorer to change the view type.&lt;br /&gt;
&lt;br /&gt;
[[File:BlueprintContextMenu.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Using Blueprints to design code==&lt;br /&gt;
&lt;br /&gt;
Blueprints are often not intended to be converted into actual executable code. For example, they may be showing a process that a user must perform.&lt;br /&gt;
&lt;br /&gt;
However, a Blueprint can also be used as an initial attempt to describe a new code macro before it has been created. In fact, experienced programmers will often design a new software routine as a collection of comments rather than writing code. Blueprints can be used to mimic this initial design process.&lt;br /&gt;
&lt;br /&gt;
A Blueprint can be converted to actual executable icons via the context menu in Project Explorer.&lt;br /&gt;
&lt;br /&gt;
Once converted, the Blueprint will be replaced with an equivalent macro that can be edited to create an actual executable function. Each icon will be converted to its code-based equivalent and will retain the displayed name, and detailed description entered when creating the Blueprint.&lt;br /&gt;
&lt;br /&gt;
The macro will need to be edited to create the appropriate code required, but starting with a Blueprint allows you to concentrate on the outline and overall function of a new macro without being bogged-down with specific details.&lt;/div&gt;</summary>
		<author><name>SteveT</name></author>
		
	</entry>
</feed>