In this section you can check out what I'm currently working in, practically in real time.
If some of this seems cryptic it's because the logs seen here come directly from my personal productivity tool prio, and are really just "notes to self".
Nevertheless, if you are interested in what I'm currently working on, this space will certainly be updated FAR more often than the news section.
10:32:26 codebase TASK: move screen capture to a reusable object
20:45:43 vidiot CLOCK: 0.1 days (01:21 hours)
18:43:43 vidiot CLOCK: 00:14 hours
18:17:36 vidiot CLOCK: 0.1 days (01:26 hours)
16:38:25 vidiot CLOCK: 0.1 days (03:08 hours)
12:36:36 vidiot CLOCK: 0.1 days (02:18 hours)
11:50:14 vidiot TASK: subdiv to own class
11:49:57 vidiot TASK: move videosources to vc
20:58:28 vidiot CLOCK: 0.2 days (05:38 hours)
16:26:44 vidiot TASK: refactored current clip access
23:10:18 vidiot CLOCK: 01:05 hours
23:09:56 vidiot TASK: softpresenter fonts
23:09:52 vidiot TASK: anim layer
23:09:50 vidiot TASK: figure out how it works again!
21:20:54 vidiot CLOCK: 0.2 days (04:27 hours)
16:39:07 vidiot CLOCK: 0.1 days (03:20 hours)
14:55:46 vidiot TASK: softpresenter
21:15:24 vidiot CLOCK: 00:29 hours
16:20:04 vidiot TASK: move MetaController to CompController
16:19:36 vidiot CLOCK: 00:08 hours
16:05:07 vidiot CLOCK: 00:30 hours
15:33:20 vidiot CLOCK: 00:29 hours
15:14:36 vidiot TASK: abstract timing interface
00:18:40 swörd TASK: group name editing
00:18:25 sbtf TASK: make sure muzzle flare still works
23:18:30 sbtf CLOCK: 0.1 days (01:18 hours)
23:15:46 sbtf TASK: basis of swörd build path
21:43:07 sbtf CLOCK: 00:14 hours
21:28:36 swörd CLOCK: 00:02 hours
21:25:57 codebase CLOCK: 00:00 hours
16:10:13 sbtf CLOCK: 00:52 hours
00:17:44 sbtf CLOCK: 0.1 days (01:33 hours)
00:17:37 sbtf LOG
Experimented with refactoring all the "fixed count" objects in Model to be more C style, just global functions and minimal state exposed via headers.
I was thinking that this would get rid of any extraneous "classes as folders", but in reality that wasn't so much of a gain when compared to the way that all the state spread out from a logical point of view. There is no longer any "top" to the state of the Model, which feels ickier.
Network stuff gets to be a little harder because of this looseness, it's less obvious what needs to be synced across the network.
I guess in the end the cons outweigh the pros, especially since the code starts taking on two distinct flavors; there are still classes and objects in cases where there are at least 2 instances of any given thing, while on the other hand everything of sole instance feels like a jumble of loose functions. Granted, I have those functions in namespaces, but the implementation feels kind of spread out and unfocused.
I will see how it feels tomorrow.
07:10:32 sbtf TASK: integrate more beast frames
16:44:32 sbtf CLOCK: 00:58 hours
15:32:15 sbtf CLOCK: 00:52 hours
11:31:37 sbtf CLOCK: 00:25 hours
10:40:19 sbtf CLOCK: 00:01 hours