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

1024 lines
118 KiB
Text
Raw Permalink 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"?>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<XMI xmi.version="1.2" xmlns:UML="http://schema.omg.org/spec/UML/1.4" verified="false" timestamp="2021-04-16T17:16:19">
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>
Tooling: Upgrade to Umbrello 4.17 (UML drawing tool) ..just open the existing uml/Lumiera.xmi and store it again
2021-04-16 15:50:22 +02:00
<XMI.exporterVersion>1.6.12</XMI.exporterVersion>
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.exporterEncoding>UnicodeUTF8</XMI.exporterEncoding>
</XMI.documentation>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<XMI.metamodel xmi.version="1.4" href="UML.xml" xmi.name="UML"/>
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.content>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Model xmi.id="m1" isSpecification="false" isRoot="false" name="UML Model" isAbstract="false" isLeaf="false">
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Stereotype visibility="public" xmi.id="folder" namespace="m1" isSpecification="false" isRoot="false" isAbstract="false" name="folder" isLeaf="false"/>
<UML:Stereotype visibility="public" xmi.id="datatype" namespace="m1" isSpecification="false" isRoot="false" isAbstract="false" name="datatype" isLeaf="false"/>
<UML:Stereotype visibility="public" xmi.id="constructor" namespace="m1" isSpecification="false" isRoot="false" isAbstract="false" name="constructor" isLeaf="false"/>
<UML:Stereotype visibility="public" xmi.id="friend" namespace="m1" isSpecification="false" isRoot="false" isAbstract="false" name="friend" isLeaf="false"/>
<UML:Stereotype visibility="public" xmi.id="virtual" namespace="m1" isSpecification="false" isRoot="false" isAbstract="false" name="virtual" isLeaf="false"/>
<UML:Stereotype visibility="public" xmi.id="owns" namespace="m1" isSpecification="false" isRoot="false" isAbstract="false" name="owns" isLeaf="false"/>
<UML:Stereotype visibility="public" xmi.id="interface" namespace="m1" isSpecification="false" isRoot="false" isAbstract="false" name="interface" isLeaf="false"/>
<UML:Model visibility="public" stereotype="folder" xmi.id="Logical View" namespace="m1" isSpecification="false" isRoot="false" isAbstract="false" name="Logical View" isLeaf="false">
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Package visibility="public" stereotype="folder" xmi.id="Datatypes" namespace="Logical View" isSpecification="false" isRoot="false" isAbstract="false" name="Datatypes" isLeaf="false">
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:DataType visibility="public" stereotype="datatype" xmi.id="mhSdaAG81L4V" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="int" isLeaf="false"/>
<UML:DataType visibility="public" stereotype="datatype" xmi.id="15L0hJXhwcFR" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="char" isLeaf="false"/>
<UML:DataType visibility="public" stereotype="datatype" xmi.id="c4Twqn0aUQB4" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="bool" isLeaf="false"/>
<UML:DataType visibility="public" stereotype="datatype" xmi.id="aPBblD5kGQlv" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="float" isLeaf="false"/>
<UML:DataType visibility="public" stereotype="datatype" xmi.id="hGddsq3TsUPg" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="double" isLeaf="false"/>
<UML:DataType visibility="public" stereotype="datatype" xmi.id="HOEjoPmPovyX" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="short" isLeaf="false"/>
<UML:DataType visibility="public" stereotype="datatype" xmi.id="83IMS1F7HsjA" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="long" isLeaf="false"/>
<UML:DataType visibility="public" stereotype="datatype" xmi.id="gkbWE0CWOQFD" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="unsigned int" isLeaf="false"/>
<UML:DataType visibility="public" stereotype="datatype" xmi.id="n1aawY72aPM0" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="unsigned short" isLeaf="false"/>
<UML:DataType visibility="public" stereotype="datatype" xmi.id="Qc5iSoq7YRdn" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="unsigned long" isLeaf="false"/>
<UML:DataType visibility="public" stereotype="datatype" xmi.id="RoHoEUz0UZaO" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="string" isLeaf="false"/>
<UML:DataType visibility="public" stereotype="datatype" xmi.id="pFknC1jVXUTk" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="Session*" isLeaf="false"/>
<UML:DataType visibility="public" xmi.id="uMMCCegdWRMed" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="unsigned char" isLeaf="false"/>
<UML:DataType visibility="public" xmi.id="uNC1udGnuzN2S" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="signed char" isLeaf="false"/>
<UML:DataType visibility="public" xmi.id="ub2aLimnOvCc8" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="signed int" isLeaf="false"/>
<UML:DataType visibility="public" xmi.id="uQjH8LmECcyqd" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="short int" isLeaf="false"/>
<UML:DataType visibility="public" xmi.id="uI4uVfXWHwlj8" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="unsigned short int" isLeaf="false"/>
<UML:DataType visibility="public" xmi.id="ufJzUkPpx5QnH" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="signed short int" isLeaf="false"/>
<UML:DataType visibility="public" xmi.id="uNqycOxR6x9BP" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="long int" isLeaf="false"/>
<UML:DataType visibility="public" xmi.id="uTDfsr4Knx3AZ" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="signed long int" isLeaf="false"/>
<UML:DataType visibility="public" xmi.id="uIVzscMhthEou" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="unsigned long int" isLeaf="false"/>
<UML:DataType visibility="public" xmi.id="uWIJRjMnWEHh8" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="long double" isLeaf="false"/>
<UML:DataType visibility="public" xmi.id="unGP2JF0ACOa5" namespace="Datatypes" isSpecification="false" isRoot="false" isAbstract="false" name="wchar_t" isLeaf="false"/>
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Package visibility="public" stereotype="folder" xmi.id="dzlPCiVfMhDw" namespace="Logical View" isSpecification="false" isRoot="false" isAbstract="false" name="GUI" isLeaf="false">
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Package visibility="public" stereotype="folder" xmi.id="AP2Jw6O9SyPl" namespace="dzlPCiVfMhDw" isSpecification="false" isRoot="false" isAbstract="false" name="Backbone" isLeaf="false">
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: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Class visibility="public" xmi.id="zt9QqECndhuG" namespace="AP2Jw6O9SyPl" isSpecification="false" isRoot="false" isAbstract="false" name="Controller" isLeaf="false">
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:Generalization xmi.idref="iWjGfYBc3xqk"/>
</UML:GeneralizableElement.generalization>
</UML:Class>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Class visibility="public" xmi.id="YVUu5DY24gSv" namespace="AP2Jw6O9SyPl" isSpecification="false" isRoot="false" isAbstract="false" name="BusTerm" isLeaf="false"/>
<UML:Class visibility="public" xmi.id="zQV7dGUdKiTL" namespace="AP2Jw6O9SyPl" isSpecification="false" isRoot="false" isAbstract="false" name="Tangible" isLeaf="false"/>
<UML:Class visibility="public" xmi.id="CIgVjFGNUjOp" namespace="AP2Jw6O9SyPl" isSpecification="false" isRoot="false" isAbstract="false" name="Widget" isLeaf="false">
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:Generalization xmi.idref="iwOwLnrzR97o"/>
</UML:GeneralizableElement.generalization>
</UML:Class>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Class visibility="public" xmi.id="AAXrURgiB2s9" namespace="AP2Jw6O9SyPl" isSpecification="false" isRoot="false" isAbstract="false" name="CoreService" isLeaf="false"/>
<UML:Class visibility="public" xmi.id="ezNd14Qkbz9H" namespace="AP2Jw6O9SyPl" isSpecification="false" isRoot="false" isAbstract="false" name="InteractionDirector" isLeaf="false"/>
<UML:Class visibility="public" xmi.id="SgmkxaeiRNDo" namespace="AP2Jw6O9SyPl" isSpecification="false" isRoot="false" isAbstract="true" name="InteractionState" isLeaf="false"/>
<UML:Interface visibility="public" stereotype="interface" xmi.id="lqjWPWP1VmdU" namespace="AP2Jw6O9SyPl" isSpecification="false" isRoot="false" isAbstract="true" name="CmdContext" isLeaf="false"/>
<UML:Class visibility="public" xmi.id="ODwy08rSmbAj" namespace="AP2Jw6O9SyPl" isSpecification="false" isRoot="false" isAbstract="false" name="InvocationTrail" isLeaf="false"/>
<UML:Interface visibility="public" stereotype="interface" xmi.id="PHufJfyMo4sv" namespace="AP2Jw6O9SyPl" isSpecification="false" isRoot="false" isAbstract="true" name="UI-Bus" isLeaf="false"/>
<UML:Interface visibility="public" stereotype="interface" xmi.id="urSQTv4G8xNl1" namespace="AP2Jw6O9SyPl" isSpecification="false" isRoot="false" isAbstract="true" name="Subject" isLeaf="false"/>
<UML:Class visibility="public" xmi.id="uVhgPcx3vVYia" namespace="AP2Jw6O9SyPl" isSpecification="false" isRoot="false" isAbstract="false" name="XYZ GestureCtrl" isLeaf="false">
<UML:GeneralizableElement.generalization>
<UML:Generalization xmi.idref="uDxR5SQ0wY8cN"/>
</UML:GeneralizableElement.generalization>
</UML:Class>
<UML:Class visibility="public" xmi.id="uanDLLZ8VytjK" namespace="AP2Jw6O9SyPl" isSpecification="false" isRoot="false" isAbstract="false" name="GestureState" isLeaf="false"/>
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Package visibility="public" stereotype="folder" xmi.id="iJ1021VZA242" namespace="dzlPCiVfMhDw" isSpecification="false" isRoot="false" isAbstract="false" name="Timeline" isLeaf="false">
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: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Class visibility="public" xmi.id="r2bQMphsIClM" namespace="iJ1021VZA242" isSpecification="false" isRoot="false" isAbstract="false" name="TrackPresenter" isLeaf="false">
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Class visibility="public" xmi.id="TxRGe5zBPLEk" namespace="iJ1021VZA242" isSpecification="false" isRoot="false" isAbstract="false" name="ClipWidget" isLeaf="false">
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:Generalization xmi.idref="XrxbmnLBD6Pa"/>
</UML:GeneralizableElement.generalization>
</UML:Class>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Class visibility="public" xmi.id="YML3K4y9h5tE" namespace="iJ1021VZA242" isSpecification="false" isRoot="false" isAbstract="false" name="ClipPresenter" isLeaf="false">
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:Generalization xmi.idref="cz4YZYaRa9pv"/>
</UML:GeneralizableElement.generalization>
</UML:Class>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Class visibility="public" xmi.id="8QIySCNjv8Nm" namespace="iJ1021VZA242" isSpecification="false" isRoot="false" isAbstract="false" name="TrackBodyWidget" isLeaf="false"/>
<UML:Class visibility="public" xmi.id="IlnerbEbwJog" namespace="iJ1021VZA242" isSpecification="false" isRoot="false" isAbstract="false" name="TrackHeadWidget" isLeaf="false"/>
<UML:Interface visibility="public" stereotype="interface" xmi.id="wB7sY2nRjOXn" namespace="iJ1021VZA242" isSpecification="false" isRoot="false" isAbstract="true" name="Element" isLeaf="false">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<UML:Classifier.feature>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Operation visibility="public" xmi.id="m71ADYgKdI1Q" isQuery="false" isSpecification="false" isRoot="false" isAbstract="false" name="allocate" isLeaf="false">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<UML:BehavioralFeature.parameter>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Parameter visibility="private" type="WIX6g3bhkPMX" xmi.id="FNAvlwvJBiEK" isSpecification="false" name="evaluation" value=""/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</UML:BehavioralFeature.parameter>
</UML:Operation>
</UML:Classifier.feature>
</UML:Interface>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Class visibility="public" xmi.id="WIX6g3bhkPMX" namespace="iJ1021VZA242" isSpecification="false" isRoot="false" isAbstract="false" name="DisplayEvaluation" isLeaf="false">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<UML:Classifier.feature>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Attribute visibility="private" type="1l72I7ToPys3" xmi.id="MAWVsNUcUWni" isSpecification="false" name="manager"/>
<UML:Operation visibility="public" xmi.id="SjGuD1cFQas5" isQuery="false" isSpecification="false" isRoot="false" isAbstract="false" name="evaluateChild" isLeaf="false">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<UML:BehavioralFeature.parameter>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Parameter visibility="private" type="wB7sY2nRjOXn" xmi.id="cv0y6n6BWVRw" isSpecification="false" name="element" value=""/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</UML:BehavioralFeature.parameter>
</UML:Operation>
</UML:Classifier.feature>
</UML:Class>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Interface visibility="public" stereotype="interface" xmi.id="1l72I7ToPys3" namespace="iJ1021VZA242" isSpecification="false" isRoot="false" isAbstract="true" name="DisplayManager" isLeaf="false">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<UML:Classifier.feature>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Operation visibility="public" xmi.id="87ehnyLmiQo0" isQuery="false" isSpecification="false" isRoot="false" isAbstract="false" name="evaluate" isLeaf="false">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<UML:BehavioralFeature.parameter>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Parameter visibility="private" type="wB7sY2nRjOXn" xmi.id="XFnvBfyB9ht1" isSpecification="false" name="element" value=""/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<diagram zoom="100" backgroundcolor="#ffffff" isopen="0" xmi.id="tyAwJXVRd8yU" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" snapgrid="1" usefillcolor="1" showattribassocs="1" localid="-1" textcolor="#000000" showattsig="1" griddotcolor="#d3d3d3" showstereotype="1" type="1" snapx="10" documentation="" canvasheight="260" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" showops="1" showopsig="1" canvaswidth="470" showatts="1" snapy="10" snapcsgrid="1" showgrid="1" name="display_evaluation">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<widgets>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<classwidget usesdiagramusefillcolor="0" width="100" showoperations="1" xmi.id="YML3K4y9h5tE" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-310" usefillcolor="1" localid="h5idAOxedsSi" textcolor="#000000" showattributes="1" isinstance="0" x="-540" showstereotype="1" height="30" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="110" showoperations="1" xmi.id="r2bQMphsIClM" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-330" usefillcolor="1" localid="NHOSxrLoU1Ho" textcolor="#000000" showattributes="1" isinstance="0" x="-670" showstereotype="1" height="30" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<interfacewidget usesdiagramusefillcolor="0" width="250" showoperations="1" drawascircle="0" xmi.id="wB7sY2nRjOXn" fillcolor="#ffffc0" linewidth="0" showpackage="1" showscope="1" y="-450" usefillcolor="1" localid="L1yddNoXLwTc" textcolor="#000000" showattributes="0" isinstance="0" x="-670" showstereotype="1" height="50" showpubliconly="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="210" showoperations="1" xmi.id="WIX6g3bhkPMX" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-510" usefillcolor="1" localid="9LtY72a9biMe" textcolor="#000000" showattributes="1" isinstance="0" x="-670" showstereotype="1" height="40" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<interfacewidget usesdiagramusefillcolor="0" width="190" showoperations="1" drawascircle="0" xmi.id="1l72I7ToPys3" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-540" usefillcolor="1" localid="0Ujit5F0Q6YV" textcolor="#000000" showattributes="0" isinstance="0" x="-890" showstereotype="1" height="50" showpubliconly="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="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>
<messages/>
<associations>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="r2bQMphsIClM" xmi.id="TdTehsF1A2Mv" fillcolor="#ffff00" totalcounta="2" widgetbid="YML3K4y9h5tE" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="510" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-560" starty="-300"/>
<endpoint endx="-540" endy="-300"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="r2bQMphsIClM" xmi.id="Tw2630Yx9gph" fillcolor="#ffff00" totalcounta="2" widgetbid="wB7sY2nRjOXn" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="511" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-620.623" starty="-330"/>
<endpoint endx="-560.7" endy="-400"/>
Tooling: Upgrade to Umbrello 4.17 (UML drawing tool) ..just open the existing uml/Lumiera.xmi and store it again
2021-04-16 15:50:22 +02:00
<point x="-620.623" y="-350.584"/>
<point x="-560.7" y="-350.584"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="YML3K4y9h5tE" xmi.id="Sk9bQzG6aNWX" fillcolor="#ffff00" totalcounta="2" widgetbid="wB7sY2nRjOXn" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="511" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-500" starty="-310"/>
<endpoint endx="-560.7" endy="-400"/>
Tooling: Upgrade to Umbrello 4.17 (UML drawing tool) ..just open the existing uml/Lumiera.xmi and store it again
2021-04-16 15:50:22 +02:00
<point x="-500" y="-350.195"/>
<point x="-560.7" y="-350.195"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="WIX6g3bhkPMX" xmi.id="MAWVsNUcUWni" fillcolor="#ffff00" totalcounta="2" widgetbid="1l72I7ToPys3" linewidth="0" indexb="1" usefillcolor="1" textcolor="#000000" visibilityA="1" indexa="1" visibilityB="1" type="512" changeabilityA="900" changeabilityB="900" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-670" starty="-510"/>
<endpoint endx="-700" endy="-510"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</linepath>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<floatingtext usesdiagramusefillcolor="1" text="manager" posttext="" width="70" xmi.id="7jPGPdall6Fd" fillcolor="none" linewidth="none" pretext="-" y="-530" usefillcolor="1" localid="2R0fh13uMDp8" textcolor="none" isinstance="0" x="-700" showstereotype="1" height="20" font="Sans Serif,9,-1,5,50,0,0,0,0,0" linecolor="none" role="710" usesdiagramfillcolor="1" autoresize="1"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="1l72I7ToPys3" xmi.id="62hs6uTYehTp" fillcolor="#ffff00" totalcounta="2" widgetbid="wB7sY2nRjOXn" linewidth="0" indexb="1" usefillcolor="1" textcolor="#000000" indexa="1" type="502" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-721" starty="-490"/>
<endpoint endx="-670" endy="-410"/>
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="-721" y="-410"/>
</linepath>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<floatingtext usesdiagramusefillcolor="1" text="invokes" posttext="" width="50" xmi.id="wvwv9HfrxE5j" fillcolor="none" linewidth="none" pretext="" y="-430" usefillcolor="1" localid="jjlNCOhc9Dp4" textcolor="none" isinstance="0" x="-730" showstereotype="1" height="20" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" role="703" usesdiagramfillcolor="1" autoresize="1"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="wB7sY2nRjOXn" xmi.id="yABcqeRWgUdK" fillcolor="#ffff00" totalcounta="2" widgetbid="WIX6g3bhkPMX" linewidth="0" indexb="1" usefillcolor="1" textcolor="#000000" indexa="1" type="502" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-633" starty="-450"/>
<endpoint endx="-633" endy="-470"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</linepath>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<floatingtext usesdiagramusefillcolor="1" text="triggers recursive" posttext="" width="110" xmi.id="GoFP24RyzOr6" fillcolor="none" linewidth="none" pretext="" y="-470" usefillcolor="1" localid="UzRv4l9lTu9f" textcolor="none" isinstance="0" x="-630" showstereotype="1" height="20" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" role="703" usesdiagramfillcolor="1" autoresize="1"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Package visibility="public" xmi.id="50pVMRCQE3mT" namespace="dzlPCiVfMhDw" isSpecification="false" isRoot="false" isAbstract="false" name="Gtk" isLeaf="false">
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: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Class visibility="public" xmi.id="04Gq3mqRDSTZ" namespace="50pVMRCQE3mT" isSpecification="false" isRoot="false" isAbstract="false" name="Gtk::Layout" isLeaf="false"/>
<UML:Class visibility="public" xmi.id="QTe1L5jo295e" namespace="50pVMRCQE3mT" isSpecification="false" isRoot="false" isAbstract="false" name="Gtk::Frame" isLeaf="false"/>
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:Namespace.ownedElement>
</UML:Package>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Package visibility="public" stereotype="folder" xmi.id="ZJjfeyODnhwR" namespace="Logical View" isSpecification="false" isRoot="false" isAbstract="false" name="Proc" isLeaf="false">
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Package visibility="public" stereotype="folder" xmi.id="3HXNyiJX20Ae" namespace="ZJjfeyODnhwR" isSpecification="false" isRoot="false" isAbstract="false" name="Session" isLeaf="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
<UML:Namespace.ownedElement>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Interface visibility="public" stereotype="interface" xmi.id="vXeW5rShP4KV" namespace="3HXNyiJX20Ae" isSpecification="false" isRoot="false" isAbstract="true" name="Session" isLeaf="false"/>
<UML:Interface visibility="public" stereotype="interface" xmi.id="i28J9X534hZ9" namespace="3HXNyiJX20Ae" isSpecification="false" isRoot="false" isAbstract="true" name="SessManager" isLeaf="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
<UML:Classifier.feature>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Operation visibility="public" xmi.id="pVqpkd56Npnb" isQuery="false" isSpecification="false" isRoot="false" isAbstract="false" name="operator->" isLeaf="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
<UML:BehavioralFeature.parameter>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Parameter type="pFknC1jVXUTk" xmi.id="wogG2YqUjTK1" kind="return"/>
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:BehavioralFeature.parameter>
</UML:Operation>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Operation visibility="public" xmi.id="tgE8kCyZfoMP" isQuery="false" isSpecification="false" isRoot="false" isAbstract="false" name="load" isLeaf="false"/>
<UML:Operation visibility="public" xmi.id="PSTlFEK4S4pe" isQuery="false" isSpecification="false" isRoot="false" isAbstract="false" name="save" isLeaf="false"/>
<UML:Operation visibility="public" xmi.id="6Y9d0aMtHa01" isQuery="false" isSpecification="false" isRoot="false" isAbstract="false" name="close" isLeaf="false"/>
<UML:Operation visibility="public" xmi.id="kyZPlvm8LFta" isQuery="false" isSpecification="false" isRoot="false" isAbstract="false" name="reset" isLeaf="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
</UML:Classifier.feature>
</UML:Interface>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Class visibility="public" xmi.id="SDesIUWO0dz1" namespace="3HXNyiJX20Ae" isSpecification="false" isRoot="false" isAbstract="false" name="LifecycleAdvisor" isLeaf="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
<UML:Classifier.feature>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Operation visibility="public" xmi.id="KsbZ85POo9Lg" isQuery="false" isSpecification="false" isRoot="false" isAbstract="false" name="pullUp" isLeaf="false"/>
<UML:Operation visibility="public" xmi.id="zzlJ9A4Ksadb" isQuery="false" isSpecification="false" isRoot="false" isAbstract="false" name="shutDown" isLeaf="false"/>
<UML:Operation visibility="public" xmi.id="cv5AydHGTsoa" isQuery="false" isSpecification="false" isRoot="false" isAbstract="false" name="openSessionInterface" isLeaf="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
</UML:Classifier.feature>
</UML:Class>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Class visibility="public" xmi.id="lSL6pzQhTDOj" namespace="3HXNyiJX20Ae" isSpecification="false" isRoot="false" isAbstract="false" name="CommandQueue" isLeaf="false"/>
<UML:Class visibility="public" xmi.id="kihkGgfmWK0o" namespace="3HXNyiJX20Ae" isSpecification="false" isRoot="false" isAbstract="false" name="SteamDispatcher" isLeaf="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
<UML:Classifier.feature>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Attribute visibility="private" xmi.id="wyW7zMFphhgG" isSpecification="false" name="deactivate"/>
<UML:Operation visibility="public" xmi.id="RFgnI9xTKVIo" isQuery="false" isSpecification="false" isRoot="false" isAbstract="false" name="activate" isLeaf="false"/>
<UML:Operation visibility="public" xmi.id="KsrSalZ00FnI" isQuery="false" isSpecification="false" isRoot="false" isAbstract="false" name="deactivate" isLeaf="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
</UML:Classifier.feature>
</UML:Class>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Interface visibility="public" stereotype="interface" xmi.id="GkMAyqUK0GFO" namespace="3HXNyiJX20Ae" isSpecification="false" isRoot="false" isAbstract="true" name="SessionCommand" isLeaf="false"/>
<UML:Class visibility="public" xmi.id="rUnjINDv0ZKK" namespace="3HXNyiJX20Ae" isSpecification="false" isRoot="false" isAbstract="false" name="SessionCommandService" isLeaf="false"/>
<UML:Class visibility="public" xmi.id="k29coo6WqCqy" namespace="3HXNyiJX20Ae" isSpecification="false" isRoot="false" isAbstract="false" name="SessionImpl" isLeaf="false"/>
<UML:Class visibility="public" xmi.id="YsfFJxnCRFW9" namespace="3HXNyiJX20Ae" isSpecification="false" isRoot="false" isAbstract="false" name="SessionSubsystem" isLeaf="false"/>
<UML:Class visibility="public" xmi.id="mPYman5InEvb" namespace="3HXNyiJX20Ae" isSpecification="false" isRoot="false" isAbstract="false" name="SessManagerImpl" isLeaf="false"/>
<UML:Class visibility="public" xmi.id="dfMQKri4XPmn" namespace="3HXNyiJX20Ae" isSpecification="false" isRoot="false" isAbstract="false" name="DispatcherLoop" isLeaf="false"/>
<UML:Interface visibility="public" stereotype="interface" xmi.id="MAnxOpF9GaE3" namespace="3HXNyiJX20Ae" isSpecification="false" isRoot="false" isAbstract="true" name="CommandDispatch" isLeaf="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
</UML:Namespace.ownedElement>
<XMI.extension xmi.extender="umbrello">
<diagrams>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<diagram zoom="100" backgroundcolor="#ffffff" isopen="0" xmi.id="ZM3pbwOfd7Ql" fillcolor="#ffffc0" linewidth="0" showpackage="1" showscope="1" snapgrid="1" usefillcolor="1" showattribassocs="1" localid="-1" textcolor="#000000" showattsig="1" griddotcolor="#d3d3d3" showstereotype="1" type="1" snapx="10" documentation="service&#xa;impl&#xa;" canvasheight="390" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" showops="1" showopsig="1" canvaswidth="960" showatts="1" snapy="10" snapcsgrid="1" showgrid="1" name="session_subsystem">
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<interfacewidget usesdiagramusefillcolor="0" width="90" showoperations="1" drawascircle="0" xmi.id="vXeW5rShP4KV" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-710" usefillcolor="1" localid="uwmKIYlruoeT" textcolor="#000000" showattributes="0" isinstance="0" x="-370" showstereotype="1" height="40" showpubliconly="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<interfacewidget usesdiagramusefillcolor="0" width="150" showoperations="1" drawascircle="0" xmi.id="i28J9X534hZ9" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-670" usefillcolor="1" localid="X1ow46Rw2BHK" textcolor="#000000" showattributes="0" isinstance="0" x="-540" showstereotype="1" height="100" showpubliconly="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="90" showoperations="1" xmi.id="k29coo6WqCqy" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-490" usefillcolor="1" localid="ht1lYYt5Yfzc" textcolor="#000000" showattributes="1" isinstance="0" x="-370" showstereotype="1" height="30" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="130" showoperations="1" xmi.id="mPYman5InEvb" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-490" usefillcolor="1" localid="0z6r9unrloaJ" textcolor="#000000" showattributes="1" isinstance="0" x="-530" showstereotype="1" height="30" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="130" showoperations="1" xmi.id="YsfFJxnCRFW9" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-540" usefillcolor="1" localid="RN28ep7sngXJ" textcolor="#000000" showattributes="1" isinstance="0" x="-1100" showstereotype="1" height="30" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="120" showoperations="1" xmi.id="kihkGgfmWK0o" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-520" usefillcolor="1" localid="Hn0h2UoTsqaW" textcolor="#000000" showattributes="1" isinstance="0" x="-910" showstereotype="1" height="50" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="110" showoperations="1" xmi.id="dfMQKri4XPmn" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-610" usefillcolor="1" localid="6RXalXO1LPgL" textcolor="#000000" showattributes="1" isinstance="0" x="-850" showstereotype="1" height="30" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="170" showoperations="1" xmi.id="rUnjINDv0ZKK" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-720" usefillcolor="1" localid="Q0MxP9iTaE4K" textcolor="#000000" showattributes="1" isinstance="0" x="-1070" showstereotype="1" height="30" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="120" showoperations="1" xmi.id="lSL6pzQhTDOj" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-590" usefillcolor="1" localid="YceY9wrYwDTK" textcolor="#000000" showattributes="1" isinstance="0" x="-710" showstereotype="1" height="30" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<interfacewidget usesdiagramusefillcolor="0" width="130" showoperations="1" drawascircle="0" xmi.id="MAnxOpF9GaE3" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-710" usefillcolor="1" localid="Xeiyr7hNhJvq" textcolor="#000000" showattributes="0" isinstance="0" x="-850" showstereotype="1" height="40" showpubliconly="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<interfacewidget usesdiagramusefillcolor="0" width="130" showoperations="1" drawascircle="0" xmi.id="GkMAyqUK0GFO" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-830" usefillcolor="1" localid="3UXJ2jLXN3VC" textcolor="#000000" showattributes="0" isinstance="0" x="-1070" showstereotype="1" height="40" showpubliconly="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="90" showoperations="1" xmi.id="AAXrURgiB2s9" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-830" usefillcolor="1" localid="sLSqZfCc8iu8" textcolor="#000000" showattributes="1" isinstance="0" x="-1210" showstereotype="1" height="30" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="160" showoperations="1" xmi.id="SDesIUWO0dz1" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-530" usefillcolor="1" localid="BLsSvsUfp14Y" textcolor="#000000" showattributes="1" isinstance="0" x="-710" showstereotype="1" height="60" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<boxwidget textcolor="#000000" usefillcolor="1" height="280" isinstance="0" linewidth="0" xmi.id="h6yyGXMa92kK" fillcolor="#ffffc0" linecolor="#000000" autoresize="1" x="-550" y="-720" width="290" usesdiagramfillcolor="0" showstereotype="1" localid="SFPt5DT0OQih" usesdiagramusefillcolor="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<notewidget usesdiagramusefillcolor="0" text="in GUI&#xa;" width="60" xmi.id="shNxnUTbqlXV" fillcolor="#e6ffd5" linewidth="0" y="-780" usefillcolor="1" localid="UslNKbislGZA" textcolor="#000000" isinstance="0" x="-1220" showstereotype="1" height="30" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" usesdiagramfillcolor="0" autoresize="1" noteType="0"/>
<notewidget usesdiagramusefillcolor="0" text="service&#xa;impl&#xa;" width="70" xmi.id="e8PPMyaCev9R" fillcolor="#e6ffd5" linewidth="0" y="-780" usefillcolor="1" localid="LzZpcNJ4F3PX" textcolor="#000000" isinstance="0" x="-910" showstereotype="1" height="40" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" usesdiagramfillcolor="0" autoresize="1" noteType="0"/>
<floatingtext usesdiagramusefillcolor="0" text="static" posttext="" width="40" xmi.id="dKSRnxZ7HiiZ" fillcolor="#ffffc0" linewidth="0" pretext="" y="-470" usefillcolor="1" localid="PWP3G7XBbTvr" textcolor="#000000" isinstance="0" x="-910" showstereotype="1" height="20" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0" linecolor="none" role="700" usesdiagramfillcolor="0" autoresize="1"/>
<floatingtext usesdiagramusefillcolor="0" text="static" posttext="" width="40" xmi.id="dKSRnxZ7HiiZ" fillcolor="#ffffc0" linewidth="0" pretext="" y="-460" usefillcolor="1" localid="f4OEWH59aVZL" textcolor="#000000" isinstance="0" x="-530" showstereotype="1" height="20" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0" linecolor="none" role="700" usesdiagramfillcolor="0" autoresize="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>
<messages/>
<associations>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="rUnjINDv0ZKK" xmi.id="vqNvRLucgl3c" fillcolor="#ffff00" totalcounta="2" widgetbid="GkMAyqUK0GFO" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="511" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="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
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-1060" starty="-720"/>
<endpoint endx="-1060" endy="-790"/>
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="dfMQKri4XPmn" xmi.id="Jn8ZrYJCuWdu" fillcolor="#ffff00" totalcounta="2" widgetbid="MAnxOpF9GaE3" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="511" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="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
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-790.355" starty="-610"/>
<endpoint endx="-790.355" endy="-670"/>
Tooling: Upgrade to Umbrello 4.17 (UML drawing tool) ..just open the existing uml/Lumiera.xmi and store it again
2021-04-16 15:50:22 +02:00
<point x="-790.355" y="-630.457"/>
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="mPYman5InEvb" xmi.id="UNNmnUMGfGd5" fillcolor="none" totalcounta="2" widgetbid="i28J9X534hZ9" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="511" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="1" autoresize="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
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-473" starty="-490"/>
<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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="k29coo6WqCqy" xmi.id="2ZLhpznz5WwR" fillcolor="#ffff00" totalcounta="2" widgetbid="vXeW5rShP4KV" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="511" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="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
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-333.5" starty="-490"/>
<endpoint endx="-333.5" endy="-670"/>
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="i28J9X534hZ9" xmi.id="7B8Ch3bX8MJP" fillcolor="#ffff00" totalcounta="2" widgetbid="vXeW5rShP4KV" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="512" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="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
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-390" starty="-630.814"/>
<endpoint endx="-370" endy="-670"/>
Tooling: Upgrade to Umbrello 4.17 (UML drawing tool) ..just open the existing uml/Lumiera.xmi and store it again
2021-04-16 15:50:22 +02:00
<point x="-380.814" y="-630.814"/>
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="mPYman5InEvb" xmi.id="C89KUQhNBiSL" fillcolor="#ffff00" totalcounta="2" widgetbid="k29coo6WqCqy" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="512" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="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
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-400" starty="-466"/>
<endpoint endx="-370" endy="-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
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="mPYman5InEvb" xmi.id="fCPqup9XS4Fq" fillcolor="#ffff00" totalcounta="2" widgetbid="SDesIUWO0dz1" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="512" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="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
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-530" starty="-478"/>
<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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="dfMQKri4XPmn" xmi.id="LSrnW4bmjOM9" fillcolor="none" totalcounta="2" widgetbid="lSL6pzQhTDOj" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="512" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="1" autoresize="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
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-740" starty="-580"/>
<endpoint endx="-710" endy="-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
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="kihkGgfmWK0o" xmi.id="XRdEpxNnRWHz" fillcolor="#ffff00" totalcounta="2" widgetbid="dfMQKri4XPmn" linewidth="0" indexb="1" usefillcolor="1" textcolor="#000000" indexa="1" type="512" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="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
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-790.116" starty="-511.047"/>
<endpoint endx="-790.116" endy="-580"/>
Tooling: Upgrade to Umbrello 4.17 (UML drawing tool) ..just open the existing uml/Lumiera.xmi and store it again
2021-04-16 15:50:22 +02:00
<point x="-790.116" y="-511.047"/>
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<floatingtext usesdiagramusefillcolor="1" text="PImpl" posttext="" width="40" xmi.id="D5Czp653fmkW" fillcolor="none" linewidth="none" pretext="" y="-550" usefillcolor="1" localid="Kc5vMuq2GxNY" textcolor="none" isinstance="0" x="-839" showstereotype="1" height="20" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" role="703" usesdiagramfillcolor="1" autoresize="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
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="rUnjINDv0ZKK" xmi.id="oa1E4HBEXCgX" fillcolor="#ffff00" totalcounta="2" widgetbid="MAnxOpF9GaE3" linewidth="0" indexb="1" usefillcolor="1" textcolor="#000000" indexa="1" type="512" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="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
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-900" starty="-710"/>
<endpoint endx="-850" endy="-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
</linepath>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<floatingtext usesdiagramusefillcolor="1" text="use" posttext="" width="30" xmi.id="MLAbIV7TaJRO" fillcolor="none" linewidth="none" pretext="" y="-710" usefillcolor="1" localid="uTwmICPcoUV8" textcolor="none" isinstance="0" x="-905" showstereotype="1" height="20" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" role="703" usesdiagramfillcolor="1" autoresize="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
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="YsfFJxnCRFW9" xmi.id="l65HIjmbuCFE" fillcolor="#ffff00" totalcounta="2" widgetbid="kihkGgfmWK0o" linewidth="0" indexb="1" usefillcolor="1" textcolor="#000000" indexa="1" type="502" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="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
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-1020" starty="-510"/>
<endpoint endx="-910" endy="-491"/>
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
<point x="-1020" y="-491"/>
</linepath>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<floatingtext usesdiagramusefillcolor="1" text="start/stop" posttext="" width="70" xmi.id="Gbiiq8jSsrHe" fillcolor="none" linewidth="none" pretext="" y="-510" usefillcolor="1" localid="gM9KHGkgokt6" textcolor="none" isinstance="0" x="-1020" showstereotype="1" height="20" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" role="703" usesdiagramfillcolor="1" autoresize="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
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="SDesIUWO0dz1" xmi.id="JlsDx7Pt5zUz" fillcolor="#ffff00" totalcounta="2" widgetbid="kihkGgfmWK0o" linewidth="0" indexb="1" usefillcolor="1" textcolor="#000000" indexa="1" type="502" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="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
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-710" starty="-479"/>
<endpoint endx="-790" 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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<floatingtext usesdiagramusefillcolor="1" text="controls" posttext="" width="60" xmi.id="cl7poVMRbkox" fillcolor="none" linewidth="none" pretext="" y="-480" usefillcolor="1" localid="Pa0FJVicSHS3" textcolor="none" isinstance="0" x="-770" showstereotype="1" height="20" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" role="703" usesdiagramfillcolor="1" autoresize="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
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="AAXrURgiB2s9" xmi.id="GUZLT1InA1V1" fillcolor="#ffff00" totalcounta="2" widgetbid="GkMAyqUK0GFO" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="512" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="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
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-1120" starty="-820"/>
<endpoint endx="-1070" endy="-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
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="shNxnUTbqlXV" fillcolor="#ffff00" totalcounta="2" widgetbid="AAXrURgiB2s9" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" visibilityA="0" indexa="1" roleAdoc="" visibilityB="0" type="513" roleBdoc="" changeabilityA="900" changeabilityB="900" documentation="" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="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
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-1170.5" starty="-780"/>
<endpoint endx="-1170.5" endy="-800"/>
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="e8PPMyaCev9R" fillcolor="#ffff00" totalcounta="2" widgetbid="rUnjINDv0ZKK" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" visibilityA="0" indexa="1" roleAdoc="" visibilityB="0" type="513" roleBdoc="" changeabilityA="900" changeabilityB="900" documentation="" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="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
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-910" starty="-740"/>
<endpoint endx="-910" endy="-720"/>
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>
</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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Package visibility="public" stereotype="folder" xmi.id="wYrkFnB1ygmi" namespace="ZJjfeyODnhwR" isSpecification="false" isRoot="false" isAbstract="false" name="Builder" isLeaf="false">
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Package visibility="public" stereotype="folder" xmi.id="RN68is2j9X47" namespace="ZJjfeyODnhwR" isSpecification="false" isRoot="false" isAbstract="false" name="Player" isLeaf="false">
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Package visibility="public" stereotype="folder" xmi.id="FLcFLmuIIl0X" namespace="ZJjfeyODnhwR" isSpecification="false" isRoot="false" isAbstract="false" name="Engine" isLeaf="false">
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Package visibility="public" stereotype="folder" xmi.id="WuodlBgQqpaC" namespace="ZJjfeyODnhwR" isSpecification="false" isRoot="false" isAbstract="false" name="CmdHandling" isLeaf="false">
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
<UML:Namespace.ownedElement>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Interface visibility="public" stereotype="interface" xmi.id="ffBANXOivrtb" namespace="WuodlBgQqpaC" isSpecification="false" isRoot="false" isAbstract="true" name="Command" isLeaf="false"/>
<UML:Class visibility="public" xmi.id="LwsGnjqnd7vk" namespace="WuodlBgQqpaC" isSpecification="false" isRoot="false" isAbstract="false" name="CmdRegistry" isLeaf="false"/>
<UML:Class visibility="public" xmi.id="BKW095CS12jp" namespace="WuodlBgQqpaC" isSpecification="false" isRoot="false" isAbstract="false" name="CmdInstanceMgr" isLeaf="false"/>
<UML:Class visibility="public" xmi.id="YBj1EISaTOYT" namespace="WuodlBgQqpaC" isSpecification="false" isRoot="false" isAbstract="false" name="CmdID" isLeaf="false"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</UML:Namespace.ownedElement>
</UML:Package>
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Package visibility="public" stereotype="folder" xmi.id="nCXlkkbOjNnt" namespace="Logical View" isSpecification="false" isRoot="false" isAbstract="false" name="Backend" isLeaf="false">
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Package visibility="public" stereotype="folder" xmi.id="ZBWVrIDGeIPK" namespace="nCXlkkbOjNnt" isSpecification="false" isRoot="false" isAbstract="false" name="Scheduler" isLeaf="false">
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:Namespace.ownedElement>
</UML:Package>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Generalization discriminator="" visibility="public" child="YML3K4y9h5tE" xmi.id="cz4YZYaRa9pv" namespace="Logical View" parent="zt9QqECndhuG" isSpecification="false" name=""/>
<UML:Generalization discriminator="" visibility="public" child="zt9QqECndhuG" xmi.id="iWjGfYBc3xqk" namespace="Logical View" parent="zQV7dGUdKiTL" isSpecification="false" name=""/>
<UML:Generalization discriminator="" visibility="public" child="TxRGe5zBPLEk" xmi.id="XrxbmnLBD6Pa" namespace="Logical View" parent="QTe1L5jo295e" isSpecification="false" name=""/>
<UML:Association visibility="public" xmi.id="TdTehsF1A2Mv" namespace="Logical View" isSpecification="false" name="">
<UML:Association.connection>
<UML:AssociationEnd visibility="public" type="r2bQMphsIClM" isNavigable="true" xmi.id="IZr82ligvi36" aggregation="composite" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="YML3K4y9h5tE" isNavigable="true" xmi.id="PoovU8DvjgaQ" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
</UML:Association.connection>
</UML:Association>
<UML:Association visibility="public" stereotype="owns" xmi.id="cppIrtav4tqC" namespace="Logical View" isSpecification="false" name="">
<UML:Association.connection>
<UML:AssociationEnd visibility="public" type="YML3K4y9h5tE" isNavigable="false" xmi.id="82LWUGfiM5b3" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="TxRGe5zBPLEk" isNavigable="true" xmi.id="Ts9OiwCIk1YZ" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
</UML:Association.connection>
</UML:Association>
<UML:Association visibility="public" xmi.id="u8UxzI77LQbn" namespace="Logical View" isSpecification="false" name="">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<UML:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="TxRGe5zBPLEk" isNavigable="false" xmi.id="gFV0K44ovBCd" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="04Gq3mqRDSTZ" isNavigable="true" xmi.id="7MupOSPGZtBY" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</UML:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Generalization discriminator="" visibility="public" child="CIgVjFGNUjOp" xmi.id="iwOwLnrzR97o" namespace="Logical View" parent="zQV7dGUdKiTL" isSpecification="false" name=""/>
<UML:Association visibility="public" xmi.id="qcxqdq4Dj7nA" namespace="Logical View" isSpecification="false" name="">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<UML:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="zQV7dGUdKiTL" isNavigable="false" xmi.id="TMTVpmdFeWnX" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="YVUu5DY24gSv" isNavigable="true" xmi.id="JLE0jvtZXoOB" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</UML:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Generalization discriminator="" visibility="public" child="r2bQMphsIClM" xmi.id="9NfcZGrNO8qZ" namespace="Logical View" parent="zt9QqECndhuG" isSpecification="false" name=""/>
<UML:Association visibility="public" xmi.id="ofNcGNdOluKC" namespace="Logical View" isSpecification="false" name="">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<UML:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="8QIySCNjv8Nm" isNavigable="true" xmi.id="4iv0qGkYq8Cg" aggregation="aggregate" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="TxRGe5zBPLEk" isNavigable="true" xmi.id="IU9TJbJ5EghU" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</UML:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Association visibility="public" xmi.id="2JrlBBvDtoBi" namespace="Logical View" isSpecification="false" name="">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<UML:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="r2bQMphsIClM" isNavigable="false" xmi.id="5wGt4QZKuilB" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="IlnerbEbwJog" isNavigable="true" xmi.id="H3GVhvyhCpTN" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</UML:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Association visibility="public" xmi.id="0ObsBkaGgo9i" namespace="Logical View" isSpecification="false" name="">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<UML:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="r2bQMphsIClM" isNavigable="false" xmi.id="Eg28NmJcnX8U" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="8QIySCNjv8Nm" isNavigable="true" xmi.id="S6Cftf0t1ZjA" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</UML:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Abstraction visibility="public" client="r2bQMphsIClM" xmi.id="Tw2630Yx9gph" namespace="Logical View" isSpecification="false" supplier="wB7sY2nRjOXn" name=""/>
<UML:Abstraction visibility="public" client="YML3K4y9h5tE" xmi.id="Sk9bQzG6aNWX" namespace="Logical View" isSpecification="false" supplier="wB7sY2nRjOXn" name=""/>
<UML:Dependency visibility="public" client="1l72I7ToPys3" xmi.id="62hs6uTYehTp" namespace="Logical View" isSpecification="false" supplier="wB7sY2nRjOXn" name="invokes"/>
<UML:Dependency visibility="public" client="wB7sY2nRjOXn" xmi.id="yABcqeRWgUdK" namespace="Logical View" isSpecification="false" supplier="WIX6g3bhkPMX" name="triggers recursive"/>
<UML:Abstraction visibility="public" client="rUnjINDv0ZKK" xmi.id="vqNvRLucgl3c" namespace="Logical View" isSpecification="false" supplier="GkMAyqUK0GFO" name=""/>
<UML:Abstraction visibility="public" client="dfMQKri4XPmn" xmi.id="Jn8ZrYJCuWdu" namespace="Logical View" isSpecification="false" supplier="MAnxOpF9GaE3" name=""/>
<UML:Abstraction visibility="public" client="mPYman5InEvb" xmi.id="UNNmnUMGfGd5" namespace="Logical View" isSpecification="false" supplier="i28J9X534hZ9" name=""/>
<UML:Abstraction visibility="public" client="k29coo6WqCqy" xmi.id="2ZLhpznz5WwR" namespace="Logical View" isSpecification="false" supplier="vXeW5rShP4KV" name=""/>
<UML:Association visibility="public" xmi.id="7B8Ch3bX8MJP" namespace="Logical View" isSpecification="false" name="">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<UML:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="i28J9X534hZ9" isNavigable="false" xmi.id="vk34CyDa4mJi" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="vXeW5rShP4KV" isNavigable="true" xmi.id="Z8PvGn4NwBXb" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</UML:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Association visibility="public" xmi.id="C89KUQhNBiSL" namespace="Logical View" isSpecification="false" name="">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<UML:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="mPYman5InEvb" isNavigable="false" xmi.id="fdvhPFQwLprb" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="k29coo6WqCqy" isNavigable="true" xmi.id="auwW3T7DZEX4" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</UML:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Association visibility="public" xmi.id="fCPqup9XS4Fq" namespace="Logical View" isSpecification="false" name="">
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:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="mPYman5InEvb" isNavigable="false" xmi.id="HfmaSc92W5WX" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="SDesIUWO0dz1" isNavigable="true" xmi.id="Wdk6sF8VRVLJ" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
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:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Association visibility="public" xmi.id="LSrnW4bmjOM9" namespace="Logical View" isSpecification="false" name="">
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:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="dfMQKri4XPmn" isNavigable="false" xmi.id="0U9UZf14Gj88" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="lSL6pzQhTDOj" isNavigable="true" xmi.id="yGdNjwe4MTqr" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
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:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Association visibility="public" xmi.id="XRdEpxNnRWHz" namespace="Logical View" isSpecification="false" name="PImpl">
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:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="kihkGgfmWK0o" isNavigable="false" xmi.id="BG1Sz9YxNAI6" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="dfMQKri4XPmn" isNavigable="true" xmi.id="4xBRQzIyQtCE" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
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:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Association visibility="public" xmi.id="oa1E4HBEXCgX" namespace="Logical View" isSpecification="false" name="use">
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:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="rUnjINDv0ZKK" isNavigable="false" xmi.id="JCSgKjmNgvo6" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="MAnxOpF9GaE3" isNavigable="true" xmi.id="s42HvFVjnUvr" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
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:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Dependency visibility="public" client="YsfFJxnCRFW9" xmi.id="l65HIjmbuCFE" namespace="Logical View" isSpecification="false" supplier="kihkGgfmWK0o" name="start/stop"/>
<UML:Dependency visibility="public" client="SDesIUWO0dz1" xmi.id="JlsDx7Pt5zUz" namespace="Logical View" isSpecification="false" supplier="kihkGgfmWK0o" name="controls"/>
<UML:Association visibility="public" xmi.id="GUZLT1InA1V1" namespace="Logical View" isSpecification="false" name="">
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:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="AAXrURgiB2s9" isNavigable="false" xmi.id="nYl3YGKWFIUs" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="GkMAyqUK0GFO" isNavigable="true" xmi.id="Gllytqe7KBRn" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
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:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Dependency visibility="public" client="ffBANXOivrtb" xmi.id="131GBLpjWYii" namespace="Logical View" isSpecification="false" supplier="LwsGnjqnd7vk" name=""/>
<UML:Dependency visibility="public" client="BKW095CS12jp" xmi.id="pntLJb28mLPJ" namespace="Logical View" isSpecification="false" supplier="LwsGnjqnd7vk" name=""/>
<UML:Abstraction visibility="public" client="SgmkxaeiRNDo" xmi.id="K0M4JkLSqfnX" namespace="Logical View" isSpecification="false" supplier="lqjWPWP1VmdU" name=""/>
<UML:Association visibility="public" xmi.id="GeC6HxeWEWcE" namespace="Logical View" isSpecification="false" name="">
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:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="ezNd14Qkbz9H" isNavigable="false" xmi.id="GEvK5ID5Ui3P" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="lqjWPWP1VmdU" isNavigable="true" xmi.id="ADebjvL0ZV6p" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
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:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Dependency visibility="public" client="BKW095CS12jp" xmi.id="SiLfEvrSAmlF" namespace="Logical View" isSpecification="false" supplier="YBj1EISaTOYT" name=""/>
<UML:Dependency visibility="public" client="rUnjINDv0ZKK" xmi.id="56iDqTQsNiNz" namespace="Logical View" isSpecification="false" supplier="BKW095CS12jp" name=""/>
<UML:Dependency visibility="public" client="lqjWPWP1VmdU" xmi.id="klZ7Tu7V9r4s" namespace="Logical View" isSpecification="false" supplier="rUnjINDv0ZKK" name=""/>
<UML:Association visibility="public" xmi.id="uUM1LQrJHt3A" namespace="Logical View" isSpecification="false" name="">
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:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="SgmkxaeiRNDo" isNavigable="true" xmi.id="4kODv0QtDmgk" aggregation="composite" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="ODwy08rSmbAj" isNavigable="true" xmi.id="S70s9Nj1r52A" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
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:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Dependency visibility="public" client="BKW095CS12jp" xmi.id="FR1SDfBdm9Tt" namespace="Logical View" isSpecification="false" supplier="kihkGgfmWK0o" name=""/>
<UML:Dependency visibility="public" client="CIgVjFGNUjOp" xmi.id="CPS2Rbf98EXg" namespace="Logical View" isSpecification="false" supplier="ODwy08rSmbAj" name=""/>
<UML:Association visibility="public" xmi.id="tYJprkh5eRGh" namespace="Logical View" isSpecification="false" name="">
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
<UML:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="CIgVjFGNUjOp" isNavigable="false" xmi.id="HaMY0Xea8njY" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="YVUu5DY24gSv" isNavigable="true" xmi.id="yrNo6hYxDrk5" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</UML:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Dependency visibility="public" client="CIgVjFGNUjOp" xmi.id="RHEp4K71H2nJ" namespace="Logical View" isSpecification="false" supplier="YBj1EISaTOYT" name="use"/>
<UML:Association visibility="public" xmi.id="usnAUyz41e5Tg" namespace="Logical View" isSpecification="false" name="">
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
<UML:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="ezNd14Qkbz9H" isNavigable="false" xmi.id="ug7uyHiAkfNp0" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="uanDLLZ8VytjK" isNavigable="true" xmi.id="uIpc6F9KgNqKc" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</UML:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Association visibility="public" xmi.id="uobpVxFZ0DLRF" namespace="Logical View" isSpecification="false" name="">
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
<UML:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="uanDLLZ8VytjK" isNavigable="true" xmi.id="uXN36S4GHeSuo" aggregation="composite" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="SgmkxaeiRNDo" isNavigable="true" xmi.id="uvK1eeFxWN0Z7" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
</UML:Association.connection>
</UML:Association>
<UML:Generalization discriminator="" visibility="public" child="uVhgPcx3vVYia" xmi.id="uDxR5SQ0wY8cN" namespace="Logical View" parent="SgmkxaeiRNDo" isSpecification="false" name=""/>
<UML:Dependency visibility="public" client="lqjWPWP1VmdU" xmi.id="utRdfDOABT6Rz" namespace="Logical View" isSpecification="false" supplier="uanDLLZ8VytjK" name="query"/>
<UML:Dependency visibility="public" client="lqjWPWP1VmdU" xmi.id="uJB2myhC1s4DV" namespace="Logical View" isSpecification="false" supplier="SgmkxaeiRNDo" name="builder"/>
<UML:Dependency visibility="public" client="CIgVjFGNUjOp" xmi.id="uppVyRsivnnGN" namespace="Logical View" isSpecification="false" supplier="lqjWPWP1VmdU" name="Binding"/>
<UML:Dependency visibility="public" client="uVhgPcx3vVYia" xmi.id="uYMOyqsVvZC7K" namespace="Logical View" isSpecification="false" supplier="urSQTv4G8xNl1" name="invoke"/>
<UML:Association visibility="public" xmi.id="udAqyhpmsg75a" namespace="Logical View" isSpecification="false" name="">
<UML:Association.connection>
<UML:AssociationEnd visibility="public" type="urSQTv4G8xNl1" isNavigable="false" xmi.id="upFPvuJOlEKKJ" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="CIgVjFGNUjOp" isNavigable="true" xmi.id="uE0yDjacfM9qj" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<diagram zoom="100" backgroundcolor="#ffffff" isopen="1" xmi.id="IIIwYfFi2Hzy" fillcolor="#ffffc0" linewidth="0" showpackage="1" showscope="1" snapgrid="1" usefillcolor="1" showattribassocs="1" localid="-1" textcolor="#000000" showattsig="1" griddotcolor="#d3d3d3" showstereotype="1" type="1" snapx="10" documentation="" canvasheight="360" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" showops="1" showopsig="1" canvaswidth="510" showatts="1" snapy="10" snapcsgrid="1" showgrid="1" name="clip_display">
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<widgets>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<classwidget usesdiagramusefillcolor="0" width="100" showoperations="1" xmi.id="YML3K4y9h5tE" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-260" usefillcolor="1" localid="h5idAOxedsSi" textcolor="#000000" showattributes="1" isinstance="0" x="-570" showstereotype="1" height="30" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="90" showoperations="1" xmi.id="TxRGe5zBPLEk" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-210" usefillcolor="1" localid="NAt4DnJss1W0" textcolor="#000000" showattributes="1" isinstance="0" x="-430" showstereotype="1" height="30" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="80" showoperations="1" xmi.id="QTe1L5jo295e" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-310" usefillcolor="1" localid="E2pbN1LiAFnN" textcolor="#000000" showattributes="1" isinstance="0" x="-430" showstereotype="1" height="30" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="90" showoperations="1" xmi.id="04Gq3mqRDSTZ" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-190" usefillcolor="1" localid="VALXJQAVRx5o" textcolor="#000000" showattributes="1" isinstance="0" x="-300" showstereotype="1" height="30" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="70" showoperations="1" xmi.id="zQV7dGUdKiTL" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-470" usefillcolor="1" localid="UHniiEFDOajg" textcolor="#000000" showattributes="1" isinstance="0" x="-620" showstereotype="1" height="30" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="80" showoperations="1" xmi.id="zt9QqECndhuG" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-380" usefillcolor="1" localid="xNsF5JZaZKGH" textcolor="#000000" showattributes="1" isinstance="0" x="-620" showstereotype="1" height="30" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="70" showoperations="1" xmi.id="YVUu5DY24gSv" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-450" usefillcolor="1" localid="sfgVKbkGyaV3" textcolor="#000000" showattributes="1" isinstance="0" x="-530" showstereotype="1" height="30" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="110" showoperations="1" xmi.id="r2bQMphsIClM" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-280" usefillcolor="1" localid="NHOSxrLoU1Ho" textcolor="#000000" showattributes="1" isinstance="0" x="-720" showstereotype="1" height="30" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="130" showoperations="1" xmi.id="IlnerbEbwJog" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-140" usefillcolor="1" localid="e1XxgzDXqd01" textcolor="#000000" showattributes="1" isinstance="0" x="-700" showstereotype="1" height="30" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="130" showoperations="1" xmi.id="8QIySCNjv8Nm" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-140" usefillcolor="1" localid="jZNeqAKUBpSs" textcolor="#000000" showattributes="1" isinstance="0" x="-520" showstereotype="1" height="30" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" showattsigs="601" usesdiagramfillcolor="0" showopsigs="601" autoresize="1"/>
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="YML3K4y9h5tE" xmi.id="cz4YZYaRa9pv" fillcolor="#ffff00" totalcounta="2" widgetbid="zt9QqECndhuG" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="500" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
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">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-520" starty="-260"/>
<endpoint endx="-590.503" endy="-350"/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<point x="-520" y="-300"/>
Tooling: Upgrade to Umbrello 4.17 (UML drawing tool) ..just open the existing uml/Lumiera.xmi and store it again
2021-04-16 15:50:22 +02:00
<point x="-590.503" y="-300.559"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="zt9QqECndhuG" xmi.id="iWjGfYBc3xqk" fillcolor="#ffff00" totalcounta="2" widgetbid="zQV7dGUdKiTL" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="500" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
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">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02: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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="TxRGe5zBPLEk" xmi.id="XrxbmnLBD6Pa" fillcolor="#ffff00" totalcounta="2" widgetbid="QTe1L5jo295e" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="500" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
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">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-400" starty="-210"/>
<endpoint endx="-400" endy="-280"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="r2bQMphsIClM" xmi.id="TdTehsF1A2Mv" fillcolor="#ffff00" totalcounta="2" widgetbid="YML3K4y9h5tE" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="510" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
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">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-610" starty="-250"/>
<endpoint endx="-570" endy="-250"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="YML3K4y9h5tE" xmi.id="cppIrtav4tqC" fillcolor="#ffff00" totalcounta="2" widgetbid="TxRGe5zBPLEk" linewidth="0" indexb="1" usefillcolor="1" textcolor="#000000" indexa="1" type="512" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
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">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-482" starty="-230"/>
<endpoint endx="-430" endy="-201"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
<point x="-482" y="-201"/>
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="TxRGe5zBPLEk" xmi.id="u8UxzI77LQbn" fillcolor="#ffff00" totalcounta="2" widgetbid="04Gq3mqRDSTZ" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="512" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
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">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-340" starty="-180"/>
<endpoint endx="-300" endy="-180"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="zQV7dGUdKiTL" xmi.id="qcxqdq4Dj7nA" fillcolor="#ffff00" totalcounta="2" widgetbid="YVUu5DY24gSv" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="512" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
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">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-550" starty="-440"/>
<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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="r2bQMphsIClM" xmi.id="9NfcZGrNO8qZ" fillcolor="#ffff00" totalcounta="2" widgetbid="zt9QqECndhuG" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="500" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
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">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-670.391" starty="-280"/>
<endpoint endx="-590.503" endy="-350"/>
Tooling: Upgrade to Umbrello 4.17 (UML drawing tool) ..just open the existing uml/Lumiera.xmi and store it again
2021-04-16 15:50:22 +02:00
<point x="-670.391" y="-300"/>
<point x="-590.503" 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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="8QIySCNjv8Nm" xmi.id="ofNcGNdOluKC" fillcolor="#ffff00" totalcounta="2" widgetbid="TxRGe5zBPLEk" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="501" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
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">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-420" starty="-140"/>
<endpoint endx="-420" endy="-180"/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="r2bQMphsIClM" xmi.id="2JrlBBvDtoBi" fillcolor="#ffff00" totalcounta="2" widgetbid="IlnerbEbwJog" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="512" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-640.136" starty="-250"/>
<endpoint endx="-640.136" endy="-140"/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="r2bQMphsIClM" xmi.id="0ObsBkaGgo9i" fillcolor="none" totalcounta="2" widgetbid="8QIySCNjv8Nm" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="512" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="1" autoresize="1">
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-640" starty="-250"/>
<endpoint endx="-520" endy="-140"/>
(cont) analysis of timeline display control
2016-11-28 03:41:25 +01:00
<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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<diagram zoom="110" backgroundcolor="#ffffff" isopen="1" xmi.id="C5tERlQ98tP3" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" snapgrid="1" usefillcolor="1" showattribassocs="1" localid="-1" textcolor="#000000" showattsig="1" griddotcolor="#d3d3d3" showstereotype="1" type="1" snapx="5" documentation="" canvasheight="330.88" showpubliconly="1" font="DejaVu Sans,8,-1,5,50,2,0,0,0,0,Oblique" linecolor="#3e0f00" showops="0" showopsig="0" canvaswidth="567.152" showatts="1" snapy="5" snapcsgrid="0" showgrid="1" name="CommandAccess">
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
<widgets>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<floatingtext usesdiagramusefillcolor="0" text="GUI" posttext="" width="28" xmi.id="wpmINPF0EHuA" fillcolor="#ffffc0" linewidth="0" pretext="" y="-135" usefillcolor="1" localid="U5feokOwe3sT" textcolor="#000000" isinstance="0" x="-640" showstereotype="1" height="17" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" role="700" usesdiagramfillcolor="0" autoresize="1"/>
<floatingtext usesdiagramusefillcolor="0" text="Steam-Layer" posttext="" width="78" xmi.id="kZZOaRpWFbmc" fillcolor="#ffffc0" linewidth="0" pretext="" y="-145" usefillcolor="1" localid="iL564mOWs2Ae" textcolor="#000000" isinstance="0" x="-500" showstereotype="1" height="17" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" role="700" usesdiagramfillcolor="0" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="95.0087" showoperations="0" xmi.id="uanDLLZ8VytjK" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-395" usefillcolor="1" localid="urcmTpA9pLOAD" textcolor="#000000" showattributes="1" isinstance="0" x="-800" showstereotype="1" height="25.4017" showpubliconly="1" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="600" autoresize="0"/>
<interfacewidget usesdiagramusefillcolor="0" width="81" showoperations="0" drawascircle="0" xmi.id="ffBANXOivrtb" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-295" usefillcolor="1" localid="0tJA7BrIGlUf" textcolor="#000000" showattributes="0" isinstance="0" x="-415" showstereotype="1" height="32" showpubliconly="0" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="600" autoresize="0"/>
<classwidget usesdiagramusefillcolor="0" width="90" showoperations="0" xmi.id="LwsGnjqnd7vk" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-230" usefillcolor="1" localid="In0YYUD2M0f8" textcolor="#000000" showattributes="1" isinstance="0" x="-380" showstereotype="1" height="25.7056" showpubliconly="1" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="600" autoresize="0"/>
<boxwidget textcolor="#000000" usefillcolor="1" height="330.88" isinstance="0" linewidth="0" xmi.id="1xInunMN9l4m" fillcolor="#ffffc0" linecolor="#000000" autoresize="0" x="-845" y="-440" width="245.415" usesdiagramfillcolor="0" showstereotype="1" localid="YRcJa6C6G7RY" usesdiagramusefillcolor="0" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique"/>
<boxwidget textcolor="#000000" usefillcolor="1" height="214.364" isinstance="0" linewidth="0" xmi.id="dr3uwTSvOjjI" fillcolor="#ffffc0" linecolor="#000000" autoresize="1" x="-520" y="-325" width="242.152" usesdiagramfillcolor="0" showstereotype="1" localid="8weypvxLMZex" usesdiagramusefillcolor="0" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique"/>
<classwidget usesdiagramusefillcolor="0" width="116" showoperations="0" xmi.id="BKW095CS12jp" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-230" usefillcolor="1" localid="lZaOgU7wH7Un" textcolor="#000000" showattributes="1" isinstance="0" x="-510" showstereotype="1" height="25" showpubliconly="1" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="600" autoresize="0"/>
<classwidget usesdiagramusefillcolor="0" width="175.064" showoperations="0" xmi.id="rUnjINDv0ZKK" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-180" usefillcolor="1" localid="afpwfT2pnZpu" textcolor="#000000" showattributes="1" isinstance="0" x="-600" showstereotype="1" height="25" showpubliconly="1" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="600" autoresize="0"/>
<classwidget usesdiagramusefillcolor="0" width="130" showoperations="0" xmi.id="ezNd14Qkbz9H" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-430" usefillcolor="1" localid="TEBiJfVtIIow" textcolor="#000000" showattributes="1" isinstance="0" x="-835" showstereotype="1" height="25.4053" showpubliconly="1" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="600" autoresize="0"/>
<interfacewidget usesdiagramusefillcolor="0" width="87" showoperations="0" drawascircle="0" xmi.id="lqjWPWP1VmdU" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-310" usefillcolor="1" localid="o3EP2LeTZpBt" textcolor="#000000" showattributes="0" isinstance="0" x="-825" showstereotype="1" height="32" showpubliconly="0" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="600" autoresize="0"/>
<classwidget usesdiagramusefillcolor="0" width="115.149" showoperations="0" drawascircle="0" xmi.id="SgmkxaeiRNDo" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-360" usefillcolor="1" localid="tcoMMRqAS3ZT" textcolor="#000000" showattributes="1" isinstance="0" x="-725" showstereotype="1" height="30.9079" showpubliconly="1" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="600" autoresize="0"/>
<classwidget usesdiagramusefillcolor="0" width="45" showoperations="0" xmi.id="YBj1EISaTOYT" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-220" usefillcolor="1" localid="UNvHz309qQi1" textcolor="#000000" showattributes="1" isinstance="0" x="-585" showstereotype="1" height="18" showpubliconly="1" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="600" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="120.772" showoperations="0" xmi.id="kihkGgfmWK0o" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-180" usefillcolor="1" localid="WtUlnXtpFH2A" textcolor="#000000" showattributes="1" isinstance="0" x="-410" showstereotype="1" height="50.0821" showpubliconly="1" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="600" autoresize="0"/>
<classwidget usesdiagramusefillcolor="0" width="48" showoperations="0" xmi.id="CIgVjFGNUjOp" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-220" usefillcolor="1" localid="00cEHXMxsQ3w" textcolor="#000000" showattributes="1" isinstance="0" x="-820" showstereotype="1" height="18" showpubliconly="1" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="600" autoresize="1"/>
<classwidget usesdiagramusefillcolor="0" width="65.607" showoperations="0" xmi.id="YVUu5DY24gSv" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-180" usefillcolor="1" localid="cb8BRB7rsFMm" textcolor="#000000" showattributes="1" isinstance="0" x="-765" showstereotype="1" height="25" showpubliconly="1" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="600" autoresize="0"/>
<interfacewidget usesdiagramusefillcolor="0" width="90.3527" showoperations="0" drawascircle="0" xmi.id="PHufJfyMo4sv" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-180" usefillcolor="1" localid="C4mf3nZwKe6H" textcolor="#000000" showattributes="0" isinstance="0" x="-690" showstereotype="1" height="35.034" showpubliconly="0" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="none" showattsigs="601" usesdiagramfillcolor="0" showopsigs="600" autoresize="0"/>
<classwidget usesdiagramusefillcolor="0" width="115.248" showoperations="0" xmi.id="uVhgPcx3vVYia" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-310" usefillcolor="1" localid="u3dz367kCfz4H" textcolor="#000000" showattributes="1" isinstance="0" x="-725" showstereotype="1" height="30.8652" showpubliconly="1" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="600" autoresize="0"/>
<interfacewidget usesdiagramusefillcolor="0" width="81" showoperations="0" drawascircle="0" xmi.id="urSQTv4G8xNl1" fillcolor="#ffffc0" linewidth="0" showpackage="0" showscope="1" y="-260" usefillcolor="1" localid="uPpRiv12gNCGd" textcolor="#000000" showattributes="0" isinstance="0" x="-725" showstereotype="1" height="32" showpubliconly="0" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" showattsigs="601" usesdiagramfillcolor="0" showopsigs="600" autoresize="0"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</widgets>
<messages/>
<associations>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="uVhgPcx3vVYia" xmi.id="uYMOyqsVvZC7K" fillcolor="#ffff00" totalcounta="2" widgetbid="urSQTv4G8xNl1" linewidth="0" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="502" font="DejaVu Sans,8,-1,5,50,2,0,0,0,0,Oblique" linecolor="#3e0f00" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
<linepath layout="Polyline">
<startpoint startx="-705.021" starty="-279.135"/>
<endpoint endx="-705.021" endy="-260"/>
</linepath>
<floatingtext usesdiagramusefillcolor="1" text="invoke" posttext="" width="44" xmi.id="upDV9DGFoYtwZ" fillcolor="none" linewidth="0" pretext="" y="-280" usefillcolor="1" localid="u8HNUHckzqnv1" textcolor="none" isinstance="0" x="-705" showstereotype="1" height="17" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" role="703" usesdiagramfillcolor="1" autoresize="1"/>
</assocwidget>
<assocwidget usesdiagramusefillcolor="0" widgetaid="uanDLLZ8VytjK" xmi.id="uobpVxFZ0DLRF" fillcolor="#ffff00" totalcounta="2" widgetbid="SgmkxaeiRNDo" linewidth="0" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="510" font="DejaVu Sans,8,-1,5,50,2,0,0,0,0,Oblique" linecolor="#3e0f00" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
<linepath layout="Polyline">
<startpoint startx="-704.991" starty="-385.313"/>
<endpoint endx="-664.826" endy="-360"/>
<point x="-664.826" y="-385.313"/>
</linepath>
</assocwidget>
<assocwidget usesdiagramusefillcolor="0" widgetaid="ezNd14Qkbz9H" xmi.id="usnAUyz41e5Tg" fillcolor="#ffff00" totalcounta="2" widgetbid="uanDLLZ8VytjK" linewidth="0" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="512" font="DejaVu Sans,8,-1,5,50,2,0,0,0,0,Oblique" linecolor="#3e0f00" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
<linepath layout="Polyline">
<startpoint startx="-825.143" starty="-404.595"/>
<endpoint endx="-800" endy="-385.775"/>
<point x="-825.143" y="-385.775"/>
</linepath>
</assocwidget>
<assocwidget usesdiagramusefillcolor="0" widgetaid="ffBANXOivrtb" xmi.id="131GBLpjWYii" fillcolor="#ffff00" totalcounta="2" widgetbid="LwsGnjqnd7vk" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="502" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
<linepath layout="Polyline">
<startpoint startx="-375" starty="-263"/>
<endpoint endx="-375" endy="-230"/>
</linepath>
</assocwidget>
<assocwidget usesdiagramusefillcolor="1" widgetaid="BKW095CS12jp" xmi.id="pntLJb28mLPJ" fillcolor="#ffff00" totalcounta="2" widgetbid="LwsGnjqnd7vk" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="502" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
<linepath layout="Polyline">
<startpoint startx="-394" starty="-207.115"/>
<endpoint endx="-380" endy="-207.115"/>
</linepath>
</assocwidget>
<assocwidget usesdiagramusefillcolor="1" widgetaid="BKW095CS12jp" xmi.id="SiLfEvrSAmlF" fillcolor="none" totalcounta="2" widgetbid="YBj1EISaTOYT" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="502" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="1" autoresize="1">
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-510" starty="-220"/>
<endpoint endx="-540" endy="-220"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="rUnjINDv0ZKK" xmi.id="56iDqTQsNiNz" fillcolor="#ffff00" totalcounta="2" widgetbid="BKW095CS12jp" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="502" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-495.256" starty="-180"/>
<endpoint endx="-495.256" endy="-205"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="BKW095CS12jp" xmi.id="FR1SDfBdm9Tt" fillcolor="#ffff00" totalcounta="2" widgetbid="kihkGgfmWK0o" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="502" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-395" starty="-205"/>
<endpoint endx="-395" endy="-180"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="CIgVjFGNUjOp" xmi.id="tYJprkh5eRGh" fillcolor="#ffff00" totalcounta="2" widgetbid="YVUu5DY24gSv" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="512" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-772" starty="-210.58"/>
<endpoint endx="-745.077" endy="-180"/>
<point x="-745.077" y="-210.58"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="CIgVjFGNUjOp" xmi.id="RHEp4K71H2nJ" fillcolor="#ffff00" totalcounta="2" widgetbid="YBj1EISaTOYT" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="502" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-772" starty="-220"/>
<endpoint endx="-585" endy="-220"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</linepath>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<floatingtext usesdiagramusefillcolor="1" text="use" posttext="" width="27" xmi.id="uQ9ZfNjKiafZI" fillcolor="none" linewidth="0" pretext="" y="-220" usefillcolor="1" localid="u3qCPlkkfgkTP" textcolor="none" isinstance="0" x="-740" showstereotype="1" height="17" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" role="703" usesdiagramfillcolor="1" autoresize="1"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="uVhgPcx3vVYia" xmi.id="uDxR5SQ0wY8cN" fillcolor="#ffff00" totalcounta="2" widgetbid="SgmkxaeiRNDo" linewidth="0" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="500" font="DejaVu Sans,8,-1,5,50,2,0,0,0,0,Oblique" linecolor="#3e0f00" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-664.955" starty="-310"/>
<endpoint endx="-664.955" endy="-329.092"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="lqjWPWP1VmdU" xmi.id="utRdfDOABT6Rz" fillcolor="#ffff00" totalcounta="2" widgetbid="uanDLLZ8VytjK" linewidth="0" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="502" font="DejaVu Sans,8,-1,5,50,2,0,0,0,0,Oblique" linecolor="#3e0f00" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-789.679" starty="-310"/>
<endpoint endx="-789.679" endy="-369.598"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</linepath>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<floatingtext usesdiagramusefillcolor="1" text="query" posttext="" width="40" xmi.id="uivjdt4KUcZRF" fillcolor="none" linewidth="0" pretext="" y="-365" usefillcolor="1" localid="uUvHcp5FwEmGW" textcolor="none" isinstance="0" x="-790" showstereotype="1" height="17" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" role="703" usesdiagramfillcolor="1" autoresize="1"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="CIgVjFGNUjOp" xmi.id="uppVyRsivnnGN" fillcolor="none" totalcounta="2" widgetbid="lqjWPWP1VmdU" linewidth="0" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="502" font="DejaVu Sans,8,-1,5,50,2,0,0,0,0,Oblique" linecolor="#3e0f00" totalcountb="2" seqnum="" usesdiagramfillcolor="1" autoresize="1">
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-810.018" starty="-220"/>
<endpoint endx="-810.018" endy="-278"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</linepath>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<floatingtext usesdiagramusefillcolor="1" text="Binding" posttext="" width="50" xmi.id="u8LWcTEcewhW5" fillcolor="none" linewidth="0" pretext="" y="-270" usefillcolor="1" localid="uidPwt8MxgebD" textcolor="none" isinstance="0" x="-830" showstereotype="1" height="17" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" role="703" usesdiagramfillcolor="1" autoresize="1"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="lqjWPWP1VmdU" xmi.id="uJB2myhC1s4DV" fillcolor="#ffff00" totalcounta="2" widgetbid="SgmkxaeiRNDo" linewidth="0" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="502" font="DejaVu Sans,8,-1,5,50,2,0,0,0,0,Oblique" linecolor="#3e0f00" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-775.342" starty="-310"/>
<endpoint endx="-725" endy="-335.505"/>
<point x="-775.342" y="-335.505"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</linepath>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<floatingtext usesdiagramusefillcolor="1" text="builder" posttext="" width="46" xmi.id="uYq5iWoNRynil" fillcolor="none" linewidth="0" pretext="" y="-335" usefillcolor="1" localid="uPUHyzvon5t0Y" textcolor="none" isinstance="0" x="-775" showstereotype="1" height="17" font="DejaVu Sans,8,-1,5,50,0,0,0,0,0,Oblique" linecolor="#3e0f00" role="703" usesdiagramfillcolor="1" autoresize="1"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="1" widgetaid="urSQTv4G8xNl1" xmi.id="udAqyhpmsg75a" fillcolor="#ffff00" totalcounta="2" widgetbid="CIgVjFGNUjOp" linewidth="0" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="512" font="DejaVu Sans,8,-1,5,50,2,0,0,0,0,Oblique" linecolor="#3e0f00" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-725" starty="-249.811"/>
<endpoint endx="-780.004" endy="-220"/>
<point x="-780.004" y="-249.811"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</linepath>
</assocwidget>
</associations>
</diagram>
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
</diagrams>
</XMI.extension>
</UML:Model>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Model visibility="public" stereotype="folder" xmi.id="Use Case View" namespace="m1" isSpecification="false" isRoot="false" isAbstract="false" name="Use Case View" isLeaf="false">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<UML:Namespace.ownedElement>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Package visibility="public" stereotype="folder" xmi.id="f4aD2h2f9RdQ" namespace="Use Case View" isSpecification="false" isRoot="false" isAbstract="false" name="Command" isLeaf="false">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<UML:Namespace.ownedElement/>
</UML:Package>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Actor visibility="public" xmi.id="zlqyX5J6PSBr" namespace="Use Case View" isSpecification="false" isRoot="false" isAbstract="false" name="SessionStart" isLeaf="false"/>
<UML:Actor visibility="public" xmi.id="YaYgpwDph1lD" namespace="Use Case View" isSpecification="false" isRoot="false" isAbstract="false" name="GlobalAction" isLeaf="false"/>
<UML:Actor visibility="public" xmi.id="bdUD2bZY97Fy" namespace="Use Case View" isSpecification="false" isRoot="false" isAbstract="false" name="Widget" isLeaf="false"/>
<UML:Actor visibility="public" xmi.id="eFcxWJO7utJx" namespace="Use Case View" isSpecification="false" isRoot="false" isAbstract="false" name="InteractionStateManager" isLeaf="false"/>
<UML:UseCase visibility="public" xmi.id="pY2KizGMCrHj" namespace="Use Case View" isSpecification="false" isRoot="false" isAbstract="false" name="define command" isLeaf="false"/>
<UML:UseCase visibility="public" xmi.id="99tISYqG4qam" namespace="Use Case View" isSpecification="false" isRoot="false" isAbstract="false" name="issue command" isLeaf="false"/>
<UML:UseCase visibility="public" xmi.id="fpYdG6ZODQgg" namespace="Use Case View" isSpecification="false" isRoot="false" isAbstract="false" name="find subject" isLeaf="false"/>
<UML:UseCase visibility="public" xmi.id="GrjGOZp3PLgd" namespace="Use Case View" isSpecification="false" isRoot="false" isAbstract="false" name="retrieve param" isLeaf="false"/>
<UML:UseCase visibility="public" xmi.id="cNavFgpTXYjv" namespace="Use Case View" isSpecification="false" isRoot="false" isAbstract="false" name="note change" isLeaf="false"/>
<UML:Association visibility="public" xmi.id="YswNymmhvlaD" namespace="Use Case View" isSpecification="false" name="">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<UML:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="YaYgpwDph1lD" isNavigable="true" xmi.id="Kt7GkuNHWzJe" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="fpYdG6ZODQgg" isNavigable="true" xmi.id="IJv7DgllWh6U" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</UML:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Association visibility="public" xmi.id="UsCNekYycfDK" namespace="Use Case View" isSpecification="false" name="">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<UML:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="YaYgpwDph1lD" isNavigable="true" xmi.id="XYa1YtgoAbuO" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="99tISYqG4qam" isNavigable="true" xmi.id="Ff7mLEEn6QAk" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</UML:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Association visibility="public" xmi.id="9jhjMs3uQdtw" namespace="Use Case View" isSpecification="false" name="">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<UML:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="bdUD2bZY97Fy" isNavigable="true" xmi.id="XZlf8d3OGB8b" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="99tISYqG4qam" isNavigable="true" xmi.id="NMOTlXCuGtda" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</UML:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Association visibility="public" xmi.id="jeU9IO6nvpS2" namespace="Use Case View" isSpecification="false" name="">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<UML:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="bdUD2bZY97Fy" isNavigable="true" xmi.id="QUOgdWI0seTb" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="GrjGOZp3PLgd" isNavigable="true" xmi.id="BfVPW6yFlSN1" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</UML:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Association visibility="public" xmi.id="oToiGEkgg6MJ" namespace="Use Case View" isSpecification="false" name="">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<UML:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="eFcxWJO7utJx" isNavigable="true" xmi.id="ccJSFn4OQXmv" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="cNavFgpTXYjv" isNavigable="true" xmi.id="ek8NAVOxwAfC" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</UML:Association.connection>
</UML:Association>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Association visibility="public" xmi.id="MNq3TBM3lgVy" namespace="Use Case View" isSpecification="false" name="">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<UML:Association.connection>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:AssociationEnd visibility="public" type="zlqyX5J6PSBr" isNavigable="true" xmi.id="RXNp57kjrt4z" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
<UML:AssociationEnd visibility="public" type="pY2KizGMCrHj" isNavigable="true" xmi.id="MQwJaZTuuIxN" aggregation="none" isSpecification="false" name="" changeability="changeable"/>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</UML:Association.connection>
</UML:Association>
</UML:Namespace.ownedElement>
<XMI.extension xmi.extender="umbrello">
<diagrams>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<diagram zoom="100" backgroundcolor="#ffffff" isopen="1" xmi.id="Q1qEMiNK0mHL" fillcolor="#ffffc0" linewidth="0" showpackage="1" showscope="1" snapgrid="0" usefillcolor="1" showattribassocs="1" localid="-1" textcolor="#000000" showattsig="1" griddotcolor="#d3d3d3" showstereotype="1" type="2" snapx="25" documentation="" canvasheight="453" showpubliconly="1" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" showops="1" showopsig="1" canvaswidth="427" showatts="1" snapy="25" snapcsgrid="0" showgrid="0" name="CommandUsage">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<widgets>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<boxwidget textcolor="#000000" usefillcolor="1" height="377" isinstance="0" linewidth="0" xmi.id="wMW5l9TCAHOW" fillcolor="#ffffc0" linecolor="#000000" autoresize="1" x="-50" y="-375" width="277" usesdiagramfillcolor="0" showstereotype="1" localid="bJB4Uoi9qGKs" usesdiagramusefillcolor="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<actorwidget textcolor="#000000" usefillcolor="1" height="58" isinstance="0" linewidth="0" xmi.id="zlqyX5J6PSBr" fillcolor="#ffffc0" linecolor="#3e0f00" autoresize="1" x="133" y="-451" width="84" usesdiagramfillcolor="0" showstereotype="1" localid="Et047Kv3eR6O" usesdiagramusefillcolor="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<actorwidget textcolor="#000000" usefillcolor="1" height="58" isinstance="0" linewidth="0" xmi.id="YaYgpwDph1lD" fillcolor="#ffffc0" linecolor="#3e0f00" autoresize="1" x="-150" y="-350" width="80" usesdiagramfillcolor="0" showstereotype="1" localid="52JSSSJgLJiR" usesdiagramusefillcolor="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<actorwidget textcolor="#000000" usefillcolor="1" height="60.4681" isinstance="0" linewidth="0" xmi.id="bdUD2bZY97Fy" fillcolor="#ffffc0" linecolor="#3e0f00" autoresize="1" x="-136" y="-178" width="49" usesdiagramfillcolor="0" showstereotype="1" localid="1QlhRWuUWBww" usesdiagramusefillcolor="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<actorwidget textcolor="#000000" usefillcolor="1" height="59" isinstance="0" linewidth="0" xmi.id="eFcxWJO7utJx" fillcolor="#ffffc0" linecolor="#3e0f00" autoresize="1" x="-200" y="-75" width="149" usesdiagramfillcolor="0" showstereotype="1" localid="UsTbyiZz8LeY" usesdiagramusefillcolor="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<usecasewidget textcolor="#000000" usefillcolor="1" height="48" isinstance="0" linewidth="0" xmi.id="pY2KizGMCrHj" fillcolor="#ffffc0" linecolor="#3e0f00" autoresize="1" x="98" y="-249" width="115" usesdiagramfillcolor="0" showstereotype="1" localid="Agq4X7zzyTaw" usesdiagramusefillcolor="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<usecasewidget textcolor="#000000" usefillcolor="1" height="48" isinstance="0" linewidth="0" xmi.id="99tISYqG4qam" fillcolor="#ffffc0" linecolor="#3e0f00" autoresize="1" x="-25" y="-250" width="111" usesdiagramfillcolor="0" showstereotype="1" localid="po62fOln2ZsZ" usesdiagramusefillcolor="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<usecasewidget textcolor="#000000" usefillcolor="1" height="48" isinstance="0" linewidth="0" xmi.id="fpYdG6ZODQgg" fillcolor="#ffffc0" linecolor="#3e0f00" autoresize="1" x="-25" y="-350" width="85" usesdiagramfillcolor="0" showstereotype="1" localid="yUu1KUn8Is8w" usesdiagramusefillcolor="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<usecasewidget textcolor="#000000" usefillcolor="1" height="48" isinstance="0" linewidth="0" xmi.id="GrjGOZp3PLgd" fillcolor="#ffffc0" linecolor="#3e0f00" autoresize="1" x="-25" y="-150" width="104" usesdiagramfillcolor="0" showstereotype="1" localid="RD1ccfGa9AbS" usesdiagramusefillcolor="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<usecasewidget textcolor="#000000" usefillcolor="1" height="48" isinstance="0" linewidth="0" xmi.id="cNavFgpTXYjv" fillcolor="#ffffc0" linecolor="#3e0f00" autoresize="1" x="-25" y="-75" width="90" usesdiagramfillcolor="0" showstereotype="1" localid="8YzVrd6Gp6sR" usesdiagramusefillcolor="0" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0"/>
<floatingtext usesdiagramusefillcolor="0" text="core commands" posttext="" width="96" xmi.id="Xcc4ALzIrwlg" fillcolor="#ffffc0" linewidth="0" pretext="" y="-375" usefillcolor="1" localid="l9ztJZJuwtn9" textcolor="#000000" isinstance="0" x="25" showstereotype="1" height="17" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="#3e0f00" role="700" usesdiagramfillcolor="0" autoresize="1"/>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</widgets>
<messages/>
<associations>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="YaYgpwDph1lD" xmi.id="YswNymmhvlaD" fillcolor="#ffff00" totalcounta="2" widgetbid="fpYdG6ZODQgg" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="503" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-70" starty="-314"/>
<endpoint endx="-25" endy="-314"/>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="YaYgpwDph1lD" xmi.id="UsCNekYycfDK" fillcolor="#ffff00" totalcounta="2" widgetbid="99tISYqG4qam" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="503" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-70" starty="-292"/>
<endpoint endx="-25" endy="-250"/>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="bdUD2bZY97Fy" xmi.id="9jhjMs3uQdtw" fillcolor="#ffff00" totalcounta="2" widgetbid="99tISYqG4qam" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="503" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-87" starty="-178"/>
<endpoint endx="-25" endy="-202"/>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="bdUD2bZY97Fy" xmi.id="jeU9IO6nvpS2" fillcolor="#ffff00" totalcounta="2" widgetbid="GrjGOZp3PLgd" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="503" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-87" starty="-127"/>
<endpoint endx="-25" endy="-127"/>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="eFcxWJO7utJx" xmi.id="oToiGEkgg6MJ" fillcolor="#ffff00" totalcounta="2" widgetbid="cNavFgpTXYjv" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="503" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="0" autoresize="1">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="-51" starty="-29"/>
<endpoint endx="-25" endy="-29"/>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</linepath>
</assocwidget>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<assocwidget usesdiagramusefillcolor="0" widgetaid="zlqyX5J6PSBr" xmi.id="MNq3TBM3lgVy" fillcolor="none" totalcounta="2" widgetbid="pY2KizGMCrHj" linewidth="none" indexb="1" usefillcolor="1" textcolor="none" indexa="1" type="503" font="DejaVu Sans,8,-1,0,50,0,0,0,0,0" linecolor="none" totalcountb="2" seqnum="" usesdiagramfillcolor="1" autoresize="1">
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
<linepath layout="Polyline">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<startpoint startx="202" starty="-393"/>
<endpoint endx="202" endy="-249"/>
command-invocation: use case analysis
2017-03-03 23:59:22 +01:00
</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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Model visibility="public" stereotype="folder" xmi.id="Component View" namespace="m1" isSpecification="false" isRoot="false" isAbstract="false" name="Component View" isLeaf="false">
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:Model>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Model visibility="public" stereotype="folder" xmi.id="Deployment View" namespace="m1" isSpecification="false" isRoot="false" isAbstract="false" name="Deployment View" isLeaf="false">
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:Model>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<UML:Model visibility="public" stereotype="folder" xmi.id="Entity Relationship Model" namespace="m1" isSpecification="false" isRoot="false" isAbstract="false" name="Entity Relationship Model" isLeaf="false">
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:Model>
</UML:Namespace.ownedElement>
</UML:Model>
</XMI.content>
<XMI.extensions xmi.extender="umbrello">
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<docsettings documentation="" uniqueid="uO02JMu3f8NTV" viewid="C5tERlQ98tP3"/>
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<listitem type="800" open="1" id="Views">
<listitem type="802" open="1" id="Use Case View">
<listitem type="804" open="1" id="f4aD2h2f9RdQ">
<listitem type="805" open="0" id="Q1qEMiNK0mHL" label="CommandUsage"/>
Tooling: Upgrade to Umbrello 4.17 (UML drawing tool) ..just open the existing uml/Lumiera.xmi and store it again
2021-04-16 15:50:22 +02:00
</listitem>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<listitem type="812" open="1" id="pY2KizGMCrHj"/>
<listitem type="812" open="1" id="fpYdG6ZODQgg"/>
<listitem type="811" open="1" id="YaYgpwDph1lD"/>
<listitem type="811" open="1" id="eFcxWJO7utJx"/>
<listitem type="812" open="1" id="99tISYqG4qam"/>
<listitem type="812" open="1" id="cNavFgpTXYjv"/>
<listitem type="812" open="1" id="GrjGOZp3PLgd"/>
<listitem type="811" open="1" id="zlqyX5J6PSBr"/>
<listitem type="811" open="1" id="bdUD2bZY97Fy"/>
Tooling: Upgrade to Umbrello 4.17 (UML drawing tool) ..just open the existing uml/Lumiera.xmi and store it again
2021-04-16 15:50:22 +02:00
</listitem>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<listitem type="836" open="1" id="Entity Relationship Model"/>
<listitem type="821" open="1" id="Component View"/>
<listitem type="801" open="1" id="Logical View">
<listitem type="803" open="1" id="nCXlkkbOjNnt">
<listitem type="803" open="1" id="ZBWVrIDGeIPK"/>
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<listitem type="830" open="0" id="Datatypes">
<listitem type="829" open="1" id="c4Twqn0aUQB4"/>
<listitem type="829" open="1" id="15L0hJXhwcFR"/>
<listitem type="829" open="1" id="hGddsq3TsUPg"/>
<listitem type="829" open="1" id="aPBblD5kGQlv"/>
<listitem type="829" open="1" id="mhSdaAG81L4V"/>
<listitem type="829" open="1" id="83IMS1F7HsjA"/>
<listitem type="829" open="0" id="uWIJRjMnWEHh8"/>
<listitem type="829" open="0" id="uNqycOxR6x9BP"/>
<listitem type="829" open="1" id="pFknC1jVXUTk"/>
<listitem type="829" open="1" id="HOEjoPmPovyX"/>
<listitem type="829" open="0" id="uQjH8LmECcyqd"/>
<listitem type="829" open="0" id="uNC1udGnuzN2S"/>
<listitem type="829" open="0" id="ub2aLimnOvCc8"/>
<listitem type="829" open="0" id="uTDfsr4Knx3AZ"/>
<listitem type="829" open="0" id="ufJzUkPpx5QnH"/>
<listitem type="829" open="1" id="RoHoEUz0UZaO"/>
<listitem type="829" open="0" id="uMMCCegdWRMed"/>
<listitem type="829" open="1" id="gkbWE0CWOQFD"/>
<listitem type="829" open="1" id="Qc5iSoq7YRdn"/>
<listitem type="829" open="0" id="uIVzscMhthEou"/>
<listitem type="829" open="1" id="n1aawY72aPM0"/>
<listitem type="829" open="0" id="uI4uVfXWHwlj8"/>
<listitem type="829" open="0" id="unGP2JF0ACOa5"/>
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<listitem type="803" open="1" id="dzlPCiVfMhDw">
<listitem type="803" open="1" id="AP2Jw6O9SyPl">
<listitem type="813" open="0" id="YVUu5DY24gSv"/>
<listitem type="817" open="0" id="lqjWPWP1VmdU"/>
<listitem type="813" open="0" id="zt9QqECndhuG"/>
<listitem type="813" open="0" id="AAXrURgiB2s9"/>
<listitem type="813" open="0" id="uanDLLZ8VytjK"/>
<listitem type="813" open="0" id="ezNd14Qkbz9H"/>
<listitem type="813" open="0" id="SgmkxaeiRNDo"/>
<listitem type="813" open="0" id="ODwy08rSmbAj"/>
<listitem type="817" open="0" id="urSQTv4G8xNl1"/>
<listitem type="813" open="1" id="zQV7dGUdKiTL"/>
<listitem type="817" open="0" id="PHufJfyMo4sv"/>
<listitem type="813" open="0" id="CIgVjFGNUjOp"/>
<listitem type="813" open="0" id="uVhgPcx3vVYia"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</listitem>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<listitem type="807" open="0" id="C5tERlQ98tP3" label="CommandAccess"/>
<listitem type="818" open="0" id="50pVMRCQE3mT">
<listitem type="813" open="0" id="QTe1L5jo295e"/>
<listitem type="813" open="0" id="04Gq3mqRDSTZ"/>
more detailed planning of architecture for clip presentation ...first UML diagram created with Umbrello!
2016-11-20 03:06:50 +01:00
</listitem>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<listitem type="803" open="1" id="iJ1021VZA242">
<listitem type="807" open="0" id="IIIwYfFi2Hzy" label="clip_display"/>
<listitem type="813" open="0" id="YML3K4y9h5tE"/>
<listitem type="813" open="0" id="TxRGe5zBPLEk"/>
<listitem type="807" open="0" id="tyAwJXVRd8yU" label="display_evaluation"/>
<listitem type="813" open="0" id="WIX6g3bhkPMX">
<listitem type="815" open="0" id="SjGuD1cFQas5"/>
<listitem type="814" open="0" id="MAWVsNUcUWni"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</listitem>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<listitem type="817" open="1" id="1l72I7ToPys3">
<listitem type="815" open="0" id="87ehnyLmiQo0"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</listitem>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<listitem type="817" open="0" id="wB7sY2nRjOXn">
<listitem type="815" open="0" id="m71ADYgKdI1Q"/>
start with actual rework of the timeline display draft a concept for timeline layout management
2016-11-30 23:12:44 +01:00
</listitem>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<listitem type="813" open="0" id="8QIySCNjv8Nm"/>
<listitem type="813" open="0" id="IlnerbEbwJog"/>
<listitem type="813" open="0" 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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<listitem type="803" open="1" id="ZJjfeyODnhwR">
<listitem type="803" open="1" id="wYrkFnB1ygmi"/>
<listitem type="803" open="1" id="WuodlBgQqpaC">
<listitem type="813" open="0" id="YBj1EISaTOYT"/>
<listitem type="813" open="0" id="BKW095CS12jp"/>
<listitem type="813" open="1" id="LwsGnjqnd7vk"/>
<listitem type="817" open="0" id="ffBANXOivrtb"/>
more planning with respect to UI/Session command access (#1087)
2017-03-11 02:07:52 +01:00
</listitem>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<listitem type="803" open="1" id="FLcFLmuIIl0X"/>
<listitem type="803" open="1" id="RN68is2j9X47"/>
<listitem type="803" open="1" id="3HXNyiJX20Ae">
<listitem type="817" open="0" id="MAnxOpF9GaE3"/>
<listitem type="813" open="0" id="lSL6pzQhTDOj"/>
<listitem type="813" open="0" id="dfMQKri4XPmn"/>
<listitem type="813" open="1" id="SDesIUWO0dz1">
<listitem type="815" open="0" id="cv5AydHGTsoa"/>
<listitem type="815" open="0" id="KsbZ85POo9Lg"/>
<listitem type="815" open="0" id="zzlJ9A4Ksadb"/>
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<listitem type="817" open="0" id="vXeW5rShP4KV"/>
<listitem type="807" open="0" id="ZM3pbwOfd7Ql" label="session_subsystem"/>
<listitem type="817" open="0" id="GkMAyqUK0GFO"/>
<listitem type="813" open="0" id="rUnjINDv0ZKK"/>
<listitem type="813" open="0" id="k29coo6WqCqy"/>
<listitem type="813" open="0" id="YsfFJxnCRFW9"/>
<listitem type="817" open="0" id="i28J9X534hZ9">
<listitem type="815" open="0" id="6Y9d0aMtHa01"/>
<listitem type="815" open="0" id="tgE8kCyZfoMP"/>
<listitem type="815" open="0" id="pVqpkd56Npnb"/>
<listitem type="815" open="0" id="kyZPlvm8LFta"/>
<listitem type="815" open="0" id="PSTlFEK4S4pe"/>
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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<listitem type="813" open="0" id="mPYman5InEvb"/>
<listitem type="813" open="1" id="kihkGgfmWK0o">
<listitem type="815" open="0" id="RFgnI9xTKVIo"/>
<listitem type="814" open="0" id="wyW7zMFphhgG"/>
<listitem type="815" open="0" id="KsrSalZ00FnI"/>
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>
</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>
DOC: update and rework documentation regarding command access In 2017, I did a first design draft, followed by a design critique, which partially obsoleted some ideas regarding command binding. Mostly, the reason to abandon parts of that initial design was due to the fact, that to many actual construction details of the UI framework were not worked out at that time. Thus I rather focussed on (re)-building a backbone for the timeline display, in order to support that kind of flexibility aspired within the session model. Now, when re-visiting the topic of an UI gesture (using simple dragging of a clip in the timeline as an example for a first draft), I picked up some of those planned structures, but tend to bind them together in a slightly different way -- more akin to a state machine and less in the way of an LR-parser. This chagneset updates the relevant part within the TiddlyWiki and the corresponding UML drawing to better reflect my actual thinking.
2021-04-16 18:14:33 +02:00
<listitem type="827" open="1" id="Deployment View"/>
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>
Tooling: Upgrade to Umbrello 4.17 (UML drawing tool) ..just open the existing uml/Lumiera.xmi and store it again
2021-04-16 15:50:22 +02:00
<codegenerator language="C++"/>
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