9bd96a1b19
time-entities refactoring: Duration isn't an Offset
...
removed that inheritance relation; it was a typical
example of abusing inheritance and violated the
Liscov substitution principle. It is sufficient
to allow promotion of an offset into a Duration.
Note: Duration is the time metric
2011-09-25 19:25:53 +02:00
5e8a9b50d1
define asset::Viewer
2011-09-25 19:25:52 +02:00
eb5e0ab9ff
WIP: start building a Test for time::Control. Need Cartesian product of cases...
2011-09-25 19:25:51 +02:00
4731afefb8
continue drafting the Player control elements -- life timevalue changes
2011-09-25 19:25:50 +02:00
c091b8e260
define Player / Output subsystem stub
2011-09-25 19:25:50 +02:00
cb6453afe1
detailed planning how to build the player subsystem
...
key idea is to grow and rework the design of the
DummyPlayer to yield the full featured Player
2011-09-25 19:25:49 +02:00
ebd6cfca82
Start design work for the Player Subsystem
2011-09-25 19:25:49 +02:00
99bf3c6d81
join with latest work on timecodes and frame quantisation
...
Merge branch 'timequant' into gui
2011-05-15 04:28:20 +02:00
6dd762fa7a
(cont) details of organising the fixture datastructure
2011-05-15 04:26:22 +02:00
29df0984ec
(cont) details of releasing storage of fixture segments
2011-05-15 04:26:22 +02:00
5f6cbdc5bc
detail analysis of fixture storage managment
2011-05-15 04:26:22 +02:00
6b1b6cb805
draft how to integrate parsing of timecode formats
2011-05-15 04:19:27 +02:00
bf61ff7248
WIP test-driven brainstorming: nudge by grid
2011-05-15 04:19:26 +02:00
5851332628
back to business: now able to implement time mutation messages
2011-05-15 04:19:25 +02:00
4d6bb3d54c
design outline for a limited time::Mutation capability
2011-05-15 04:19:24 +02:00
0e4ed856d7
WIP: get back into the topic of time value mutations
...
start drafting a unit test....
2011-05-15 04:19:24 +02:00
ab72b528c8
draft test for changing time specs
2011-05-15 04:19:22 +02:00
1e1c3706dc
update some DIR_INFO entries
2011-04-05 00:44:30 +02:00
ecb7d58a4f
Merge changes to make Lumiera installable
2011-03-07 03:31:19 +01:00
Stefan Kangas
58a6303a4c
Remove incorrect occurrences of glade being mentioned as a dependency.
2011-03-07 03:02:35 +01:00
587f507292
analysis/design: changing time values
2011-01-23 22:44:26 +01:00
14f233f83b
WIP: some more test coverage ... unveiling yet more bugs
2011-01-22 02:35:58 +01:00
9d75739089
SMPTE Timecode (without drop frame) unit test pass
2011-01-21 20:24:41 +01:00
05383ea44a
crafting a integer scale wrapping util, for timecode conversions
2011-01-20 13:21:14 +01:00
aa5c78a30f
TimeGridBasics_test pass
2011-01-15 15:04:23 +01:00
ee0dcf3ba0
introduce generic grid API to subsume quantiser and grid asset
2011-01-15 03:49:35 +01:00
a1f2a60427
WIP design draft regarding the interplay of quantisation and timecode
2011-01-13 23:56:52 +01:00
52eb4c4709
set an explicit artificial limit on the allowed time range
...
this is the first building block in an attempt to
protrect against time wraparound. The intention is
not to be airtight, but practically effective.
A really airtight solution would require writing
our own SafeInt class
2011-01-13 03:36:11 +01:00
d30515c37e
analysis of range limit problems in quantisation
2011-01-13 03:36:11 +01:00
dede87d384
implement basic quantisation operation for timehandling library
2011-01-13 03:36:11 +01:00
e7f5ce9e33
WIP rework timecode format hierarchy
...
second try: eliminate base class,
work with concrete formats allways...
2011-01-13 03:36:09 +01:00
f798428428
WIP start a unit test to cover simple time grids
2011-01-13 03:36:08 +01:00
640d061de6
Meta Assets as a framework for specifiyng a TimeGrid
2011-01-13 03:36:08 +01:00
ff87b62387
decide how to categorise time grids: they are Meta Assets.
2011-01-13 03:36:07 +01:00
b5f32522b1
still chewing on the remaining problems with time quantisation
2010-12-26 03:36:27 +01:00
9e60a631eb
solve or decide the problems turned up by the usage analysis.
2010-12-24 19:21:10 +01:00
966d2227e5
analysis of time usage, including quantisation pitfalls
2010-12-23 22:20:56 +01:00
1294926508
Time Quantisation: theoretical analysis and initial design draft
2010-12-20 07:37:41 +01:00
e7191ed3c6
Planning Fixure: Segmentation datastructure ( #726 )
2010-12-13 03:22:11 +01:00
8a54e00b6b
ModelPort registry unit test pass ( closes #727 )
2010-12-11 23:40:12 +01:00
2827961385
WIP: test driven brainstorming about model port registry
2010-12-10 01:27:17 +01:00
ee56ab36a0
Definition of ModelPort, model port reference and -table ( #718 )
2010-12-05 02:46:37 +01:00
56ceca398b
The first substantial step towards a builder backbone
...
Defined the structure of the fixture and the outline
of the process leading to creating this data structure.
2010-12-05 02:46:36 +01:00
fc051dfcba
OutputMapping implementation draft
...
coded up the easy part, omitting the actual resolution
based on an configuration query
2010-11-27 06:01:31 +01:00
b42e5c859f
Test-driven brainstorming: how should output mapping be used?
2010-11-23 03:40:11 +01:00
a43bd239cb
Try to complete the design of Binding and OutputMapping
2010-11-22 04:26:28 +01:00
f0fbf0e6f1
bring some UML diagrams up-to-date
2010-11-22 02:28:03 +01:00
5ae1f819f2
Finished the design of global pipes
2010-11-21 02:29:26 +01:00
9473fd3d67
OutputDesignation implementation draft
2010-11-19 05:01:43 +01:00
cfc4325f55
define details of binding and mapping
2010-11-17 04:49:22 +01:00
