The config sync works in the 'www_rc' -> browser Javascript direction,

The config sync works in the 'www_rc' -> browser Javascript direction, proving the other way is a little tricky, I might as well just write the schedule GUI and be done with it rather that write test code etc etc

Reality check,

Reality check, its 14:30, its light - sooo its the middle of the night - right ?

Just spent 3 hours coding the schedules config sync,

Just spent 3 hours coding the schedules config sync, so when you change something in the GUI (yet to be written), it syncs to 'www_rc'. kmotion3 will have 8 user defined weekly schedules, each of which can tie into one of 4 exception schedules based on special dates, ie bank holidays etc. Its a lot of addition ... might take a little break before I test and debug it ;)

On nights,

On nights, its 4:36 AM, eyes heavy, mind groggy, struggling !

Really exciting screenshot :)

It is said development is boring ? Just to prove this myth totally wrong here is an exciting screenshot showing the current state of Schedules :)

Cool heh ?

Started the schedule code,

Started the schedule code, this bit is going to be interesting, you can have a schedule, what you do every mon - sun then you can have exceptions for bank holidays etc. So far I have a single blank timeline and a bunch of config in 'www_rc', will join the two up and then expand from there ...

Darn time is tight !

Darn time is tight !, getting pulled away again but managed to fix a couple of bugs in camera config, plus enabled log scrolling now so you can see a few hundred entries, going to be important since v3 will use the logs a lot more. Trying to decide whether to work on the scheduling GUI + backend or the themes. Think I will leave themes to last, they will give kmotion eye candy plus reveal a small surprise :)

Big mug of Tea and kmotion3 IDE in front of me :)

Big mug of Tea and kmotion3 IDE in front of me :)

Stealing ideas is good :)

So an update, when I changed the feed config GUI I removed some options and added different ones, this totally broke the back end javascript and python so I have spent a few hours fixing it so the web interface works again, oh plus a few cosmetic touches. And I am proud to announce that the first 'new' feature now actually works, PAL / NTSC. I say new because Robert coded it in v2 - and I well stole the idea ;)

Coding is funny,

Coding is funny, you can code and code and in your mind you know what you have done and know the end has drawn a little closer but explain what you have done to someone, even your cat ? difficult ! So I have done a fair bit of coding and nothing more to say. v2 took something like a 18 months to write, v3 will not take that long but its still got a long way to go.

That broken server ...

That dead kmotion server ... PSU dead, video capture card physically broken (???), New PSU, New video capture card, Spinrite both HDD's, Memtest86 over night, re-install software, not really needed but was an upgrade from 9.04 ?, so installed 10.04 LTS, soak test and ready to be returned to owner :)

I have a secret plan

So after a good start a lot of real world stuff has been eating my time, relatives from Australia, my wife getting ill, on call - its all been a bit of a whirlwind but I have a secret plan. This weekend I have nothing planned in the evenings ;)

OK so a little more code

OK so a little more code on the "misc function" buttons to get the new ones to behave properly and starting to convert logs to the new format.