29e67e828d
remove NoBug resourcetracker and switch back to plain pthreads
...
due to desing shortcomings, the resourcetracker
produces lots of false positives and inhibits
any further diagnostics regarding GUI startup.
2011-02-07 09:55:39 +01:00
ff0ae1527a
Fix build: the LUMIERA_PLUGIN didn't get through to the object compilation
2011-02-06 15:12:13 +01:00
88678209bc
use setup.ini to retrieve the modulepath and configpath
...
connect config-facade with the new BasicSetup implementation
to fetch values from setup.ini, instead of the (not implemented)
Config-system. Hook this new lookup mechanism into the
plugin loader to retrieve the search path from there
2011-02-06 05:06:16 +01:00
87475fa3c1
Fix usage of field named "new" in configitem.h
...
This prevents including config.h into C++ code
2011-02-06 02:39:34 +01:00
Stefan Kangas
9f3c1ecf00
spelling fixes
2011-02-06 02:12:55 +01:00
11d709b85e
incorporate basic setup.ini into the AppState object
2011-02-06 02:12:00 +01:00
e84ceec9b5
refactor some lib facilities
...
- Cmdline into namespace lib
- test coverage for the SearchPath iterator
2011-02-05 23:53:37 +01:00
e73bea379c
Adjust some Copyright headers
...
List of years instead of a range is better
2011-02-05 20:56:51 +01:00
ad246ad31d
Merge Buildsystem adaptations for installing Lumiera
...
- use custom builders
- clean up specification of target paths
- generated executable is fully relocatable
- read a bootstrap INI instead of compiled in searchpath
2011-02-05 15:54:24 +01:00
51ef755a4f
Merge Timehandling draft and GUI DrawStrategy and TimelineEntiy refactorings
...
Merge branch 'gui' into install
2011-02-05 14:30:11 +01:00
0ac0149137
Define first preview version number 0.pre.01
...
Rewrite README, INSTALL and AUTHORS
as foundation for the Debian package
2011-02-04 22:19:25 +01:00
babbe33d1d
Demonstration of complete bootstrap, loading INI and resolving GUI module path
2011-02-04 16:10:59 +01:00
a42e6a5a8f
draft solution loading an INI file for module path resolution
...
this would remove the need to compile any path into the EXE
2011-02-03 17:34:24 +01:00
208b552955
Demonstration how the application could resolve the module loading location
...
The real application likely will consult the configuration file
to search alternative module installation locations.
2011-02-01 05:10:45 +01:00
29e2233e6a
an exercise: how to get the path of the current executable
...
Note: this is a non-portable Linux solution
2011-01-31 05:35:43 +01:00
d9f90c2c04
SCons: finish reworking buildsystem to rely on custom builders.
...
All target paths and install targets now defined automatically,
most of the buildscript just using plain sourcefile names
2011-01-30 22:12:55 +01:00
9cb03c7015
Fix installation triggered already by build target
2011-01-30 19:43:51 +01:00
daef6c7676
SCons: remove unnecessary indirections $SRCDIR, $MODULES, $ICONDIR etc
...
these don't create real flexibility and make definitions less readable
2011-01-30 19:20:02 +01:00
abf1bc776b
SCons: remove all explicit target and install specifications
...
now superfluous, because our custom builder handles that automatically
2011-01-30 18:56:51 +01:00
609873d90b
switch to use the new (better) builder implementation
...
especially this means to use the common well-known names again,
like "Program" "SharedLibrary". The customisation now happens
invisible in LumieraEnvironment.
2011-01-30 17:00:15 +01:00
ab481a80b8
better implementation of Lumiera custom SCons builders, wrapping the predefined builders
2011-01-30 16:47:03 +01:00
014c22b40a
SCons: rework build directory configuration. All customisations to LuimieraEnvironment
2011-01-30 15:27:21 +01:00
9e56434c7e
SCons: start concentrating all custom builders into LumieraEnvironment
2011-01-29 23:09:02 +01:00
bc22ec7faa
Install: first preliminary working installation setup
...
the installed lumiera exe can even be started...
...well with a bit of cheating: you need to cd into the lib/lumiera
because the PLUGINPATH problem isn't solved yet
2011-01-29 16:45:22 +01:00
7993759f8e
SCons: remove the homebrew tarballer
...
that was a nice SCons learning exercise, but never used
moreover, packaing is not the concern of a build system
2011-01-29 14:16:15 +01:00
a6810957b4
Install: change organisation of target and output directory variables
...
now supporting a PREFIX in addition to the INSTALLDIR.
The latter is intended for package building
2011-01-29 14:10:19 +01:00
2bcc8d9ae3
SCons: build loadable modules immediately to the target destination
2011-01-29 02:33:13 +01:00
35953b335b
SCons: rearrange output directory to target/modules
2011-01-29 02:06:21 +01:00
764a38abe6
SCons: experimental support for some library lookup concerns
...
- setting -rpath with $ORIGIN to build a relocatable package
- fix missing DT_SONAME (likely just a problem of very old SCons version)
2011-01-28 23:31:00 +01:00
587f507292
analysis/design: changing time values
2011-01-23 22:44:26 +01:00
faf579c4c5
enforce generally imutable time values
2011-01-22 23:20:12 +01:00
dea026cfd9
omit the Digxel timing measurments from test suite
2011-01-22 18:44:03 +01:00
7b783e885a
more thorhoug testing of denormalised values
...
...uncovered yet more bugs.. yay!
2011-01-22 18:35:04 +01:00
69eb659d4e
refactor to extract a special "flip representation" operation
2011-01-22 18:33:15 +01:00
acc7a19fbd
Fix: now able to handle negative extended SMPTE
...
changed the order of propagation when wrapping
the individual digxels of the SMPTE Timecode
2011-01-22 14:41:58 +01:00
ac9e9a99df
change the way the Digxel mutator is invoked
...
this refactoring prepares a change to address
the problems with negative extended SMPTE Timecode
2011-01-22 14:04:43 +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
1a07cc9bb2
SMPTE Timecode: first round of debugging and testing
2011-01-21 16:22:01 +01:00
0493caac1d
first complete implementation of SMPTE timecode
...
first integration of the various components
developed thus far; design still needs some
improvements, esp. regarding the effectiveFramerate
Note NTSC-drop-frame not yet supported...
2011-01-21 11:42:29 +01:00
f930703e86
WIP draft cascading breakdown of time into timecode components
...
TODO not entirely correct... and how to access the framerate?
2011-01-20 22:17:25 +01:00
1b79b4a937
fix regression
2011-01-20 21:39:17 +01:00
c55260d4e4
generalise to long and int; improve test coverage
2011-01-20 21:30:48 +01:00
05383ea44a
crafting a integer scale wrapping util, for timecode conversions
2011-01-20 13:21:14 +01:00
e1c025778b
Digxel: ensure the mutator functor is also called on increment
2011-01-19 11:47:14 +01:00
c3d0fda495
remove superfluous type qualifier
2011-01-19 11:32:38 +01:00
5418902442
remove superfluous default parameters from Tuple constructor function
2011-01-19 11:32:27 +01:00
9df0df6145
Merge Stefan's work on timeconversion and SMPTE drop-frame
2011-01-19 11:32:03 +01:00
Stefan Kangas
551ec8f011
Remove preconditions requiring correct formatting of input times in time lib.
...
For example, one could not specify minutes > 59 nor milliseconds > 999. Other
parts of the code however relied on the fact that one could give arbitrary times
in all fields (hours, milliseconds and minutes).
2011-01-19 11:10:39 +01:00
Stefan Kangas
6a44134833
Add support for NTSC drop-frame timecode.
2011-01-19 11:10:39 +01:00
