ichthyo/LUMIERA.clone
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
LUMIERA.clone/uml/Lumiera.xmi

3218 lines
194 KiB
Text
Raw Normal View History

DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
<?xml version="1.0" encoding="UTF-8"?>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<XMI verified="false" xmi.version="1.2" timestamp="2017-03-03T23:58:31" xmlns:UML="http://schema.omg.org/spec/UML/1.3">
DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
<XMI.header>
<XMI.documentation>
<XMI.exporter>umbrello uml modeller http://umbrello.kde.org</XMI.exporter>
<XMI.exporterVersion>1.6.9</XMI.exporterVersion>
<XMI.exporterEncoding>UnicodeUTF8</XMI.exporterEncoding>
</XMI.documentation>
<XMI.metamodel xmi.version="1.3" href="UML.xml" xmi.name="UML"/>
</XMI.header>
<XMI.content>
<UML:Model isSpecification="false" isAbstract="false" isLeaf="false" xmi.id="m1" isRoot="false" name="UML Model">
<UML:Namespace.ownedElement>
<UML:Stereotype visibility="public" isSpecification="false" namespace="m1" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="folder" name="folder"/>
<UML:Stereotype visibility="public" isSpecification="false" namespace="m1" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="datatype" name="datatype"/>
<UML:Stereotype visibility="public" isSpecification="false" namespace="m1" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="constructor" name="constructor"/>
<UML:Stereotype visibility="public" isSpecification="false" namespace="m1" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="friend" name="friend"/>
<UML:Stereotype visibility="public" isSpecification="false" namespace="m1" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="virtual" name="virtual"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<UML:Stereotype visibility="public" isSpecification="false" namespace="m1" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="owns" name="owns"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<UML:Stereotype visibility="public" isSpecification="false" namespace="m1" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="interface" name="interface"/>
DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
<UML:Model stereotype="folder" visibility="public" isSpecification="false" namespace="m1" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="Logical View" name="Logical View">
<UML:Namespace.ownedElement>
<UML:Package stereotype="folder" visibility="public" isSpecification="false" namespace="Logical View" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="Datatypes" name="Datatypes">
<UML:Namespace.ownedElement>
<UML:DataType stereotype="datatype" visibility="public" isSpecification="false" namespace="Datatypes" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="mhSdaAG81L4V" name="int"/>
<UML:DataType stereotype="datatype" visibility="public" isSpecification="false" namespace="Datatypes" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="15L0hJXhwcFR" name="char"/>
<UML:DataType stereotype="datatype" visibility="public" isSpecification="false" namespace="Datatypes" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="c4Twqn0aUQB4" name="bool"/>
<UML:DataType stereotype="datatype" visibility="public" isSpecification="false" namespace="Datatypes" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="aPBblD5kGQlv" name="float"/>
<UML:DataType stereotype="datatype" visibility="public" isSpecification="false" namespace="Datatypes" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="hGddsq3TsUPg" name="double"/>
<UML:DataType stereotype="datatype" visibility="public" isSpecification="false" namespace="Datatypes" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="HOEjoPmPovyX" name="short"/>
<UML:DataType stereotype="datatype" visibility="public" isSpecification="false" namespace="Datatypes" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="83IMS1F7HsjA" name="long"/>
<UML:DataType stereotype="datatype" visibility="public" isSpecification="false" namespace="Datatypes" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="gkbWE0CWOQFD" name="unsigned int"/>
<UML:DataType stereotype="datatype" visibility="public" isSpecification="false" namespace="Datatypes" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="n1aawY72aPM0" name="unsigned short"/>
<UML:DataType stereotype="datatype" visibility="public" isSpecification="false" namespace="Datatypes" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="Qc5iSoq7YRdn" name="unsigned long"/>
<UML:DataType stereotype="datatype" visibility="public" isSpecification="false" namespace="Datatypes" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="RoHoEUz0UZaO" name="string"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<UML:DataType stereotype="datatype" visibility="public" isSpecification="false" namespace="Datatypes" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="pFknC1jVXUTk" name="Session*"/>
DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
</UML:Namespace.ownedElement>
</UML:Package>
<UML:Package stereotype="folder" visibility="public" isSpecification="false" namespace="Logical View" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="dzlPCiVfMhDw" name="GUI">
<UML:Namespace.ownedElement>
<UML:Package stereotype="folder" visibility="public" isSpecification="false" namespace="dzlPCiVfMhDw" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="AP2Jw6O9SyPl" name="Backbone">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<UML:Namespace.ownedElement>
<UML:Class visibility="public" isSpecification="false" namespace="AP2Jw6O9SyPl" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="zt9QqECndhuG" name="Controller">
<UML:GeneralizableElement.generalization>
<UML:Generalization xmi.idref="iWjGfYBc3xqk"/>
</UML:GeneralizableElement.generalization>
</UML:Class>
<UML:Class visibility="public" isSpecification="false" namespace="AP2Jw6O9SyPl" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="YVUu5DY24gSv" name="BusTerm"/>
<UML:Class visibility="public" isSpecification="false" namespace="AP2Jw6O9SyPl" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="zQV7dGUdKiTL" name="Tangible"/>
<UML:Class visibility="public" isSpecification="false" namespace="AP2Jw6O9SyPl" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="CIgVjFGNUjOp" name="Widget">
<UML:GeneralizableElement.generalization>
<UML:Generalization xmi.idref="iwOwLnrzR97o"/>
</UML:GeneralizableElement.generalization>
</UML:Class>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<UML:Class visibility="public" isSpecification="false" namespace="AP2Jw6O9SyPl" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="AAXrURgiB2s9" name="CoreService"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</UML:Namespace.ownedElement>
DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
</UML:Package>
<UML:Package stereotype="folder" visibility="public" isSpecification="false" namespace="dzlPCiVfMhDw" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="iJ1021VZA242" name="Timeline">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<UML:Namespace.ownedElement>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<UML:Class visibility="public" isSpecification="false" namespace="iJ1021VZA242" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="r2bQMphsIClM" name="TrackPresenter">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<UML:GeneralizableElement.generalization>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<UML:Generalization xmi.idref="9NfcZGrNO8qZ"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</UML:GeneralizableElement.generalization>
</UML:Class>
<UML:Class visibility="public" isSpecification="false" namespace="iJ1021VZA242" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="TxRGe5zBPLEk" name="ClipWidget">
<UML:GeneralizableElement.generalization>
<UML:Generalization xmi.idref="XrxbmnLBD6Pa"/>
</UML:GeneralizableElement.generalization>
</UML:Class>
<UML:Class visibility="public" isSpecification="false" namespace="iJ1021VZA242" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="YML3K4y9h5tE" name="ClipPresenter">
<UML:GeneralizableElement.generalization>
<UML:Generalization xmi.idref="cz4YZYaRa9pv"/>
</UML:GeneralizableElement.generalization>
</UML:Class>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<UML:Class visibility="public" isSpecification="false" namespace="iJ1021VZA242" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="8QIySCNjv8Nm" name="TrackBodyWidget"/>
<UML:Class visibility="public" isSpecification="false" namespace="iJ1021VZA242" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="IlnerbEbwJog" name="TrackHeadWidget"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<UML:Interface stereotype="interface" visibility="public" isSpecification="false" namespace="iJ1021VZA242" isAbstract="true" isLeaf="false" isRoot="false" xmi.id="wB7sY2nRjOXn" name="Element">
<UML:Classifier.feature>
<UML:Operation visibility="public" isSpecification="false" isQuery="false" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="m71ADYgKdI1Q" name="allocate">
<UML:BehavioralFeature.parameter>
<UML:Parameter visibility="private" isSpecification="false" xmi.id="FNAvlwvJBiEK" type="WIX6g3bhkPMX" value="" name="evaluation"/>
</UML:BehavioralFeature.parameter>
</UML:Operation>
</UML:Classifier.feature>
</UML:Interface>
<UML:Class visibility="public" isSpecification="false" namespace="iJ1021VZA242" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="WIX6g3bhkPMX" name="DisplayEvaluation">
<UML:Classifier.feature>
<UML:Attribute visibility="private" isSpecification="false" xmi.id="MAWVsNUcUWni" type="1l72I7ToPys3" name="manager"/>
<UML:Operation visibility="public" isSpecification="false" isQuery="false" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="SjGuD1cFQas5" name="evaluateChild">
<UML:BehavioralFeature.parameter>
<UML:Parameter visibility="private" isSpecification="false" xmi.id="cv0y6n6BWVRw" type="wB7sY2nRjOXn" value="" name="element"/>
</UML:BehavioralFeature.parameter>
</UML:Operation>
</UML:Classifier.feature>
</UML:Class>
<UML:Interface stereotype="interface" visibility="public" isSpecification="false" namespace="iJ1021VZA242" isAbstract="true" isLeaf="false" isRoot="false" xmi.id="1l72I7ToPys3" name="DisplayManager">
<UML:Classifier.feature>
<UML:Operation visibility="public" isSpecification="false" isQuery="false" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="87ehnyLmiQo0" name="evaluate">
<UML:BehavioralFeature.parameter>
<UML:Parameter visibility="private" isSpecification="false" xmi.id="XFnvBfyB9ht1" type="wB7sY2nRjOXn" value="" name="element"/>
</UML:BehavioralFeature.parameter>
</UML:Operation>
</UML:Classifier.feature>
</UML:Interface>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</UML:Namespace.ownedElement>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<XMI.extension xmi.extender="umbrello">
<diagrams>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<diagram showopsig="1" linecolor="#3e0f00" snapx="10" showattribassocs="1" snapy="10" linewidth="0" showattsig="1" textcolor="#000000" isopen="0" showpackage="0" showpubliconly="1" showstereotype="1" name="display_evaluation" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" canvasheight="260" canvaswidth="450" localid="-1" snapcsgrid="1" showgrid="1" showops="1" griddotcolor="#d3d3d3" backgroundcolor="#ffffff" usefillcolor="1" fillcolor="#ffffc0" zoom="100" xmi.id="tyAwJXVRd8yU" documentation="" showscope="1" snapgrid="1" showatts="1" type="1">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<widgets>
<classwidget linecolor="#3e0f00" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-540" showattsigs="601" showstereotype="1" y="-310" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="h5idAOxedsSi" width="100" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="YML3K4y9h5tE" showscope="1" height="30" showopsigs="601"/>
<classwidget linecolor="#3e0f00" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-670" showattsigs="601" showstereotype="1" y="-330" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="NHOSxrLoU1Ho" width="110" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="r2bQMphsIClM" showscope="1" height="30" showopsigs="601"/>
<interfacewidget linecolor="#3e0f00" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="0" showpackage="1" x="-670" showattsigs="601" showstereotype="1" y="-450" showattributes="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" drawascircle="0" localid="L1yddNoXLwTc" width="220" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="wB7sY2nRjOXn" showscope="1" height="50" showopsigs="601"/>
<classwidget linecolor="#3e0f00" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-670" showattsigs="601" showstereotype="1" y="-510" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="9LtY72a9biMe" width="190" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="WIX6g3bhkPMX" showscope="1" height="40" showopsigs="601"/>
<interfacewidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="0" showpackage="0" x="-890" showattsigs="601" showstereotype="1" y="-540" showattributes="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" drawascircle="0" localid="0Ujit5F0Q6YV" width="170" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="1l72I7ToPys3" showscope="1" height="50" showopsigs="601"/>
</widgets>
<messages/>
<associations>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="r2bQMphsIClM" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="TdTehsF1A2Mv" widgetbid="YML3K4y9h5tE" totalcountb="2" type="510" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
<startpoint startx="-560" starty="-300"/>
<endpoint endx="-540" endy="-300"/>
</linepath>
</assocwidget>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="r2bQMphsIClM" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="Tw2630Yx9gph" widgetbid="wB7sY2nRjOXn" totalcountb="2" type="511" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
<startpoint startx="-620,62255859375" starty="-330"/>
<endpoint endx="-560,7003784179688" endy="-400"/>
<point x="-620,62255859375" y="-350,5836486816406"/>
<point x="-560,7003784179688" y="-350,5836486816406"/>
</linepath>
</assocwidget>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="1" widgetaid="YML3K4y9h5tE" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="Sk9bQzG6aNWX" widgetbid="wB7sY2nRjOXn" totalcountb="2" type="511" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
<startpoint startx="-500" starty="-310"/>
<endpoint endx="-560,7003784179688" endy="-400"/>
<point x="-500" y="-350,1945495605469"/>
<point x="-560,7003784179688" y="-350,1945495605469"/>
</linepath>
</assocwidget>
<assocwidget linecolor="#3e0f00" indexa="1" usesdiagramfillcolor="0" widgetbid="1l72I7ToPys3" indexb="1" linewidth="0" seqnum="" textcolor="#000000" usesdiagramusefillcolor="0" totalcounta="2" totalcountb="2" widgetaid="WIX6g3bhkPMX" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" visibilityA="1" visibilityB="1" usefillcolor="1" fillcolor="#ffff00" changeabilityA="900" xmi.id="MAWVsNUcUWni" changeabilityB="900" type="512">
<linepath layout="Polyline">
<startpoint startx="-670" starty="-510"/>
<endpoint endx="-720" endy="-510"/>
</linepath>
<floatingtext linecolor="none" usesdiagramfillcolor="1" linewidth="none" textcolor="none" usesdiagramusefillcolor="1" x="-700" showstereotype="1" y="-530" text="manager" font="Sans Serif,9,-1,5,50,0,0,0,0,0" localid="2R0fh13uMDp8" pretext="-" role="710" width="70" isinstance="0" posttext="" usefillcolor="1" fillcolor="none" xmi.id="7jPGPdall6Fd" height="20"/>
</assocwidget>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="1l72I7ToPys3" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="#3e0f00" seqnum="" totalcounta="2" xmi.id="62hs6uTYehTp" widgetbid="wB7sY2nRjOXn" totalcountb="2" type="502" textcolor="#000000" usefillcolor="1" linewidth="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
<startpoint startx="-721" starty="-490"/>
<endpoint endx="-670" endy="-410"/>
<point x="-721" y="-410"/>
</linepath>
<floatingtext linecolor="none" usesdiagramfillcolor="1" linewidth="none" textcolor="none" usesdiagramusefillcolor="1" x="-730" showstereotype="1" y="-430" text="invokes" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="jjlNCOhc9Dp4" pretext="" role="703" width="60" isinstance="0" posttext="" usefillcolor="1" fillcolor="none" xmi.id="wvwv9HfrxE5j" height="20"/>
</assocwidget>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="wB7sY2nRjOXn" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="#3e0f00" seqnum="" totalcounta="2" xmi.id="yABcqeRWgUdK" widgetbid="WIX6g3bhkPMX" totalcountb="2" type="502" textcolor="#000000" usefillcolor="1" linewidth="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
<startpoint startx="-633" starty="-450"/>
<endpoint endx="-633" endy="-470"/>
</linepath>
<floatingtext linecolor="none" usesdiagramfillcolor="1" linewidth="none" textcolor="none" usesdiagramusefillcolor="1" x="-630" showstereotype="1" y="-470" text="triggers recursive" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="UzRv4l9lTu9f" pretext="" role="703" width="110" isinstance="0" posttext="" usefillcolor="1" fillcolor="none" xmi.id="GoFP24RyzOr6" height="20"/>
</assocwidget>
</associations>
</diagram>
</diagrams>
</XMI.extension>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</UML:Package>
<UML:Package visibility="public" isSpecification="false" namespace="dzlPCiVfMhDw" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="50pVMRCQE3mT" name="Gtk">
<UML:Namespace.ownedElement>
<UML:Class visibility="public" isSpecification="false" namespace="50pVMRCQE3mT" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="04Gq3mqRDSTZ" name="Gtk::Layout"/>
<UML:Class visibility="public" isSpecification="false" namespace="50pVMRCQE3mT" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="QTe1L5jo295e" name="Gtk::Frame"/>
</UML:Namespace.ownedElement>
DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
</UML:Package>
</UML:Namespace.ownedElement>
</UML:Package>
<UML:Package stereotype="folder" visibility="public" isSpecification="false" namespace="Logical View" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="ZJjfeyODnhwR" name="Proc">
<UML:Namespace.ownedElement>
<UML:Package stereotype="folder" visibility="public" isSpecification="false" namespace="ZJjfeyODnhwR" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="3HXNyiJX20Ae" name="Session">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<UML:Namespace.ownedElement>
<UML:Interface stereotype="interface" visibility="public" isSpecification="false" namespace="3HXNyiJX20Ae" isAbstract="true" isLeaf="false" isRoot="false" xmi.id="vXeW5rShP4KV" name="Session"/>
<UML:Interface stereotype="interface" visibility="public" isSpecification="false" namespace="3HXNyiJX20Ae" isAbstract="true" isLeaf="false" isRoot="false" xmi.id="i28J9X534hZ9" name="SessManager">
<UML:Classifier.feature>
<UML:Operation visibility="public" isSpecification="false" isQuery="false" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="pVqpkd56Npnb" name="operator->">
<UML:BehavioralFeature.parameter>
<UML:Parameter kind="return" xmi.id="wogG2YqUjTK1" type="pFknC1jVXUTk"/>
</UML:BehavioralFeature.parameter>
</UML:Operation>
<UML:Operation visibility="public" isSpecification="false" isQuery="false" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="tgE8kCyZfoMP" name="load"/>
<UML:Operation visibility="public" isSpecification="false" isQuery="false" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="PSTlFEK4S4pe" name="save"/>
<UML:Operation visibility="public" isSpecification="false" isQuery="false" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="6Y9d0aMtHa01" name="close"/>
<UML:Operation visibility="public" isSpecification="false" isQuery="false" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="kyZPlvm8LFta" name="reset"/>
</UML:Classifier.feature>
</UML:Interface>
<UML:Class visibility="public" isSpecification="false" namespace="3HXNyiJX20Ae" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="SDesIUWO0dz1" name="LifecycleAdvisor">
<UML:Classifier.feature>
<UML:Operation visibility="public" isSpecification="false" isQuery="false" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="KsbZ85POo9Lg" name="pullUp"/>
<UML:Operation visibility="public" isSpecification="false" isQuery="false" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="zzlJ9A4Ksadb" name="shutDown"/>
<UML:Operation visibility="public" isSpecification="false" isQuery="false" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="cv5AydHGTsoa" name="openSessionInterface"/>
</UML:Classifier.feature>
</UML:Class>
<UML:Class visibility="public" isSpecification="false" namespace="3HXNyiJX20Ae" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="lSL6pzQhTDOj" name="CommandQueue"/>
<UML:Class visibility="public" isSpecification="false" namespace="3HXNyiJX20Ae" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="kihkGgfmWK0o" name="ProcDispatcher">
<UML:Classifier.feature>
<UML:Attribute visibility="private" isSpecification="false" xmi.id="wyW7zMFphhgG" name="deactivate"/>
<UML:Operation visibility="public" isSpecification="false" isQuery="false" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="RFgnI9xTKVIo" name="activate"/>
<UML:Operation visibility="public" isSpecification="false" isQuery="false" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="KsrSalZ00FnI" name="deactivate"/>
</UML:Classifier.feature>
</UML:Class>
<UML:Interface stereotype="interface" visibility="public" isSpecification="false" namespace="3HXNyiJX20Ae" isAbstract="true" isLeaf="false" isRoot="false" xmi.id="GkMAyqUK0GFO" name="SessionCommand"/>
<UML:Class visibility="public" isSpecification="false" namespace="3HXNyiJX20Ae" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="rUnjINDv0ZKK" name="SessionCommandService"/>
<UML:Class visibility="public" isSpecification="false" namespace="3HXNyiJX20Ae" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="k29coo6WqCqy" name="SessionImpl"/>
<UML:Class visibility="public" isSpecification="false" namespace="3HXNyiJX20Ae" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="YsfFJxnCRFW9" name="SessionSubsystem"/>
<UML:Class visibility="public" isSpecification="false" namespace="3HXNyiJX20Ae" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="mPYman5InEvb" name="SessManagerImpl"/>
<UML:Class visibility="public" isSpecification="false" namespace="3HXNyiJX20Ae" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="dfMQKri4XPmn" name="DispatcherLoop"/>
<UML:Interface stereotype="interface" visibility="public" isSpecification="false" namespace="3HXNyiJX20Ae" isAbstract="true" isLeaf="false" isRoot="false" xmi.id="MAnxOpF9GaE3" name="CommandDispatch"/>
</UML:Namespace.ownedElement>
<XMI.extension xmi.extender="umbrello">
<diagrams>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<diagram showopsig="1" linecolor="#3e0f00" snapx="10" showattribassocs="1" snapy="10" linewidth="0" showattsig="1" textcolor="#000000" isopen="0" showpackage="1" showpubliconly="1" showstereotype="1" name="session_subsystem" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" canvasheight="390" canvaswidth="960" localid="-1" snapcsgrid="1" showgrid="1" showops="1" griddotcolor="#d3d3d3" backgroundcolor="#ffffff" usefillcolor="1" fillcolor="#ffffc0" zoom="90" xmi.id="ZM3pbwOfd7Ql" documentation="service&#xa;impl&#xa;" showscope="1" snapgrid="1" showatts="1" type="1">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<widgets>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<interfacewidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="0" showpackage="0" x="-370" showattsigs="601" showstereotype="1" y="-710" showattributes="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" drawascircle="0" localid="uwmKIYlruoeT" width="90" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="vXeW5rShP4KV" showscope="1" height="40" showopsigs="601"/>
<interfacewidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="0" showpackage="0" x="-540" showattsigs="601" showstereotype="1" y="-670" showattributes="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" drawascircle="0" localid="X1ow46Rw2BHK" width="140" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="i28J9X534hZ9" showscope="1" height="100" showopsigs="601"/>
<classwidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-370" showattsigs="601" showstereotype="1" y="-490" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="ht1lYYt5Yfzc" width="90" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="k29coo6WqCqy" showscope="1" height="30" showopsigs="601"/>
<classwidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-530" showattsigs="601" showstereotype="1" y="-490" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="0z6r9unrloaJ" width="130" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="mPYman5InEvb" showscope="1" height="30" showopsigs="601"/>
<interfacewidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="0" showpackage="0" x="-1100" showattsigs="601" showstereotype="1" y="-620" showattributes="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" drawascircle="0" localid="GzbfW5BQ0azw" width="140" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="vUTLjCtthGnz" showscope="1" height="40" showopsigs="601"/>
<classwidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-1100" showattsigs="601" showstereotype="1" y="-540" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="RN28ep7sngXJ" width="130" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="YsfFJxnCRFW9" showscope="1" height="30" showopsigs="601"/>
<classwidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-910" showattsigs="601" showstereotype="1" y="-520" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="Hn0h2UoTsqaW" width="110" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="kihkGgfmWK0o" showscope="1" height="50" showopsigs="601"/>
<classwidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-850" showattsigs="601" showstereotype="1" y="-610" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="6RXalXO1LPgL" width="110" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="dfMQKri4XPmn" showscope="1" height="30" showopsigs="601"/>
<classwidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-1070" showattsigs="601" showstereotype="1" y="-720" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="Q0MxP9iTaE4K" width="170" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="rUnjINDv0ZKK" showscope="1" height="30" showopsigs="601"/>
<classwidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-710" showattsigs="601" showstereotype="1" y="-590" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="YceY9wrYwDTK" width="120" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="lSL6pzQhTDOj" showscope="1" height="30" showopsigs="601"/>
<interfacewidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="0" showpackage="0" x="-850" showattsigs="601" showstereotype="1" y="-710" showattributes="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" drawascircle="0" localid="Xeiyr7hNhJvq" width="130" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="MAnxOpF9GaE3" showscope="1" height="40" showopsigs="601"/>
<interfacewidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="0" showpackage="0" x="-1070" showattsigs="601" showstereotype="1" y="-830" showattributes="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" drawascircle="0" localid="3UXJ2jLXN3VC" width="130" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="GkMAyqUK0GFO" showscope="1" height="40" showopsigs="601"/>
<classwidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-1210" showattsigs="601" showstereotype="1" y="-830" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="sLSqZfCc8iu8" width="90" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="AAXrURgiB2s9" showscope="1" height="30" showopsigs="601"/>
<interfacewidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="0" showpackage="0" x="-710" showattsigs="601" showstereotype="1" y="-710" showattributes="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" drawascircle="0" localid="JWl0DRFVH4yq" width="140" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="OkjgF2UByyJx" showscope="1" height="40" showopsigs="601"/>
<classwidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-710" showattsigs="601" showstereotype="1" y="-530" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="BLsSvsUfp14Y" width="160" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="SDesIUWO0dz1" showscope="1" height="60" showopsigs="601"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<boxwidget width="290" showstereotype="1" x="-550" usesdiagramusefillcolor="0" y="-720" usesdiagramfillcolor="0" isinstance="0" localid="SFPt5DT0OQih" fillcolor="#ffffc0" height="280" linecolor="#000000" xmi.id="h6yyGXMa92kK" textcolor="#000000" usefillcolor="1" linewidth="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<notewidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" textcolor="#000000" usesdiagramusefillcolor="0" x="-1220" showstereotype="1" y="-780" text="in GUI&#xa;" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="UslNKbislGZA" width="60" isinstance="0" noteType="0" usefillcolor="1" fillcolor="#e6ffd5" xmi.id="shNxnUTbqlXV" height="30"/>
<notewidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" textcolor="#000000" usesdiagramusefillcolor="0" x="-910" showstereotype="1" y="-780" text="service&#xa;impl&#xa;" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="LzZpcNJ4F3PX" width="70" isinstance="0" noteType="0" usefillcolor="1" fillcolor="#e6ffd5" xmi.id="e8PPMyaCev9R" height="40"/>
<floatingtext linecolor="none" usesdiagramfillcolor="0" linewidth="0" textcolor="#000000" usesdiagramusefillcolor="0" x="-910" showstereotype="1" y="-470" text="static" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0" localid="PWP3G7XBbTvr" pretext="" role="700" width="40" isinstance="0" posttext="" usefillcolor="1" fillcolor="#ffffc0" xmi.id="dKSRnxZ7HiiZ" height="20"/>
<floatingtext linecolor="none" usesdiagramfillcolor="0" linewidth="0" textcolor="#000000" usesdiagramusefillcolor="0" x="-530" showstereotype="1" y="-460" text="static" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0" localid="f4OEWH59aVZL" pretext="" role="700" width="40" isinstance="0" posttext="" usefillcolor="1" fillcolor="#ffffc0" xmi.id="dKSRnxZ7HiiZ" height="20"/>
</widgets>
<messages/>
<associations>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="1" widgetaid="rUnjINDv0ZKK" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="vqNvRLucgl3c" widgetbid="GkMAyqUK0GFO" totalcountb="2" type="511" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<linepath layout="Polyline">
<startpoint startx="-1060" starty="-720"/>
<endpoint endx="-1060" endy="-790"/>
</linepath>
</assocwidget>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="1" widgetaid="YsfFJxnCRFW9" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="ahkHSlr1G4Qm" widgetbid="vUTLjCtthGnz" totalcountb="2" type="511" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<linepath layout="Polyline">
<startpoint startx="-1060" starty="-540"/>
<endpoint endx="-1060" endy="-580"/>
</linepath>
</assocwidget>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="1" widgetaid="dfMQKri4XPmn" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="Jn8ZrYJCuWdu" widgetbid="MAnxOpF9GaE3" totalcountb="2" type="511" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<linepath layout="Polyline">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<startpoint startx="-790,3553466796875" starty="-610"/>
<endpoint endx="-790,3553466796875" endy="-670"/>
<point x="-790,3553466796875" y="-630,4568481445312"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</linepath>
</assocwidget>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="1" widgetaid="dfMQKri4XPmn" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="gbWZ59RQKR9a" widgetbid="OkjgF2UByyJx" totalcountb="2" type="511" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<linepath layout="Polyline">
<startpoint startx="-790" starty="-610"/>
<endpoint endx="-690" endy="-670"/>
<point x="-790" y="-630"/>
<point x="-690" y="-630"/>
</linepath>
</assocwidget>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="1" widgetaid="mPYman5InEvb" usesdiagramfillcolor="1" fillcolor="none" linecolor="none" seqnum="" totalcounta="2" xmi.id="UNNmnUMGfGd5" widgetbid="i28J9X534hZ9" totalcountb="2" type="511" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<linepath layout="Polyline">
<startpoint startx="-473" starty="-490"/>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<endpoint endx="-473" endy="-570"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</linepath>
</assocwidget>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="1" widgetaid="k29coo6WqCqy" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="2ZLhpznz5WwR" widgetbid="vXeW5rShP4KV" totalcountb="2" type="511" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<linepath layout="Polyline">
<startpoint startx="-333,5" starty="-490"/>
<endpoint endx="-333,5" endy="-670"/>
</linepath>
</assocwidget>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="1" widgetaid="i28J9X534hZ9" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="7B8Ch3bX8MJP" widgetbid="vXeW5rShP4KV" totalcountb="2" type="512" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<linepath layout="Polyline">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<startpoint startx="-400" starty="-630,81396484375"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<endpoint endx="-370" endy="-670"/>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<point x="-380,81396484375" y="-630,81396484375"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</linepath>
</assocwidget>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="1" widgetaid="mPYman5InEvb" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="C89KUQhNBiSL" widgetbid="k29coo6WqCqy" totalcountb="2" type="512" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<linepath layout="Polyline">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<startpoint startx="-400" starty="-466"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<endpoint endx="-370" endy="-466"/>
</linepath>
</assocwidget>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="1" widgetaid="mPYman5InEvb" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="fCPqup9XS4Fq" widgetbid="SDesIUWO0dz1" totalcountb="2" type="512" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<linepath layout="Polyline">
<startpoint startx="-530" starty="-478"/>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<endpoint endx="-550" endy="-478"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</linepath>
</assocwidget>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="dfMQKri4XPmn" usesdiagramfillcolor="1" fillcolor="none" linecolor="none" seqnum="" totalcounta="2" xmi.id="LSrnW4bmjOM9" widgetbid="lSL6pzQhTDOj" totalcountb="2" type="512" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<linepath layout="Polyline">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<startpoint startx="-740" starty="-580"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<endpoint endx="-710" endy="-580"/>
</linepath>
</assocwidget>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="kihkGgfmWK0o" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="#3e0f00" seqnum="" totalcounta="2" xmi.id="XRdEpxNnRWHz" widgetbid="dfMQKri4XPmn" totalcountb="2" type="512" textcolor="#000000" usefillcolor="1" linewidth="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<startpoint startx="-800" starty="-511,0465087890625"/>
<endpoint endx="-790,1162719726562" endy="-580"/>
<point x="-790,1162719726562" y="-511,0465087890625"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</linepath>
<floatingtext linecolor="none" usesdiagramfillcolor="1" linewidth="none" textcolor="none" usesdiagramusefillcolor="1" x="-830" showstereotype="1" y="-550" text="PImpl" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="Kc5vMuq2GxNY" pretext="" role="703" width="40" isinstance="0" posttext="" usefillcolor="1" fillcolor="none" xmi.id="D5Czp653fmkW" height="20"/>
</assocwidget>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="rUnjINDv0ZKK" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="#3e0f00" seqnum="" totalcounta="2" xmi.id="oa1E4HBEXCgX" widgetbid="MAnxOpF9GaE3" totalcountb="2" type="512" textcolor="#000000" usefillcolor="1" linewidth="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<startpoint startx="-900" starty="-710"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<endpoint endx="-850" endy="-710"/>
</linepath>
<floatingtext linecolor="none" usesdiagramfillcolor="1" linewidth="none" textcolor="none" usesdiagramusefillcolor="1" x="-900" showstereotype="1" y="-710" text="use" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="uTwmICPcoUV8" pretext="" role="703" width="30" isinstance="0" posttext="" usefillcolor="1" fillcolor="none" xmi.id="MLAbIV7TaJRO" height="20"/>
</assocwidget>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="YsfFJxnCRFW9" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="#3e0f00" seqnum="" totalcounta="2" xmi.id="l65HIjmbuCFE" widgetbid="kihkGgfmWK0o" totalcountb="2" type="502" textcolor="#000000" usefillcolor="1" linewidth="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
<startpoint startx="-1020" starty="-510"/>
<endpoint endx="-910" endy="-491"/>
<point x="-1020" y="-491"/>
</linepath>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<floatingtext linecolor="none" usesdiagramfillcolor="1" linewidth="none" textcolor="none" usesdiagramusefillcolor="1" x="-1020" showstereotype="1" y="-510" text="start/stop" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="gM9KHGkgokt6" pretext="" role="703" width="70" isinstance="0" posttext="" usefillcolor="1" fillcolor="none" xmi.id="Gbiiq8jSsrHe" height="20"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</assocwidget>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="SDesIUWO0dz1" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="#3e0f00" seqnum="" totalcounta="2" xmi.id="JlsDx7Pt5zUz" widgetbid="kihkGgfmWK0o" totalcountb="2" type="502" textcolor="#000000" usefillcolor="1" linewidth="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
<startpoint startx="-710" starty="-479"/>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<endpoint endx="-800" endy="-479"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</linepath>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<floatingtext linecolor="none" usesdiagramfillcolor="1" linewidth="none" textcolor="none" usesdiagramusefillcolor="1" x="-760" showstereotype="1" y="-480" text="controls" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="Pa0FJVicSHS3" pretext="" role="703" width="60" isinstance="0" posttext="" usefillcolor="1" fillcolor="none" xmi.id="cl7poVMRbkox" height="20"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</assocwidget>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="1" widgetaid="AAXrURgiB2s9" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="GUZLT1InA1V1" widgetbid="GkMAyqUK0GFO" totalcountb="2" type="512" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<linepath layout="Polyline">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<startpoint startx="-1120" starty="-820"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<endpoint endx="-1070" endy="-820"/>
</linepath>
</assocwidget>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<assocwidget roleBdoc="" linecolor="none" indexa="1" usesdiagramfillcolor="0" widgetbid="AAXrURgiB2s9" indexb="1" linewidth="none" seqnum="" textcolor="none" usesdiagramusefillcolor="1" totalcounta="2" totalcountb="2" roleAdoc="" widgetaid="shNxnUTbqlXV" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" visibilityA="0" visibilityB="0" usefillcolor="1" fillcolor="#ffff00" changeabilityA="900" changeabilityB="900" documentation="" type="513">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<linepath layout="Polyline">
<startpoint startx="-1170,5" starty="-780"/>
<endpoint endx="-1170,5" endy="-800"/>
</linepath>
</assocwidget>
<assocwidget roleBdoc="" linecolor="none" indexa="1" usesdiagramfillcolor="0" widgetbid="rUnjINDv0ZKK" indexb="1" linewidth="none" seqnum="" textcolor="none" usesdiagramusefillcolor="0" totalcounta="2" totalcountb="2" roleAdoc="" widgetaid="e8PPMyaCev9R" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" visibilityA="0" visibilityB="0" usefillcolor="1" fillcolor="#ffff00" changeabilityA="900" changeabilityB="900" documentation="" type="513">
<linepath layout="Polyline">
<startpoint startx="-910" starty="-740"/>
<endpoint endx="-910" endy="-720"/>
</linepath>
</assocwidget>
</associations>
</diagram>
</diagrams>
</XMI.extension>
DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
</UML:Package>
<UML:Package stereotype="folder" visibility="public" isSpecification="false" namespace="ZJjfeyODnhwR" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="wYrkFnB1ygmi" name="Builder">
<UML:Namespace.ownedElement/>
</UML:Package>
<UML:Package stereotype="folder" visibility="public" isSpecification="false" namespace="ZJjfeyODnhwR" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="RN68is2j9X47" name="Player">
<UML:Namespace.ownedElement/>
</UML:Package>
<UML:Package stereotype="folder" visibility="public" isSpecification="false" namespace="ZJjfeyODnhwR" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="FLcFLmuIIl0X" name="Engine">
<UML:Namespace.ownedElement/>
</UML:Package>
</UML:Namespace.ownedElement>
</UML:Package>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<UML:Interface stereotype="interface" visibility="public" isSpecification="false" namespace="Logical View" isAbstract="true" isLeaf="false" isRoot="false" xmi.id="vUTLjCtthGnz" name="Subsys"/>
<UML:Interface stereotype="interface" visibility="public" isSpecification="false" namespace="Logical View" isAbstract="true" isLeaf="false" isRoot="false" xmi.id="OkjgF2UByyJx" name="ThreadJoinable"/>
DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
<UML:Package stereotype="folder" visibility="public" isSpecification="false" namespace="Logical View" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="nCXlkkbOjNnt" name="Backend">
<UML:Namespace.ownedElement>
<UML:Package stereotype="folder" visibility="public" isSpecification="false" namespace="nCXlkkbOjNnt" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="ZBWVrIDGeIPK" name="Scheduler">
<UML:Namespace.ownedElement/>
</UML:Package>
</UML:Namespace.ownedElement>
</UML:Package>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<UML:Generalization discriminator="" visibility="public" isSpecification="false" namespace="Logical View" child="YML3K4y9h5tE" xmi.id="cz4YZYaRa9pv" parent="zt9QqECndhuG" name=""/>
<UML:Generalization discriminator="" visibility="public" isSpecification="false" namespace="Logical View" child="zt9QqECndhuG" xmi.id="iWjGfYBc3xqk" parent="zQV7dGUdKiTL" name=""/>
<UML:Generalization discriminator="" visibility="public" isSpecification="false" namespace="Logical View" child="TxRGe5zBPLEk" xmi.id="XrxbmnLBD6Pa" parent="QTe1L5jo295e" name=""/>
<UML:Association visibility="public" isSpecification="false" namespace="Logical View" xmi.id="TdTehsF1A2Mv" name="">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="IZr82ligvi36" type="r2bQMphsIClM" name="" aggregation="composite"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="PoovU8DvjgaQ" type="YML3K4y9h5tE" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
<UML:Association stereotype="owns" visibility="public" isSpecification="false" namespace="Logical View" xmi.id="cppIrtav4tqC" name="">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="false" isSpecification="false" xmi.id="82LWUGfiM5b3" type="YML3K4y9h5tE" name="" aggregation="none"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="Ts9OiwCIk1YZ" type="TxRGe5zBPLEk" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
<UML:Association visibility="public" isSpecification="false" namespace="Logical View" xmi.id="u8UxzI77LQbn" name="">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="false" isSpecification="false" xmi.id="gFV0K44ovBCd" type="TxRGe5zBPLEk" name="" aggregation="none"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="7MupOSPGZtBY" type="04Gq3mqRDSTZ" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
<UML:Generalization discriminator="" visibility="public" isSpecification="false" namespace="Logical View" child="CIgVjFGNUjOp" xmi.id="iwOwLnrzR97o" parent="zQV7dGUdKiTL" name=""/>
<UML:Association visibility="public" isSpecification="false" namespace="Logical View" xmi.id="qcxqdq4Dj7nA" name="">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="false" isSpecification="false" xmi.id="TMTVpmdFeWnX" type="zQV7dGUdKiTL" name="" aggregation="none"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="JLE0jvtZXoOB" type="YVUu5DY24gSv" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<UML:Generalization discriminator="" visibility="public" isSpecification="false" namespace="Logical View" child="r2bQMphsIClM" xmi.id="9NfcZGrNO8qZ" parent="zt9QqECndhuG" name=""/>
<UML:Association visibility="public" isSpecification="false" namespace="Logical View" xmi.id="ofNcGNdOluKC" name="">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="4iv0qGkYq8Cg" type="8QIySCNjv8Nm" name="" aggregation="aggregate"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="IU9TJbJ5EghU" type="TxRGe5zBPLEk" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
<UML:Association visibility="public" isSpecification="false" namespace="Logical View" xmi.id="2JrlBBvDtoBi" name="">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="false" isSpecification="false" xmi.id="5wGt4QZKuilB" type="r2bQMphsIClM" name="" aggregation="none"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="H3GVhvyhCpTN" type="IlnerbEbwJog" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
<UML:Association visibility="public" isSpecification="false" namespace="Logical View" xmi.id="0ObsBkaGgo9i" name="">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="false" isSpecification="false" xmi.id="Eg28NmJcnX8U" type="r2bQMphsIClM" name="" aggregation="none"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="S6Cftf0t1ZjA" type="8QIySCNjv8Nm" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<UML:Abstraction visibility="public" isSpecification="false" namespace="Logical View" supplier="wB7sY2nRjOXn" xmi.id="Tw2630Yx9gph" client="r2bQMphsIClM" name=""/>
<UML:Abstraction visibility="public" isSpecification="false" namespace="Logical View" supplier="wB7sY2nRjOXn" xmi.id="Sk9bQzG6aNWX" client="YML3K4y9h5tE" name=""/>
<UML:Dependency visibility="public" isSpecification="false" namespace="Logical View" supplier="wB7sY2nRjOXn" xmi.id="62hs6uTYehTp" client="1l72I7ToPys3" name="invokes"/>
<UML:Dependency visibility="public" isSpecification="false" namespace="Logical View" supplier="WIX6g3bhkPMX" xmi.id="yABcqeRWgUdK" client="wB7sY2nRjOXn" name="triggers recursive"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<UML:Abstraction visibility="public" isSpecification="false" namespace="Logical View" supplier="GkMAyqUK0GFO" xmi.id="vqNvRLucgl3c" client="rUnjINDv0ZKK" name=""/>
<UML:Abstraction visibility="public" isSpecification="false" namespace="Logical View" supplier="vUTLjCtthGnz" xmi.id="ahkHSlr1G4Qm" client="YsfFJxnCRFW9" name=""/>
<UML:Abstraction visibility="public" isSpecification="false" namespace="Logical View" supplier="MAnxOpF9GaE3" xmi.id="Jn8ZrYJCuWdu" client="dfMQKri4XPmn" name=""/>
<UML:Abstraction visibility="public" isSpecification="false" namespace="Logical View" supplier="OkjgF2UByyJx" xmi.id="gbWZ59RQKR9a" client="dfMQKri4XPmn" name=""/>
<UML:Abstraction visibility="public" isSpecification="false" namespace="Logical View" supplier="i28J9X534hZ9" xmi.id="UNNmnUMGfGd5" client="mPYman5InEvb" name=""/>
<UML:Abstraction visibility="public" isSpecification="false" namespace="Logical View" supplier="vXeW5rShP4KV" xmi.id="2ZLhpznz5WwR" client="k29coo6WqCqy" name=""/>
<UML:Association visibility="public" isSpecification="false" namespace="Logical View" xmi.id="7B8Ch3bX8MJP" name="">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="false" isSpecification="false" xmi.id="vk34CyDa4mJi" type="i28J9X534hZ9" name="" aggregation="none"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="Z8PvGn4NwBXb" type="vXeW5rShP4KV" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
<UML:Association visibility="public" isSpecification="false" namespace="Logical View" xmi.id="C89KUQhNBiSL" name="">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="false" isSpecification="false" xmi.id="fdvhPFQwLprb" type="mPYman5InEvb" name="" aggregation="none"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="auwW3T7DZEX4" type="k29coo6WqCqy" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
<UML:Association visibility="public" isSpecification="false" namespace="Logical View" xmi.id="fCPqup9XS4Fq" name="">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="false" isSpecification="false" xmi.id="HfmaSc92W5WX" type="mPYman5InEvb" name="" aggregation="none"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="Wdk6sF8VRVLJ" type="SDesIUWO0dz1" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
<UML:Association visibility="public" isSpecification="false" namespace="Logical View" xmi.id="LSrnW4bmjOM9" name="">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="false" isSpecification="false" xmi.id="0U9UZf14Gj88" type="dfMQKri4XPmn" name="" aggregation="none"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="yGdNjwe4MTqr" type="lSL6pzQhTDOj" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
<UML:Association visibility="public" isSpecification="false" namespace="Logical View" xmi.id="XRdEpxNnRWHz" name="PImpl">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="false" isSpecification="false" xmi.id="BG1Sz9YxNAI6" type="kihkGgfmWK0o" name="" aggregation="none"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="4xBRQzIyQtCE" type="dfMQKri4XPmn" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
<UML:Association visibility="public" isSpecification="false" namespace="Logical View" xmi.id="oa1E4HBEXCgX" name="use">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="false" isSpecification="false" xmi.id="JCSgKjmNgvo6" type="rUnjINDv0ZKK" name="" aggregation="none"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="s42HvFVjnUvr" type="MAnxOpF9GaE3" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
<UML:Dependency visibility="public" isSpecification="false" namespace="Logical View" supplier="kihkGgfmWK0o" xmi.id="l65HIjmbuCFE" client="YsfFJxnCRFW9" name="start/stop"/>
<UML:Dependency visibility="public" isSpecification="false" namespace="Logical View" supplier="kihkGgfmWK0o" xmi.id="JlsDx7Pt5zUz" client="SDesIUWO0dz1" name="controls"/>
<UML:Association visibility="public" isSpecification="false" namespace="Logical View" xmi.id="GUZLT1InA1V1" name="">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="false" isSpecification="false" xmi.id="nYl3YGKWFIUs" type="AAXrURgiB2s9" name="" aggregation="none"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="Gllytqe7KBRn" type="GkMAyqUK0GFO" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
</UML:Namespace.ownedElement>
<XMI.extension xmi.extender="umbrello">
<diagrams>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<diagram showopsig="1" linecolor="#3e0f00" snapx="10" showattribassocs="1" snapy="10" linewidth="0" showattsig="1" textcolor="#000000" isopen="1" showpackage="1" showpubliconly="1" showstereotype="1" name="clip_display" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" canvasheight="360" canvaswidth="510" localid="-1" snapcsgrid="1" showgrid="1" showops="1" griddotcolor="#d3d3d3" backgroundcolor="#ffffff" usefillcolor="1" fillcolor="#ffffc0" zoom="100" xmi.id="IIIwYfFi2Hzy" documentation="" showscope="1" snapgrid="1" showatts="1" type="1">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<widgets>
<classwidget linecolor="#3e0f00" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-570" showattsigs="601" showstereotype="1" y="-260" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="h5idAOxedsSi" width="100" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="YML3K4y9h5tE" showscope="1" height="30" showopsigs="601"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<classwidget linecolor="#3e0f00" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-430" showattsigs="601" showstereotype="1" y="-210" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="NAt4DnJss1W0" width="90" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="TxRGe5zBPLEk" showscope="1" height="30" showopsigs="601"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<classwidget linecolor="#3e0f00" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-430" showattsigs="601" showstereotype="1" y="-310" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="E2pbN1LiAFnN" width="80" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="QTe1L5jo295e" showscope="1" height="30" showopsigs="601"/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<classwidget linecolor="#3e0f00" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-300" showattsigs="601" showstereotype="1" y="-190" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="VALXJQAVRx5o" width="90" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="04Gq3mqRDSTZ" showscope="1" height="30" showopsigs="601"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<classwidget linecolor="#3e0f00" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-620" showattsigs="601" showstereotype="1" y="-470" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="UHniiEFDOajg" width="70" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="zQV7dGUdKiTL" showscope="1" height="30" showopsigs="601"/>
<classwidget linecolor="#3e0f00" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-620" showattsigs="601" showstereotype="1" y="-380" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="xNsF5JZaZKGH" width="80" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="zt9QqECndhuG" showscope="1" height="30" showopsigs="601"/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<classwidget linecolor="#3e0f00" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-530" showattsigs="601" showstereotype="1" y="-450" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="sfgVKbkGyaV3" width="70" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="YVUu5DY24gSv" showscope="1" height="30" showopsigs="601"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<classwidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-720" showattsigs="601" showstereotype="1" y="-280" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="NHOSxrLoU1Ho" width="110" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="r2bQMphsIClM" showscope="1" height="30" showopsigs="601"/>
<classwidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-700" showattsigs="601" showstereotype="1" y="-140" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="e1XxgzDXqd01" width="130" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="IlnerbEbwJog" showscope="1" height="30" showopsigs="601"/>
<classwidget linecolor="none" usesdiagramfillcolor="0" linewidth="0" showoperations="1" textcolor="#000000" usesdiagramusefillcolor="0" showpubliconly="1" showpackage="0" x="-520" showattsigs="601" showstereotype="1" y="-140" showattributes="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="jZNeqAKUBpSs" width="130" isinstance="0" usefillcolor="1" fillcolor="#ffffc0" xmi.id="8QIySCNjv8Nm" showscope="1" height="30" showopsigs="601"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</widgets>
DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
<messages/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<associations>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="YML3K4y9h5tE" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="cz4YZYaRa9pv" widgetbid="zt9QqECndhuG" totalcountb="2" type="500" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<startpoint startx="-520" starty="-260"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<endpoint endx="-590,5028076171875" endy="-350"/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<point x="-520" y="-300"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<point x="-590,5028076171875" y="-300,5586547851562"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</linepath>
</assocwidget>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="zt9QqECndhuG" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="iWjGfYBc3xqk" widgetbid="zQV7dGUdKiTL" totalcountb="2" type="500" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<startpoint startx="-592" starty="-380"/>
<endpoint endx="-592" endy="-440"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</linepath>
</assocwidget>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="1" widgetaid="TxRGe5zBPLEk" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="XrxbmnLBD6Pa" widgetbid="QTe1L5jo295e" totalcountb="2" type="500" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
<startpoint startx="-400" starty="-210"/>
<endpoint endx="-400" endy="-280"/>
</linepath>
</assocwidget>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="r2bQMphsIClM" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="TdTehsF1A2Mv" widgetbid="YML3K4y9h5tE" totalcountb="2" type="510" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<startpoint startx="-610" starty="-250"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<endpoint endx="-570" endy="-250"/>
</linepath>
</assocwidget>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="YML3K4y9h5tE" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="#3e0f00" seqnum="" totalcounta="2" xmi.id="cppIrtav4tqC" widgetbid="TxRGe5zBPLEk" totalcountb="2" type="512" textcolor="#000000" usefillcolor="1" linewidth="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
<startpoint startx="-482" starty="-230"/>
<endpoint endx="-430" endy="-201"/>
<point x="-482" y="-201"/>
</linepath>
</assocwidget>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="1" widgetaid="TxRGe5zBPLEk" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="u8UxzI77LQbn" widgetbid="04Gq3mqRDSTZ" totalcountb="2" type="512" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<startpoint startx="-340" starty="-180"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<endpoint endx="-300" endy="-180"/>
</linepath>
</assocwidget>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="zQV7dGUdKiTL" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="qcxqdq4Dj7nA" widgetbid="YVUu5DY24gSv" totalcountb="2" type="512" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<linepath layout="Polyline">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<startpoint startx="-550" starty="-440"/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<endpoint endx="-530" endy="-440"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</linepath>
</assocwidget>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="1" widgetaid="r2bQMphsIClM" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="9NfcZGrNO8qZ" widgetbid="zt9QqECndhuG" totalcountb="2" type="500" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<linepath layout="Polyline">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<startpoint startx="-670,3910522460938" starty="-280"/>
<endpoint endx="-590,5028076171875" endy="-350"/>
<point x="-670,3910522460938" y="-300"/>
<point x="-590,5028076171875" y="-300"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</linepath>
</assocwidget>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="8QIySCNjv8Nm" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="ofNcGNdOluKC" widgetbid="TxRGe5zBPLEk" totalcountb="2" type="501" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<linepath layout="Polyline">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<startpoint startx="-420" starty="-140"/>
<endpoint endx="-420" endy="-180"/>
</linepath>
</assocwidget>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="1" widgetaid="r2bQMphsIClM" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="2JrlBBvDtoBi" widgetbid="IlnerbEbwJog" totalcountb="2" type="512" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<linepath layout="Polyline">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<startpoint startx="-640,1360473632812" starty="-250"/>
<endpoint endx="-640,1360473632812" endy="-140"/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</linepath>
</assocwidget>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="r2bQMphsIClM" usesdiagramfillcolor="1" fillcolor="none" linecolor="none" seqnum="" totalcounta="2" xmi.id="0ObsBkaGgo9i" widgetbid="8QIySCNjv8Nm" totalcountb="2" type="512" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<linepath layout="Polyline">
<startpoint startx="-640" starty="-250"/>
<endpoint endx="-520" endy="-140"/>
<point x="-640" y="-200"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</linepath>
</assocwidget>
</associations>
DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
</diagram>
</diagrams>
</XMI.extension>
</UML:Model>
<UML:Model stereotype="folder" visibility="public" isSpecification="false" namespace="m1" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="Use Case View" name="Use Case View">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<UML:Namespace.ownedElement>
<UML:Package stereotype="folder" visibility="public" isSpecification="false" namespace="Use Case View" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="f4aD2h2f9RdQ" name="Command">
<UML:Namespace.ownedElement/>
</UML:Package>
<UML:Actor visibility="public" isSpecification="false" namespace="Use Case View" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="zlqyX5J6PSBr" name="SessionStart"/>
<UML:Actor visibility="public" isSpecification="false" namespace="Use Case View" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="YaYgpwDph1lD" name="GlobalAction"/>
<UML:Actor visibility="public" isSpecification="false" namespace="Use Case View" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="bdUD2bZY97Fy" name="Widget"/>
<UML:Actor visibility="public" isSpecification="false" namespace="Use Case View" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="eFcxWJO7utJx" name="InteractionStateManager"/>
<UML:UseCase visibility="public" isSpecification="false" namespace="Use Case View" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="pY2KizGMCrHj" name="define command"/>
<UML:UseCase visibility="public" isSpecification="false" namespace="Use Case View" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="99tISYqG4qam" name="issue command"/>
<UML:UseCase visibility="public" isSpecification="false" namespace="Use Case View" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="fpYdG6ZODQgg" name="find subject"/>
<UML:UseCase visibility="public" isSpecification="false" namespace="Use Case View" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="GrjGOZp3PLgd" name="retrieve param"/>
<UML:UseCase visibility="public" isSpecification="false" namespace="Use Case View" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="cNavFgpTXYjv" name="note change"/>
<UML:Association visibility="public" isSpecification="false" namespace="Use Case View" xmi.id="YswNymmhvlaD" name="">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="Kt7GkuNHWzJe" type="YaYgpwDph1lD" name="" aggregation="none"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="IJv7DgllWh6U" type="fpYdG6ZODQgg" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
<UML:Association visibility="public" isSpecification="false" namespace="Use Case View" xmi.id="UsCNekYycfDK" name="">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="XYa1YtgoAbuO" type="YaYgpwDph1lD" name="" aggregation="none"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="Ff7mLEEn6QAk" type="99tISYqG4qam" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
<UML:Association visibility="public" isSpecification="false" namespace="Use Case View" xmi.id="9jhjMs3uQdtw" name="">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="XZlf8d3OGB8b" type="bdUD2bZY97Fy" name="" aggregation="none"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="NMOTlXCuGtda" type="99tISYqG4qam" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
<UML:Association visibility="public" isSpecification="false" namespace="Use Case View" xmi.id="jeU9IO6nvpS2" name="">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="QUOgdWI0seTb" type="bdUD2bZY97Fy" name="" aggregation="none"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="BfVPW6yFlSN1" type="GrjGOZp3PLgd" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
<UML:Association visibility="public" isSpecification="false" namespace="Use Case View" xmi.id="oToiGEkgg6MJ" name="">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="ccJSFn4OQXmv" type="eFcxWJO7utJx" name="" aggregation="none"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="ek8NAVOxwAfC" type="cNavFgpTXYjv" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
<UML:Association visibility="public" isSpecification="false" namespace="Use Case View" xmi.id="MNq3TBM3lgVy" name="">
<UML:Association.connection>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="RXNp57kjrt4z" type="zlqyX5J6PSBr" name="" aggregation="none"/>
<UML:AssociationEnd changeability="changeable" visibility="public" isNavigable="true" isSpecification="false" xmi.id="MQwJaZTuuIxN" type="pY2KizGMCrHj" name="" aggregation="none"/>
</UML:Association.connection>
</UML:Association>
</UML:Namespace.ownedElement>
<XMI.extension xmi.extender="umbrello">
<diagrams>
<diagram showopsig="1" linecolor="#3e0f00" snapx="25" showattribassocs="1" snapy="25" linewidth="0" showattsig="1" textcolor="#000000" isopen="1" showpackage="1" showpubliconly="1" showstereotype="1" name="CommandUsage" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" canvasheight="729" canvaswidth="750" localid="-1" snapcsgrid="0" showgrid="0" showops="1" griddotcolor="#d3d3d3" backgroundcolor="#ffffff" usefillcolor="1" fillcolor="#ffffc0" zoom="100" xmi.id="Q1qEMiNK0mHL" documentation="" showscope="1" snapgrid="0" showatts="1" type="2">
<widgets>
<boxwidget width="277" showstereotype="1" x="-50" usesdiagramusefillcolor="0" y="-375" usesdiagramfillcolor="0" isinstance="0" localid="bJB4Uoi9qGKs" fillcolor="#ffffc0" height="377" linecolor="#000000" xmi.id="wMW5l9TCAHOW" textcolor="#000000" usefillcolor="1" linewidth="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<actorwidget width="72" showstereotype="1" x="133" usesdiagramusefillcolor="0" y="-451" usesdiagramfillcolor="0" isinstance="0" localid="Et047Kv3eR6O" fillcolor="#ffffc0" height="57" linecolor="#3e0f00" xmi.id="zlqyX5J6PSBr" textcolor="#000000" usefillcolor="1" linewidth="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<actorwidget width="70" showstereotype="1" x="-150" usesdiagramusefillcolor="0" y="-350" usesdiagramfillcolor="0" isinstance="0" localid="52JSSSJgLJiR" fillcolor="#ffffc0" height="57" linecolor="#3e0f00" xmi.id="YaYgpwDph1lD" textcolor="#000000" usefillcolor="1" linewidth="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<actorwidget width="43" showstereotype="1" x="-136" usesdiagramusefillcolor="0" y="-178" usesdiagramfillcolor="0" isinstance="0" localid="1QlhRWuUWBww" fillcolor="#ffffc0" height="57" linecolor="#3e0f00" xmi.id="bdUD2bZY97Fy" textcolor="#000000" usefillcolor="1" linewidth="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<actorwidget width="132" showstereotype="1" x="-200" usesdiagramusefillcolor="0" y="-75" usesdiagramfillcolor="0" isinstance="0" localid="UsTbyiZz8LeY" fillcolor="#ffffc0" height="59" linecolor="#3e0f00" xmi.id="eFcxWJO7utJx" textcolor="#000000" usefillcolor="1" linewidth="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<usecasewidget width="115" showstereotype="1" x="98" usesdiagramusefillcolor="0" y="-249" usesdiagramfillcolor="0" isinstance="0" localid="Agq4X7zzyTaw" fillcolor="#ffffc0" height="48" linecolor="#3e0f00" xmi.id="pY2KizGMCrHj" textcolor="#000000" usefillcolor="1" linewidth="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<usecasewidget width="111" showstereotype="1" x="-25" usesdiagramusefillcolor="0" y="-250" usesdiagramfillcolor="0" isinstance="0" localid="po62fOln2ZsZ" fillcolor="#ffffc0" height="48" linecolor="#3e0f00" xmi.id="99tISYqG4qam" textcolor="#000000" usefillcolor="1" linewidth="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<usecasewidget width="85" showstereotype="1" x="-25" usesdiagramusefillcolor="0" y="-350" usesdiagramfillcolor="0" isinstance="0" localid="yUu1KUn8Is8w" fillcolor="#ffffc0" height="48" linecolor="#3e0f00" xmi.id="fpYdG6ZODQgg" textcolor="#000000" usefillcolor="1" linewidth="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<usecasewidget width="104" showstereotype="1" x="-25" usesdiagramusefillcolor="0" y="-150" usesdiagramfillcolor="0" isinstance="0" localid="RD1ccfGa9AbS" fillcolor="#ffffc0" height="48" linecolor="#3e0f00" xmi.id="GrjGOZp3PLgd" textcolor="#000000" usefillcolor="1" linewidth="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<usecasewidget width="90" showstereotype="1" x="-25" usesdiagramusefillcolor="0" y="-75" usesdiagramfillcolor="0" isinstance="0" localid="8YzVrd6Gp6sR" fillcolor="#ffffc0" height="48" linecolor="#3e0f00" xmi.id="cNavFgpTXYjv" textcolor="#000000" usefillcolor="1" linewidth="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<floatingtext linecolor="#3e0f00" usesdiagramfillcolor="0" linewidth="0" textcolor="#000000" usesdiagramusefillcolor="0" x="25" showstereotype="1" y="-375" text="core commands" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" localid="l9ztJZJuwtn9" pretext="" role="700" width="100" isinstance="0" posttext="" usefillcolor="1" fillcolor="#ffffc0" xmi.id="Xcc4ALzIrwlg" height="17"/>
</widgets>
<messages/>
<associations>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="YaYgpwDph1lD" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="YswNymmhvlaD" widgetbid="fpYdG6ZODQgg" totalcountb="2" type="503" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
<startpoint startx="-80" starty="-314"/>
<endpoint endx="-25" endy="-314"/>
</linepath>
</assocwidget>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="YaYgpwDph1lD" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="UsCNekYycfDK" widgetbid="99tISYqG4qam" totalcountb="2" type="503" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
<startpoint startx="-80" starty="-293"/>
<endpoint endx="-25" endy="-250"/>
</linepath>
</assocwidget>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="bdUD2bZY97Fy" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="9jhjMs3uQdtw" widgetbid="99tISYqG4qam" totalcountb="2" type="503" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
<startpoint startx="-93" starty="-178"/>
<endpoint endx="-25" endy="-202"/>
</linepath>
</assocwidget>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="bdUD2bZY97Fy" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="jeU9IO6nvpS2" widgetbid="GrjGOZp3PLgd" totalcountb="2" type="503" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
<startpoint startx="-93" starty="-127"/>
<endpoint endx="-25" endy="-127"/>
</linepath>
</assocwidget>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="eFcxWJO7utJx" usesdiagramfillcolor="0" fillcolor="#ffff00" linecolor="none" seqnum="" totalcounta="2" xmi.id="oToiGEkgg6MJ" widgetbid="cNavFgpTXYjv" totalcountb="2" type="503" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
<startpoint startx="-68" starty="-29"/>
<endpoint endx="-25" endy="-29"/>
</linepath>
</assocwidget>
<assocwidget indexa="1" indexb="1" usesdiagramusefillcolor="0" widgetaid="zlqyX5J6PSBr" usesdiagramfillcolor="255" fillcolor="none" linecolor="none" seqnum="" totalcounta="2" xmi.id="MNq3TBM3lgVy" widgetbid="pY2KizGMCrHj" totalcountb="2" type="503" textcolor="none" usefillcolor="1" linewidth="none" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0">
<linepath layout="Polyline">
<startpoint startx="202" starty="-394"/>
<endpoint endx="202" endy="-249"/>
</linepath>
</assocwidget>
</associations>
</diagram>
</diagrams>
</XMI.extension>
DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
</UML:Model>
<UML:Model stereotype="folder" visibility="public" isSpecification="false" namespace="m1" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="Component View" name="Component View">
<UML:Namespace.ownedElement/>
</UML:Model>
<UML:Model stereotype="folder" visibility="public" isSpecification="false" namespace="m1" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="Deployment View" name="Deployment View">
<UML:Namespace.ownedElement/>
</UML:Model>
<UML:Model stereotype="folder" visibility="public" isSpecification="false" namespace="m1" isAbstract="false" isLeaf="false" isRoot="false" xmi.id="Entity Relationship Model" name="Entity Relationship Model">
<UML:Namespace.ownedElement/>
</UML:Model>
</UML:Namespace.ownedElement>
</UML:Model>
</XMI.content>
<XMI.extensions xmi.extender="umbrello">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<docsettings viewid="Q1qEMiNK0mHL" uniqueid="MQwJaZTuuIxN" documentation=""/>
DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
<listview>
<listitem open="1" type="800" id="Views">
<listitem open="1" type="821" id="Component View"/>
<listitem open="1" type="827" id="Deployment View"/>
<listitem open="1" type="836" id="Entity Relationship Model"/>
<listitem open="1" type="801" id="Logical View">
<listitem open="1" type="803" id="nCXlkkbOjNnt">
<listitem open="1" type="803" id="ZBWVrIDGeIPK"/>
</listitem>
<listitem open="0" type="830" id="Datatypes">
<listitem open="1" type="829" id="c4Twqn0aUQB4"/>
<listitem open="1" type="829" id="15L0hJXhwcFR"/>
<listitem open="1" type="829" id="hGddsq3TsUPg"/>
<listitem open="1" type="829" id="aPBblD5kGQlv"/>
<listitem open="1" type="829" id="mhSdaAG81L4V"/>
<listitem open="1" type="829" id="83IMS1F7HsjA"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<listitem open="1" type="829" id="pFknC1jVXUTk"/>
DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
<listitem open="1" type="829" id="HOEjoPmPovyX"/>
<listitem open="1" type="829" id="RoHoEUz0UZaO"/>
<listitem open="1" type="829" id="gkbWE0CWOQFD"/>
<listitem open="1" type="829" id="Qc5iSoq7YRdn"/>
<listitem open="1" type="829" id="n1aawY72aPM0"/>
</listitem>
<listitem open="1" type="803" id="dzlPCiVfMhDw">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<listitem open="1" type="803" id="AP2Jw6O9SyPl">
<listitem open="0" type="813" id="YVUu5DY24gSv"/>
<listitem open="0" type="813" id="zt9QqECndhuG"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<listitem open="0" type="813" id="AAXrURgiB2s9"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<listitem open="0" type="813" id="zQV7dGUdKiTL"/>
<listitem open="0" type="813" id="CIgVjFGNUjOp"/>
</listitem>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<listitem open="0" type="818" id="50pVMRCQE3mT">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<listitem open="0" type="813" id="QTe1L5jo295e"/>
<listitem open="0" type="813" id="04Gq3mqRDSTZ"/>
</listitem>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<listitem open="1" type="803" id="iJ1021VZA242">
DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
<listitem open="0" type="807" id="IIIwYfFi2Hzy" label="clip_display"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<listitem open="0" type="813" id="YML3K4y9h5tE"/>
<listitem open="0" type="813" id="TxRGe5zBPLEk"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<listitem open="0" type="807" id="tyAwJXVRd8yU" label="display_evaluation"/>
<listitem open="1" type="813" id="WIX6g3bhkPMX">
<listitem open="0" type="815" id="SjGuD1cFQas5"/>
<listitem open="0" type="814" id="MAWVsNUcUWni"/>
</listitem>
<listitem open="1" type="817" id="1l72I7ToPys3">
<listitem open="0" type="815" id="87ehnyLmiQo0"/>
</listitem>
<listitem open="1" type="817" id="wB7sY2nRjOXn">
<listitem open="0" type="815" id="m71ADYgKdI1Q"/>
</listitem>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<listitem open="0" type="813" id="8QIySCNjv8Nm"/>
<listitem open="0" type="813" id="IlnerbEbwJog"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<listitem open="0" type="813" id="r2bQMphsIClM"/>
DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
</listitem>
</listitem>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<listitem open="1" type="817" id="OkjgF2UByyJx"/>
<listitem open="1" type="817" id="vUTLjCtthGnz"/>
DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
<listitem open="1" type="803" id="ZJjfeyODnhwR">
<listitem open="1" type="803" id="wYrkFnB1ygmi"/>
<listitem open="1" type="803" id="FLcFLmuIIl0X"/>
<listitem open="1" type="803" id="RN68is2j9X47"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<listitem open="1" type="803" id="3HXNyiJX20Ae">
<listitem open="0" type="817" id="MAnxOpF9GaE3"/>
<listitem open="0" type="813" id="lSL6pzQhTDOj"/>
<listitem open="0" type="813" id="dfMQKri4XPmn"/>
<listitem open="1" type="813" id="SDesIUWO0dz1">
<listitem open="0" type="815" id="cv5AydHGTsoa"/>
<listitem open="0" type="815" id="KsbZ85POo9Lg"/>
<listitem open="0" type="815" id="zzlJ9A4Ksadb"/>
</listitem>
<listitem open="0" type="813" id="kihkGgfmWK0o">
<listitem open="0" type="815" id="RFgnI9xTKVIo"/>
<listitem open="0" type="814" id="wyW7zMFphhgG"/>
<listitem open="0" type="815" id="KsrSalZ00FnI"/>
</listitem>
<listitem open="0" type="817" id="vXeW5rShP4KV"/>
<listitem open="0" type="807" id="ZM3pbwOfd7Ql" label="session_subsystem"/>
<listitem open="0" type="817" id="GkMAyqUK0GFO"/>
<listitem open="0" type="813" id="rUnjINDv0ZKK"/>
<listitem open="0" type="813" id="k29coo6WqCqy"/>
<listitem open="0" type="813" id="YsfFJxnCRFW9"/>
<listitem open="1" type="817" id="i28J9X534hZ9">
<listitem open="0" type="815" id="6Y9d0aMtHa01"/>
<listitem open="0" type="815" id="tgE8kCyZfoMP"/>
<listitem open="0" type="815" id="pVqpkd56Npnb"/>
<listitem open="0" type="815" id="kyZPlvm8LFta"/>
<listitem open="0" type="815" id="PSTlFEK4S4pe"/>
</listitem>
<listitem open="0" type="813" id="mPYman5InEvb"/>
</listitem>
DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
</listitem>
</listitem>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<listitem open="1" type="802" id="Use Case View">
<listitem open="1" type="804" id="f4aD2h2f9RdQ">
<listitem open="0" type="805" id="Q1qEMiNK0mHL" label="CommandUsage"/>
</listitem>
<listitem open="1" type="812" id="pY2KizGMCrHj"/>
<listitem open="1" type="812" id="fpYdG6ZODQgg"/>
<listitem open="1" type="811" id="YaYgpwDph1lD"/>
<listitem open="1" type="811" id="eFcxWJO7utJx"/>
<listitem open="1" type="812" id="99tISYqG4qam"/>
<listitem open="1" type="812" id="cNavFgpTXYjv"/>
<listitem open="1" type="812" id="GrjGOZp3PLgd"/>
<listitem open="1" type="811" id="zlqyX5J6PSBr"/>
<listitem open="1" type="811" id="bdUD2bZY97Fy"/>
</listitem>
DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
</listitem>
</listview>
<codegeneration>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<codegenerator language="C++">
<classifiercodedocument package="AP2Jw6O9SyPl" fileExt=".cpp" parent_class="zt9QqECndhuG" id="zt9QqECndhuG" fileName="Controller" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="includes" text="#include &quot;controller.h&quot;&amp;#010;">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<classfields/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</classifiercodedocument>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<classifiercodedocument package="AP2Jw6O9SyPl" fileExt=".cpp" parent_class="YVUu5DY24gSv" id="YVUu5DY24gSv" fileName="BusTerm" writeOutCode="true">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<textblocks>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<codeblockwithcomments tag="includes" text="#include &quot;busterm.h&quot;&amp;#010;">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<classfields/>
</classifiercodedocument>
<classifiercodedocument package="AP2Jw6O9SyPl" fileExt=".cpp" parent_class="zQV7dGUdKiTL" id="zQV7dGUdKiTL" fileName="Tangible" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="includes" text="#include &quot;tangible.h&quot;&amp;#010;">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</header>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</classifiercodedocument>
<classifiercodedocument package="AP2Jw6O9SyPl" fileExt=".cpp" parent_class="CIgVjFGNUjOp" id="CIgVjFGNUjOp" fileName="Widget" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="includes" text="#include &quot;widget.h&quot;&amp;#010;">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="AP2Jw6O9SyPl" fileExt=".cpp" parent_class="AAXrURgiB2s9" id="AAXrURgiB2s9" fileName="CoreService" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="includes" text="#include &quot;coreservice.h&quot;&amp;#010;">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
</classifiercodedocument>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<classifiercodedocument package="iJ1021VZA242" fileExt=".cpp" parent_class="r2bQMphsIClM" id="r2bQMphsIClM" fileName="TrackPresenter" writeOutCode="true">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<textblocks>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<codeblockwithcomments tag="includes" text="#include &quot;trackpresenter.h&quot;&amp;#010;">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
<textblocks>
<codeaccessormethod role_id="0" tag="hblock_tag_0" accessType="0" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text="return ;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="0" tag="hblock_tag_1" accessType="1" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text=" = value;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="0" tag="hblock_tag_2" accessType="2" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text="%VARNAME%.push_back(value);" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<codeaccessormethod role_id="0" tag="hblock_tag_3" accessType="3" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text="int size = %VARNAME%.size();&amp;#010;for (int i = 0; i &lt; size; ++i) {&amp;#010;&#x9;ClipPresenter item = %VARNAME%.at(i);&amp;#010;&#x9;if(item == value) {&amp;#010;&#x9;&#x9;vector&lt;ClipPresenter>::iterator it = %VARNAME%.begin() + i;&amp;#010;&#x9;&#x9;%VARNAME%.erase(it);&amp;#010;&#x9;&#x9;return;&amp;#010;&#x9;}&amp;#010; }" canDelete="false">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="0" tag="hblock_tag_4" accessType="4" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text="return ;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
</textblocks>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeclassfield role_id="0" listClassName="" field_type="4" parent_id="TdTehsF1A2Mv" writeOutMethods="true" initialValue="">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<ccfdeclarationcodeblock role_id="0" tag="" parent_id="TdTehsF1A2Mv" writeOutText="false" indentLevel="1" text="public TrackPresenter ;" canDelete="false">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false" indentLevel="1"/>
</header>
</ccfdeclarationcodeblock>
<codeaccessormethod role_id="0" tag="hblock_tag_0" accessType="0" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text="return ;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="0" tag="hblock_tag_1" accessType="1" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text=" = value;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="0" tag="hblock_tag_2" accessType="2" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text="%VARNAME%.push_back(value);" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<codeaccessormethod role_id="0" tag="hblock_tag_3" accessType="3" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text="int size = %VARNAME%.size();&amp;#010;for (int i = 0; i &lt; size; ++i) {&amp;#010;&#x9;ClipPresenter item = %VARNAME%.at(i);&amp;#010;&#x9;if(item == value) {&amp;#010;&#x9;&#x9;vector&lt;ClipPresenter>::iterator it = %VARNAME%.begin() + i;&amp;#010;&#x9;&#x9;%VARNAME%.erase(it);&amp;#010;&#x9;&#x9;return;&amp;#010;&#x9;}&amp;#010; }" canDelete="false">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="0" tag="hblock_tag_4" accessType="4" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text="return ;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
</codeclassfield>
</classfields>
</classifiercodedocument>
<classifiercodedocument package="iJ1021VZA242" fileExt=".cpp" parent_class="TxRGe5zBPLEk" id="TxRGe5zBPLEk" fileName="ClipWidget" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="includes" text="#include &quot;clipwidget.h&quot;&amp;#010;">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<textblocks>
<codeaccessormethod role_id="1" tag="hblock_tag_0" accessType="0" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text="return ;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="1" tag="hblock_tag_1" accessType="1" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text=" = value;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="1" tag="hblock_tag_2" accessType="2" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text="%VARNAME%.push_back(value);" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="1" tag="hblock_tag_3" accessType="3" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text="int size = %VARNAME%.size();&amp;#010;for (int i = 0; i &lt; size; ++i) {&amp;#010;&#x9;TrackBodyWidget item = %VARNAME%.at(i);&amp;#010;&#x9;if(item == value) {&amp;#010;&#x9;&#x9;vector&lt;TrackBodyWidget>::iterator it = %VARNAME%.begin() + i;&amp;#010;&#x9;&#x9;%VARNAME%.erase(it);&amp;#010;&#x9;&#x9;return;&amp;#010;&#x9;}&amp;#010; }" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="1" tag="hblock_tag_4" accessType="4" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text="return ;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
</textblocks>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<classfields>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeclassfield role_id="0" listClassName="" field_type="3" parent_id="ofNcGNdOluKC" writeOutMethods="true" initialValue="">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<ccfdeclarationcodeblock role_id="1" tag="" parent_id="ofNcGNdOluKC" writeOutText="false" indentLevel="1" text="public TrackBodyWidget ;" canDelete="false">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false" indentLevel="1"/>
</header>
</ccfdeclarationcodeblock>
<codeaccessormethod role_id="1" tag="hblock_tag_0" accessType="0" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text="return ;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="1" tag="hblock_tag_1" accessType="1" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text=" = value;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="1" tag="hblock_tag_2" accessType="2" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text="%VARNAME%.push_back(value);" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="1" tag="hblock_tag_3" accessType="3" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text="int size = %VARNAME%.size();&amp;#010;for (int i = 0; i &lt; size; ++i) {&amp;#010;&#x9;TrackBodyWidget item = %VARNAME%.at(i);&amp;#010;&#x9;if(item == value) {&amp;#010;&#x9;&#x9;vector&lt;TrackBodyWidget>::iterator it = %VARNAME%.begin() + i;&amp;#010;&#x9;&#x9;%VARNAME%.erase(it);&amp;#010;&#x9;&#x9;return;&amp;#010;&#x9;}&amp;#010; }" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="1" tag="hblock_tag_4" accessType="4" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text="return ;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
</codeclassfield>
</classfields>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</classifiercodedocument>
<classifiercodedocument package="iJ1021VZA242" fileExt=".cpp" parent_class="YML3K4y9h5tE" id="YML3K4y9h5tE" fileName="ClipPresenter" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="includes" text="#include &quot;clippresenter.h&quot;&amp;#010;">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
<textblocks>
<codeaccessormethod role_id="1" tag="hblock_tag_0" accessType="0" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text="return ;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="1" tag="hblock_tag_1" accessType="1" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text=" = value;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="1" tag="hblock_tag_2" accessType="2" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text="%VARNAME%.push_back(value);" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<codeaccessormethod role_id="1" tag="hblock_tag_3" accessType="3" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text="int size = %VARNAME%.size();&amp;#010;for (int i = 0; i &lt; size; ++i) {&amp;#010;&#x9;TrackPresenter item = %VARNAME%.at(i);&amp;#010;&#x9;if(item == value) {&amp;#010;&#x9;&#x9;vector&lt;TrackPresenter>::iterator it = %VARNAME%.begin() + i;&amp;#010;&#x9;&#x9;%VARNAME%.erase(it);&amp;#010;&#x9;&#x9;return;&amp;#010;&#x9;}&amp;#010; }" canDelete="false">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="1" tag="hblock_tag_4" accessType="4" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text="return ;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
</textblocks>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeclassfield role_id="1" listClassName="" field_type="4" parent_id="TdTehsF1A2Mv" writeOutMethods="true" initialValue="">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<ccfdeclarationcodeblock role_id="1" tag="" parent_id="TdTehsF1A2Mv" writeOutText="false" indentLevel="1" text="public ClipPresenter ;" canDelete="false">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false" indentLevel="1"/>
</header>
</ccfdeclarationcodeblock>
<codeaccessormethod role_id="1" tag="hblock_tag_0" accessType="0" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text="return ;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="1" tag="hblock_tag_1" accessType="1" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text=" = value;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="1" tag="hblock_tag_2" accessType="2" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text="%VARNAME%.push_back(value);" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<codeaccessormethod role_id="1" tag="hblock_tag_3" accessType="3" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text="int size = %VARNAME%.size();&amp;#010;for (int i = 0; i &lt; size; ++i) {&amp;#010;&#x9;TrackPresenter item = %VARNAME%.at(i);&amp;#010;&#x9;if(item == value) {&amp;#010;&#x9;&#x9;vector&lt;TrackPresenter>::iterator it = %VARNAME%.begin() + i;&amp;#010;&#x9;&#x9;%VARNAME%.erase(it);&amp;#010;&#x9;&#x9;return;&amp;#010;&#x9;}&amp;#010; }" canDelete="false">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="1" tag="hblock_tag_4" accessType="4" parent_id="TdTehsF1A2Mv" writeOutText="false" classfield_id="TdTehsF1A2Mv" text="return ;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
</codeclassfield>
</classfields>
</classifiercodedocument>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<classifiercodedocument package="iJ1021VZA242" fileExt=".cpp" parent_class="8QIySCNjv8Nm" id="8QIySCNjv8Nm" fileName="TrackBodyWidget" writeOutCode="true">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<textblocks>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<codeblockwithcomments tag="includes" text="#include &quot;trackbodywidget.h&quot;&amp;#010;">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<textblocks>
<codeaccessormethod role_id="0" tag="hblock_tag_0" accessType="0" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text="return ;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="0" tag="hblock_tag_1" accessType="1" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text=" = value;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="0" tag="hblock_tag_2" accessType="2" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text="%VARNAME%.push_back(value);" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="0" tag="hblock_tag_3" accessType="3" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text="int size = %VARNAME%.size();&amp;#010;for (int i = 0; i &lt; size; ++i) {&amp;#010;&#x9;ClipWidget item = %VARNAME%.at(i);&amp;#010;&#x9;if(item == value) {&amp;#010;&#x9;&#x9;vector&lt;ClipWidget>::iterator it = %VARNAME%.begin() + i;&amp;#010;&#x9;&#x9;%VARNAME%.erase(it);&amp;#010;&#x9;&#x9;return;&amp;#010;&#x9;}&amp;#010; }" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="0" tag="hblock_tag_4" accessType="4" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text="return ;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
</textblocks>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<classfields>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeclassfield role_id="1" listClassName="" field_type="3" parent_id="ofNcGNdOluKC" writeOutMethods="true" initialValue="">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<ccfdeclarationcodeblock role_id="0" tag="" parent_id="ofNcGNdOluKC" writeOutText="false" indentLevel="1" text="public ClipWidget ;" canDelete="false">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false" indentLevel="1"/>
</header>
</ccfdeclarationcodeblock>
<codeaccessormethod role_id="0" tag="hblock_tag_0" accessType="0" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text="return ;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="0" tag="hblock_tag_1" accessType="1" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text=" = value;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="0" tag="hblock_tag_2" accessType="2" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text="%VARNAME%.push_back(value);" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="0" tag="hblock_tag_3" accessType="3" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text="int size = %VARNAME%.size();&amp;#010;for (int i = 0; i &lt; size; ++i) {&amp;#010;&#x9;ClipWidget item = %VARNAME%.at(i);&amp;#010;&#x9;if(item == value) {&amp;#010;&#x9;&#x9;vector&lt;ClipWidget>::iterator it = %VARNAME%.begin() + i;&amp;#010;&#x9;&#x9;%VARNAME%.erase(it);&amp;#010;&#x9;&#x9;return;&amp;#010;&#x9;}&amp;#010; }" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod role_id="0" tag="hblock_tag_4" accessType="4" parent_id="ofNcGNdOluKC" writeOutText="false" classfield_id="ofNcGNdOluKC" text="return ;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
</codeclassfield>
</classfields>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</classifiercodedocument>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<classifiercodedocument package="iJ1021VZA242" fileExt=".cpp" parent_class="IlnerbEbwJog" id="IlnerbEbwJog" fileName="TrackHeadWidget" writeOutCode="true">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<textblocks>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<codeblockwithcomments tag="includes" text="#include &quot;trackheadwidget.h&quot;&amp;#010;">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
</classifiercodedocument>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<classifiercodedocument package="iJ1021VZA242" fileExt=".cpp" parent_class="wB7sY2nRjOXn" id="wB7sY2nRjOXn" fileName="Element" writeOutCode="true">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<textblocks>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<codeblockwithcomments tag="includes" text="#include &quot;element.h&quot;&amp;#010;">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</header>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<cppcodedocumentation tag="" text="Methods"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</header>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<textblocks>
<codeoperation tag="operation_m71ADYgKdI1Q" parent_id="m71ADYgKdI1Q" writeOutText="false" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeoperation>
</textblocks>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<classfields/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</classifiercodedocument>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<classifiercodedocument package="iJ1021VZA242" fileExt=".cpp" parent_class="WIX6g3bhkPMX" id="WIX6g3bhkPMX" fileName="DisplayEvaluation" writeOutCode="true">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<textblocks>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<codeblockwithcomments tag="includes" text="#include &quot;displayevaluation.h&quot;&amp;#010;">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
<textblocks>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<codeaccessormethod tag="hblock_tag_0" accessType="0" parent_id="MAWVsNUcUWni" writeOutText="false" classfield_id="MAWVsNUcUWni" text="return manager;" canDelete="false">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<codeaccessormethod tag="hblock_tag_1" accessType="1" parent_id="MAWVsNUcUWni" writeOutText="false" classfield_id="MAWVsNUcUWni" text="manager = value;" canDelete="false">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<codeoperation tag="operation_SjGuD1cFQas5" parent_id="SjGuD1cFQas5" writeOutText="false" canDelete="false">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</codeoperation>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</textblocks>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<codeclassfield role_id="-1" listClassName="" field_type="0" parent_id="MAWVsNUcUWni" writeOutMethods="true" initialValue="">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<ccfdeclarationcodeblock tag="" parent_id="MAWVsNUcUWni" indentLevel="1" text="private GUI::Timeline::DisplayManager manager;" canDelete="false">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<cppcodedocumentation tag="" indentLevel="1"/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</header>
</ccfdeclarationcodeblock>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<codeaccessormethod tag="hblock_tag_0" accessType="0" parent_id="MAWVsNUcUWni" writeOutText="false" classfield_id="MAWVsNUcUWni" text="return manager;" canDelete="false">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<codeaccessormethod tag="hblock_tag_1" accessType="1" parent_id="MAWVsNUcUWni" writeOutText="false" classfield_id="MAWVsNUcUWni" text="manager = value;" canDelete="false">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
</codeclassfield>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</classfields>
</classifiercodedocument>
<classifiercodedocument package="iJ1021VZA242" fileExt=".cpp" parent_class="1l72I7ToPys3" id="1l72I7ToPys3" fileName="DisplayManager" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="includes" text="#include &quot;displaymanager.h&quot;&amp;#010;">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</header>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
<textblocks>
<codeoperation tag="operation_87ehnyLmiQo0" parent_id="87ehnyLmiQo0" writeOutText="false" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeoperation>
</textblocks>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
</classifiercodedocument>
<classifiercodedocument package="50pVMRCQE3mT" fileExt=".cpp" parent_class="04Gq3mqRDSTZ" id="04Gq3mqRDSTZ" fileName="Gtk_Layout" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="includes" text="#include &quot;gtk_layout.h&quot;&amp;#010;">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
</classifiercodedocument>
<classifiercodedocument package="50pVMRCQE3mT" fileExt=".cpp" parent_class="QTe1L5jo295e" id="QTe1L5jo295e" fileName="Gtk_Frame" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="includes" text="#include &quot;gtk_frame.h&quot;&amp;#010;">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</classifiercodedocument>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".cpp" parent_class="vXeW5rShP4KV" id="vXeW5rShP4KV" fileName="Session" writeOutCode="true">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<textblocks>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<codeblockwithcomments tag="includes" text="#include &quot;session.h&quot;&amp;#010;">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</header>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</hierarchicalcodeblock>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<cppcodedocumentation tag="" text="Methods"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</header>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks/>
</hierarchicalcodeblock>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</textblocks>
<header>
<codecomment tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classfields/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</classifiercodedocument>
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".cpp" parent_class="i28J9X534hZ9" id="i28J9X534hZ9" fileName="SessManager" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="includes" text="#include &quot;sessmanager.h&quot;&amp;#010;">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</header>
<textblocks>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<codeoperation tag="operation_pVqpkd56Npnb" parent_id="pVqpkd56Npnb" writeOutText="false" canDelete="false">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<cppcodedocumentation tag=""/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</header>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</codeoperation>
<codeoperation tag="operation_tgE8kCyZfoMP" parent_id="tgE8kCyZfoMP" writeOutText="false" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeoperation>
<codeoperation tag="operation_PSTlFEK4S4pe" parent_id="PSTlFEK4S4pe" writeOutText="false" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeoperation>
<codeoperation tag="operation_6Y9d0aMtHa01" parent_id="6Y9d0aMtHa01" writeOutText="false" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeoperation>
<codeoperation tag="operation_kyZPlvm8LFta" parent_id="kyZPlvm8LFta" writeOutText="false" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeoperation>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</textblocks>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classfields/>
</classifiercodedocument>
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".cpp" parent_class="SDesIUWO0dz1" id="SDesIUWO0dz1" fileName="LifecycleAdvisor" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="includes" text="#include &quot;lifecycleadvisor.h&quot;&amp;#010;">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
<textblocks>
<codeoperation tag="operation_KsbZ85POo9Lg" parent_id="KsbZ85POo9Lg" writeOutText="false" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeoperation>
<codeoperation tag="operation_zzlJ9A4Ksadb" parent_id="zzlJ9A4Ksadb" writeOutText="false" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeoperation>
<codeoperation tag="operation_cv5AydHGTsoa" parent_id="cv5AydHGTsoa" writeOutText="false" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeoperation>
</textblocks>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".cpp" parent_class="lSL6pzQhTDOj" id="lSL6pzQhTDOj" fileName="CommandQueue" writeOutCode="true">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &quot;commandqueue.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classfields/>
</classifiercodedocument>
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".cpp" parent_class="kihkGgfmWK0o" id="kihkGgfmWK0o" fileName="ProcDispatcher" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="includes" text="#include &quot;procdispatcher.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
<textblocks>
<codeoperation tag="operation_RFgnI9xTKVIo" parent_id="RFgnI9xTKVIo" writeOutText="false" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeoperation>
<codeaccessormethod tag="hblock_tag_0" accessType="0" parent_id="wyW7zMFphhgG" writeOutText="false" classfield_id="wyW7zMFphhgG" text="return deactivate;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeaccessormethod tag="hblock_tag_1" accessType="1" parent_id="wyW7zMFphhgG" writeOutText="false" classfield_id="wyW7zMFphhgG" text="deactivate = value;" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
<codeoperation tag="operation_KsrSalZ00FnI" parent_id="KsrSalZ00FnI" writeOutText="false" canDelete="false">
<header>
<cppcodedocumentation tag=""/>
</header>
</codeoperation>
</textblocks>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields>
<codeclassfield role_id="-1" listClassName="" field_type="0" parent_id="wyW7zMFphhgG" writeOutMethods="true" initialValue="">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<ccfdeclarationcodeblock tag="" parent_id="wyW7zMFphhgG" indentLevel="1" text="private deactivate;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" indentLevel="1"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
</ccfdeclarationcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod tag="hblock_tag_0" accessType="0" parent_id="wyW7zMFphhgG" writeOutText="false" classfield_id="wyW7zMFphhgG" text="return deactivate;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod tag="hblock_tag_1" accessType="1" parent_id="wyW7zMFphhgG" writeOutText="false" classfield_id="wyW7zMFphhgG" text="deactivate = value;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
</codeaccessormethod>
</codeclassfield>
</classfields>
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".cpp" parent_class="GkMAyqUK0GFO" id="GkMAyqUK0GFO" fileName="SessionCommand" writeOutCode="true">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &quot;sessioncommand.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classfields/>
</classifiercodedocument>
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".cpp" parent_class="rUnjINDv0ZKK" id="rUnjINDv0ZKK" fileName="SessionCommandService" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="includes" text="#include &quot;sessioncommandservice.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" text="Methods"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<textblocks/>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".cpp" parent_class="k29coo6WqCqy" id="k29coo6WqCqy" fileName="SessionImpl" writeOutCode="true">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &quot;sessionimpl.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classfields/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</classifiercodedocument>
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".cpp" parent_class="YsfFJxnCRFW9" id="YsfFJxnCRFW9" fileName="SessionSubsystem" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="includes" text="#include &quot;sessionsubsystem.h&quot;&amp;#010;">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classfields/>
</classifiercodedocument>
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".cpp" parent_class="mPYman5InEvb" id="mPYman5InEvb" fileName="SessManagerImpl" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="includes" text="#include &quot;sessmanagerimpl.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" text="Methods"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<textblocks/>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
</classifiercodedocument>
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".cpp" parent_class="dfMQKri4XPmn" id="dfMQKri4XPmn" fileName="DispatcherLoop" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="includes" text="#include &quot;dispatcherloop.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<textblocks/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" text="Methods"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<textblocks/>
</hierarchicalcodeblock>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</textblocks>
<header>
<codecomment tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classfields/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".cpp" parent_class="MAnxOpF9GaE3" id="MAnxOpF9GaE3" fileName="CommandDispatch" writeOutCode="true">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &quot;commanddispatch.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<textblocks/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" text="Methods"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<textblocks/>
</hierarchicalcodeblock>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</textblocks>
<header>
<codecomment tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classfields/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="Logical View" fileExt=".cpp" parent_class="vUTLjCtthGnz" id="vUTLjCtthGnz" fileName="Subsys" writeOutCode="true">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &quot;subsys.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<textblocks/>
</hierarchicalcodeblock>
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Methods"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
</classifiercodedocument>
<classifiercodedocument package="Logical View" fileExt=".cpp" parent_class="OkjgF2UByyJx" id="OkjgF2UByyJx" fileName="ThreadJoinable" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="includes" text="#include &quot;threadjoinable.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<hierarchicalcodeblock tag="constructionMethodsBlock" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" text="Constructors/Destructors"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<textblocks/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<hierarchicalcodeblock tag="otherMethodsBlock" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" text="Methods"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<textblocks/>
</hierarchicalcodeblock>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="AP2Jw6O9SyPl" fileExt=".h" parent_class="zt9QqECndhuG" id="cppheaderzt9QqECndhuG" fileName="Controller" writeOutCode="true">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef CONTROLLER_H&amp;#010;#define CONTROLLER_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;#include &quot;tangible.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<textblocks>
<codeblockwithcomments tag="enums" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //CONTROLLER_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="AP2Jw6O9SyPl" fileExt=".h" parent_class="YVUu5DY24gSv" id="cppheaderYVUu5DY24gSv" fileName="BusTerm" writeOutCode="true">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef BUSTERM_H&amp;#010;#define BUSTERM_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks>
<codeblockwithcomments tag="enums" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //BUSTERM_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="AP2Jw6O9SyPl" fileExt=".h" parent_class="zQV7dGUdKiTL" id="cppheaderzQV7dGUdKiTL" fileName="Tangible" writeOutCode="true">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef TANGIBLE_H&amp;#010;#define TANGIBLE_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;#include &quot;busterm.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<textblocks>
<codeblockwithcomments tag="enums" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //TANGIBLE_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="AP2Jw6O9SyPl" fileExt=".h" parent_class="CIgVjFGNUjOp" id="cppheaderCIgVjFGNUjOp" fileName="Widget" writeOutCode="true">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef WIDGET_H&amp;#010;#define WIDGET_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;#include &quot;tangible.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks>
<codeblockwithcomments tag="enums" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //WIDGET_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="AP2Jw6O9SyPl" fileExt=".h" parent_class="AAXrURgiB2s9" id="cppheaderAAXrURgiB2s9" fileName="CoreService" writeOutCode="true">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef CORESERVICE_H&amp;#010;#define CORESERVICE_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;#include &quot;sessioncommand.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks>
<codeblockwithcomments tag="enums" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //CORESERVICE_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="iJ1021VZA242" fileExt=".h" parent_class="r2bQMphsIClM" id="cppheaderr2bQMphsIClM" fileName="TrackPresenter" writeOutCode="true">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef TRACKPRESENTER_H&amp;#010;#define TRACKPRESENTER_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;#include &quot;clippresenter.h&quot;&amp;#010;#include &quot;controller.h&quot;&amp;#010;#include &quot;trackheadwidget.h&quot;&amp;#010;#include &quot;trackbodywidget.h&quot;&amp;#010;#include &quot;element.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="using" text="using GUI_Timeline::TrackPresenter;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="enums" writeOutText="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</textblocks>
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //TRACKPRESENTER_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeclassfield role_id="0" listClassName="" field_type="4" parent_id="TdTehsF1A2Mv" writeOutMethods="true" initialValue="">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<ccfdeclarationcodeblock role_id="0" tag="tblock_0" parent_id="TdTehsF1A2Mv" writeOutText="false" indentLevel="1" text=" TrackPresenter ;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false" indentLevel="1"/>
</header>
</ccfdeclarationcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="0" tag="hblock_tag_0" accessType="0" parent_id="TdTehsF1A2Mv" writeOutText="false" indentLevel="1" classfield_id="TdTehsF1A2Mv" text="return ;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="0" tag="hblock_tag_1" accessType="1" parent_id="TdTehsF1A2Mv" writeOutText="false" indentLevel="1" classfield_id="TdTehsF1A2Mv" text=" = value;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="0" tag="hblock_tag_2" accessType="2" parent_id="TdTehsF1A2Mv" writeOutText="false" indentLevel="1" classfield_id="TdTehsF1A2Mv" text="%VARNAME%.push_back(value);" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="0" tag="hblock_tag_3" accessType="3" parent_id="TdTehsF1A2Mv" writeOutText="false" indentLevel="1" classfield_id="TdTehsF1A2Mv" text="int size = %VARNAME%.size();&amp;#010;for (int i = 0; i &lt; size; ++i) {&amp;#010;&#x9;ClipPresenter item = %VARNAME%.at(i);&amp;#010;&#x9;if(item == value) {&amp;#010;&#x9;&#x9;vector&lt;ClipPresenter>::iterator it = %VARNAME%.begin() + i;&amp;#010;&#x9;&#x9;%VARNAME%.erase(it);&amp;#010;&#x9;&#x9;return;&amp;#010;&#x9;}&amp;#010; }" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="0" tag="hblock_tag_4" accessType="4" parent_id="TdTehsF1A2Mv" writeOutText="false" indentLevel="1" classfield_id="TdTehsF1A2Mv" text="return ;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
</codeclassfield>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</classfields>
</classifiercodedocument>
<classifiercodedocument package="iJ1021VZA242" fileExt=".h" parent_class="TxRGe5zBPLEk" id="cppheaderTxRGe5zBPLEk" fileName="ClipWidget" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="hashDefBlock" text="#ifndef CLIPWIDGET_H&amp;#010;#define CLIPWIDGET_H">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;#include &quot;gtk_frame.h&quot;&amp;#010;#include &quot;gtk_layout.h&quot;&amp;#010;">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="using" text="using GUI_Timeline::ClipWidget;&amp;#010;">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks>
<codeblockwithcomments tag="enums" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
</hierarchicalcodeblock>
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //CLIPWIDGET_H">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields>
<codeclassfield role_id="0" listClassName="" field_type="3" parent_id="ofNcGNdOluKC" writeOutMethods="true" initialValue="">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<ccfdeclarationcodeblock role_id="1" tag="tblock_0" parent_id="ofNcGNdOluKC" writeOutText="false" indentLevel="1" text=" TrackBodyWidget ;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false" indentLevel="1"/>
</header>
</ccfdeclarationcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="1" tag="hblock_tag_0" accessType="0" parent_id="ofNcGNdOluKC" writeOutText="false" indentLevel="1" classfield_id="ofNcGNdOluKC" text="return ;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="1" tag="hblock_tag_1" accessType="1" parent_id="ofNcGNdOluKC" writeOutText="false" indentLevel="1" classfield_id="ofNcGNdOluKC" text=" = value;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="1" tag="hblock_tag_2" accessType="2" parent_id="ofNcGNdOluKC" writeOutText="false" indentLevel="1" classfield_id="ofNcGNdOluKC" text="%VARNAME%.push_back(value);" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="1" tag="hblock_tag_3" accessType="3" parent_id="ofNcGNdOluKC" writeOutText="false" indentLevel="1" classfield_id="ofNcGNdOluKC" text="int size = %VARNAME%.size();&amp;#010;for (int i = 0; i &lt; size; ++i) {&amp;#010;&#x9;TrackBodyWidget item = %VARNAME%.at(i);&amp;#010;&#x9;if(item == value) {&amp;#010;&#x9;&#x9;vector&lt;TrackBodyWidget>::iterator it = %VARNAME%.begin() + i;&amp;#010;&#x9;&#x9;%VARNAME%.erase(it);&amp;#010;&#x9;&#x9;return;&amp;#010;&#x9;}&amp;#010; }" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="1" tag="hblock_tag_4" accessType="4" parent_id="ofNcGNdOluKC" writeOutText="false" indentLevel="1" classfield_id="ofNcGNdOluKC" text="return ;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
</codeclassfield>
</classfields>
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="iJ1021VZA242" fileExt=".h" parent_class="YML3K4y9h5tE" id="cppheaderYML3K4y9h5tE" fileName="ClipPresenter" writeOutCode="true">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef CLIPPRESENTER_H&amp;#010;#define CLIPPRESENTER_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;#include &quot;controller.h&quot;&amp;#010;#include &quot;clipwidget.h&quot;&amp;#010;#include &quot;element.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="using" text="using GUI_Timeline::ClipPresenter;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="enums" writeOutText="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</textblocks>
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //CLIPPRESENTER_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeclassfield role_id="1" listClassName="" field_type="4" parent_id="TdTehsF1A2Mv" writeOutMethods="true" initialValue="">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<ccfdeclarationcodeblock role_id="1" tag="tblock_0" parent_id="TdTehsF1A2Mv" writeOutText="false" indentLevel="1" text=" ClipPresenter ;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false" indentLevel="1"/>
</header>
</ccfdeclarationcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="1" tag="hblock_tag_0" accessType="0" parent_id="TdTehsF1A2Mv" writeOutText="false" indentLevel="1" classfield_id="TdTehsF1A2Mv" text="return ;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="1" tag="hblock_tag_1" accessType="1" parent_id="TdTehsF1A2Mv" writeOutText="false" indentLevel="1" classfield_id="TdTehsF1A2Mv" text=" = value;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="1" tag="hblock_tag_2" accessType="2" parent_id="TdTehsF1A2Mv" writeOutText="false" indentLevel="1" classfield_id="TdTehsF1A2Mv" text="%VARNAME%.push_back(value);" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="1" tag="hblock_tag_3" accessType="3" parent_id="TdTehsF1A2Mv" writeOutText="false" indentLevel="1" classfield_id="TdTehsF1A2Mv" text="int size = %VARNAME%.size();&amp;#010;for (int i = 0; i &lt; size; ++i) {&amp;#010;&#x9;TrackPresenter item = %VARNAME%.at(i);&amp;#010;&#x9;if(item == value) {&amp;#010;&#x9;&#x9;vector&lt;TrackPresenter>::iterator it = %VARNAME%.begin() + i;&amp;#010;&#x9;&#x9;%VARNAME%.erase(it);&amp;#010;&#x9;&#x9;return;&amp;#010;&#x9;}&amp;#010; }" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="1" tag="hblock_tag_4" accessType="4" parent_id="TdTehsF1A2Mv" writeOutText="false" indentLevel="1" classfield_id="TdTehsF1A2Mv" text="return ;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
</codeclassfield>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</classfields>
</classifiercodedocument>
<classifiercodedocument package="iJ1021VZA242" fileExt=".h" parent_class="8QIySCNjv8Nm" id="cppheader8QIySCNjv8Nm" fileName="TrackBodyWidget" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="hashDefBlock" text="#ifndef TRACKBODYWIDGET_H&amp;#010;#define TRACKBODYWIDGET_H">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;#include &quot;clipwidget.h&quot;&amp;#010;">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks>
<codeblockwithcomments tag="enums" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
</hierarchicalcodeblock>
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //TRACKBODYWIDGET_H">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields>
<codeclassfield role_id="1" listClassName="" field_type="3" parent_id="ofNcGNdOluKC" writeOutMethods="true" initialValue="">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<ccfdeclarationcodeblock role_id="0" tag="tblock_0" parent_id="ofNcGNdOluKC" writeOutText="false" indentLevel="1" text=" ClipWidget ;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false" indentLevel="1"/>
</header>
</ccfdeclarationcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="0" tag="hblock_tag_0" accessType="0" parent_id="ofNcGNdOluKC" writeOutText="false" indentLevel="1" classfield_id="ofNcGNdOluKC" text="return ;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="0" tag="hblock_tag_1" accessType="1" parent_id="ofNcGNdOluKC" writeOutText="false" indentLevel="1" classfield_id="ofNcGNdOluKC" text=" = value;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="0" tag="hblock_tag_2" accessType="2" parent_id="ofNcGNdOluKC" writeOutText="false" indentLevel="1" classfield_id="ofNcGNdOluKC" text="%VARNAME%.push_back(value);" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="0" tag="hblock_tag_3" accessType="3" parent_id="ofNcGNdOluKC" writeOutText="false" indentLevel="1" classfield_id="ofNcGNdOluKC" text="int size = %VARNAME%.size();&amp;#010;for (int i = 0; i &lt; size; ++i) {&amp;#010;&#x9;ClipWidget item = %VARNAME%.at(i);&amp;#010;&#x9;if(item == value) {&amp;#010;&#x9;&#x9;vector&lt;ClipWidget>::iterator it = %VARNAME%.begin() + i;&amp;#010;&#x9;&#x9;%VARNAME%.erase(it);&amp;#010;&#x9;&#x9;return;&amp;#010;&#x9;}&amp;#010; }" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod role_id="0" tag="hblock_tag_4" accessType="4" parent_id="ofNcGNdOluKC" writeOutText="false" indentLevel="1" classfield_id="ofNcGNdOluKC" text="return ;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
</codeclassfield>
</classfields>
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="iJ1021VZA242" fileExt=".h" parent_class="IlnerbEbwJog" id="cppheaderIlnerbEbwJog" fileName="TrackHeadWidget" writeOutCode="true">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef TRACKHEADWIDGET_H&amp;#010;#define TRACKHEADWIDGET_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks>
<codeblockwithcomments tag="enums" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //TRACKHEADWIDGET_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classfields/>
</classifiercodedocument>
<classifiercodedocument package="iJ1021VZA242" fileExt=".h" parent_class="wB7sY2nRjOXn" id="cppheaderwB7sY2nRjOXn" fileName="Element" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="hashDefBlock" text="#ifndef ELEMENT_H&amp;#010;#define ELEMENT_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;#include &quot;displayevaluation.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //ELEMENT_H">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="iJ1021VZA242" fileExt=".h" parent_class="WIX6g3bhkPMX" id="cppheaderWIX6g3bhkPMX" fileName="DisplayEvaluation" writeOutCode="true">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef DISPLAYEVALUATION_H&amp;#010;#define DISPLAYEVALUATION_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;#include &quot;element.h&quot;&amp;#010;#include &quot;displaymanager.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks>
<codeblockwithcomments tag="enums" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //DISPLAYEVALUATION_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeclassfield role_id="-1" listClassName="" field_type="0" parent_id="MAWVsNUcUWni" writeOutMethods="true" initialValue="">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<ccfdeclarationcodeblock tag="tblock_0" parent_id="MAWVsNUcUWni" indentLevel="1" text=" GUI::Timeline::DisplayManager manager;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false" indentLevel="1"/>
</header>
</ccfdeclarationcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod tag="hblock_tag_0" accessType="0" parent_id="MAWVsNUcUWni" indentLevel="1" classfield_id="MAWVsNUcUWni" text="return manager;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod tag="hblock_tag_1" accessType="1" parent_id="MAWVsNUcUWni" indentLevel="1" classfield_id="MAWVsNUcUWni" text="manager = value;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
</codeclassfield>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</classfields>
</classifiercodedocument>
<classifiercodedocument package="iJ1021VZA242" fileExt=".h" parent_class="1l72I7ToPys3" id="cppheader1l72I7ToPys3" fileName="DisplayManager" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="hashDefBlock" text="#ifndef DISPLAYMANAGER_H&amp;#010;#define DISPLAYMANAGER_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;#include &quot;element.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //DISPLAYMANAGER_H">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="50pVMRCQE3mT" fileExt=".h" parent_class="04Gq3mqRDSTZ" id="cppheader04Gq3mqRDSTZ" fileName="Gtk_Layout" writeOutCode="true">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef GTK_LAYOUT_H&amp;#010;#define GTK_LAYOUT_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="enums" writeOutText="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</textblocks>
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //GTK_LAYOUT_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classfields/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="50pVMRCQE3mT" fileExt=".h" parent_class="QTe1L5jo295e" id="cppheaderQTe1L5jo295e" fileName="Gtk_Frame" writeOutCode="true">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef GTK_FRAME_H&amp;#010;#define GTK_FRAME_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks>
<codeblockwithcomments tag="enums" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //GTK_FRAME_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classfields/>
</classifiercodedocument>
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".h" parent_class="vXeW5rShP4KV" id="cppheadervXeW5rShP4KV" fileName="Session" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="hashDefBlock" text="#ifndef SESSION_H&amp;#010;#define SESSION_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //SESSION_H">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".h" parent_class="i28J9X534hZ9" id="cppheaderi28J9X534hZ9" fileName="SessManager" writeOutCode="true">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef SESSMANAGER_H&amp;#010;#define SESSMANAGER_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;#include &quot;session.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<textblocks/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //SESSMANAGER_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classfields/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".h" parent_class="SDesIUWO0dz1" id="cppheaderSDesIUWO0dz1" fileName="LifecycleAdvisor" writeOutCode="true">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef LIFECYCLEADVISOR_H&amp;#010;#define LIFECYCLEADVISOR_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;#include &quot;procdispatcher.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks>
<codeblockwithcomments tag="enums" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //LIFECYCLEADVISOR_H">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classfields/>
</classifiercodedocument>
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".h" parent_class="lSL6pzQhTDOj" id="cppheaderlSL6pzQhTDOj" fileName="CommandQueue" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="hashDefBlock" text="#ifndef COMMANDQUEUE_H&amp;#010;#define COMMANDQUEUE_H">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks>
<codeblockwithcomments tag="enums" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
</hierarchicalcodeblock>
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //COMMANDQUEUE_H">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".h" parent_class="kihkGgfmWK0o" id="cppheaderkihkGgfmWK0o" fileName="ProcDispatcher" writeOutCode="true">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef PROCDISPATCHER_H&amp;#010;#define PROCDISPATCHER_H">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;#include &quot;dispatcherloop.h&quot;&amp;#010;">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks>
<codeblockwithcomments tag="enums" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</textblocks>
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //PROCDISPATCHER_H">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<codecomment tag=""/>
</header>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<classfields>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeclassfield role_id="-1" listClassName="" field_type="0" parent_id="wyW7zMFphhgG" writeOutMethods="true" initialValue="">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<ccfdeclarationcodeblock tag="tblock_0" parent_id="wyW7zMFphhgG" indentLevel="1" text=" deactivate;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false" indentLevel="1"/>
</header>
</ccfdeclarationcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod tag="hblock_tag_0" accessType="0" parent_id="wyW7zMFphhgG" indentLevel="1" classfield_id="wyW7zMFphhgG" text="return deactivate;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeaccessormethod tag="hblock_tag_1" accessType="1" parent_id="wyW7zMFphhgG" indentLevel="1" classfield_id="wyW7zMFphhgG" text="deactivate = value;" canDelete="false">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
<cppcodedocumentation tag="" indentLevel="1"/>
</header>
</codeaccessormethod>
</codeclassfield>
</classfields>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".h" parent_class="GkMAyqUK0GFO" id="cppheaderGkMAyqUK0GFO" fileName="SessionCommand" writeOutCode="true">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef SESSIONCOMMAND_H&amp;#010;#define SESSIONCOMMAND_H">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<codeblockwithcomments tag="using" writeOutText="false">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //SESSIONCOMMAND_H">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
</classifiercodedocument>
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".h" parent_class="rUnjINDv0ZKK" id="cppheaderrUnjINDv0ZKK" fileName="SessionCommandService" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="hashDefBlock" text="#ifndef SESSIONCOMMANDSERVICE_H&amp;#010;#define SESSIONCOMMANDSERVICE_H">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;#include &quot;sessioncommand.h&quot;&amp;#010;#include &quot;commanddispatch.h&quot;&amp;#010;">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks>
<codeblockwithcomments tag="enums" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</textblocks>
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //SESSIONCOMMANDSERVICE_H">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classfields/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".h" parent_class="k29coo6WqCqy" id="cppheaderk29coo6WqCqy" fileName="SessionImpl" writeOutCode="true">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef SESSIONIMPL_H&amp;#010;#define SESSIONIMPL_H">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</header>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;#include &quot;session.h&quot;&amp;#010;">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</header>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</codeblockwithcomments>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<codeblockwithcomments tag="using" writeOutText="false">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="enums" writeOutText="false">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</textblocks>
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //SESSIONIMPL_H">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classfields/>
</classifiercodedocument>
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".h" parent_class="YsfFJxnCRFW9" id="cppheaderYsfFJxnCRFW9" fileName="SessionSubsystem" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="hashDefBlock" text="#ifndef SESSIONSUBSYSTEM_H&amp;#010;#define SESSIONSUBSYSTEM_H">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;#include &quot;subsys.h&quot;&amp;#010;#include &quot;procdispatcher.h&quot;&amp;#010;">
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks>
<codeblockwithcomments tag="enums" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
</hierarchicalcodeblock>
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //SESSIONSUBSYSTEM_H">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
<classfields/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".h" parent_class="mPYman5InEvb" id="cppheadermPYman5InEvb" fileName="SessManagerImpl" writeOutCode="true">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef SESSMANAGERIMPL_H&amp;#010;#define SESSMANAGERIMPL_H">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;#include &quot;sessmanager.h&quot;&amp;#010;#include &quot;sessionimpl.h&quot;&amp;#010;#include &quot;lifecycleadvisor.h&quot;&amp;#010;">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
DOC: decision about where to home the SessionCommandService After some consideration, it became clear that this service implementation is closely tied to the DispatcherLoop -- which will consequently be responsible to run and expose this service implementation
2016-12-15 05:07:40 +01:00
<codeblockwithcomments tag="using" writeOutText="false">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="enums" writeOutText="false">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</textblocks>
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //SESSMANAGERIMPL_H">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classfields/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".h" parent_class="dfMQKri4XPmn" id="cppheaderdfMQKri4XPmn" fileName="DispatcherLoop" writeOutCode="true">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef DISPATCHERLOOP_H&amp;#010;#define DISPATCHERLOOP_H">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;#include &quot;commanddispatch.h&quot;&amp;#010;#include &quot;threadjoinable.h&quot;&amp;#010;#include &quot;commandqueue.h&quot;&amp;#010;">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<codeblockwithcomments tag="using" writeOutText="false">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks>
<codeblockwithcomments tag="enums" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //DISPATCHERLOOP_H">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classfields/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="3HXNyiJX20Ae" fileExt=".h" parent_class="MAnxOpF9GaE3" id="cppheaderMAnxOpF9GaE3" fileName="CommandDispatch" writeOutCode="true">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef COMMANDDISPATCH_H&amp;#010;#define COMMANDDISPATCH_H">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<textblocks/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //COMMANDDISPATCH_H">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classfields/>
</classifiercodedocument>
<classifiercodedocument package="Logical View" fileExt=".h" parent_class="vUTLjCtthGnz" id="cppheadervUTLjCtthGnz" fileName="Subsys" writeOutCode="true">
<textblocks>
<codeblockwithcomments tag="hashDefBlock" text="#ifndef SUBSYS_H&amp;#010;#define SUBSYS_H">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<cppcodedocumentation tag="" writeOutText="false"/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</codeblockwithcomments>
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
<textblocks/>
</hierarchicalcodeblock>
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //SUBSYS_H">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<header>
<codecomment tag=""/>
</header>
<classfields/>
</classifiercodedocument>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classifiercodedocument package="Logical View" fileExt=".h" parent_class="OkjgF2UByyJx" id="cppheaderOkjgF2UByyJx" fileName="ThreadJoinable" writeOutCode="true">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<textblocks>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlock" text="#ifndef THREADJOINABLE_H&amp;#010;#define THREADJOINABLE_H">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="includes" text="#include &lt;string>&amp;#010;">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<codeblockwithcomments tag="using" writeOutText="false">
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
<hierarchicalcodeblock tag="namespace" canDelete="false">
<header>
<cppcodedocumentation tag="" text="Namespace"/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<textblocks/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</hierarchicalcodeblock>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<codeblockwithcomments tag="hashDefBlockEnd" text="#endif //THREADJOINABLE_H">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<header>
<cppcodedocumentation tag="" writeOutText="false"/>
</header>
</codeblockwithcomments>
</textblocks>
<header>
<codecomment tag=""/>
</header>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<classfields/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</classifiercodedocument>
</codegenerator>
DOC: abandon BoUML and start over with Umbrello (closes #960) BoUML was close sourced by its author and consequently dropped from Debian. We use UML as a drawing and documentation tool, and thus we'll just start over with the /obvious/ choice, which is the Umbrello tool.
2016-11-19 00:13:19 +01:00
</codegeneration>
</XMI.extensions>
</XMI>
Reference in a new issue Copy permalink