Re:The Story Behind F.lux
by keithpeter on Sunday January 24, 2016 @05:18AM
(#10962123)
Quote from interesting page linked in parent post...
"...Now to be fair most of this is the result of OpenBSD ports choosing to build and package optional dependencies, including the GUI..."
I suspect the people who produce and maintain the ports builds are putting all the options in to cover as many use-cases as possible. I've noticed that some OpenBSD ports give alternatives to pick from with different compilation options. I suspect that might be impractical for many choices.
Now I'm wondering if I can build sct.c on the Slackware box and have a play with a bash script setting the colour temp by time of day for current latitude...
there is a whole bunch of stuff built but unreleased outside of the app.
Re:The Story Behind F.lux
by verusfossa on Saturday January 23, 2016 @06:13PM
(#10960572)
If this is true, it's unfortunate. Things like flux should have a small footprint and a small working domain. I'm willing to spare some complexity for usability tools, but always end up getting off the bus when it gets too heavy.
What kind of stuff?
It is complicated. I only know because I am a friend, so we have to wait till he releases stuff.
Re:The Story Behind F.lux
by edwintorok on Saturday January 23, 2016 @06:24PM
(#10960610)
Will it be released as open-source?
Doesn't really make sense to develop it as a closed-source application, when the application itself is offered for free, and open source versions exist already.
this is a very small understanding of what they are trying to build.
[0] http://www.tedunangst.com/flak/post/sct-set-color-temperatur...