LCDHost Alpha 29

Whats new in LCDHost 0.0.29:

  • Fixed degree symbols
  • Set Eos layout default application to HWiNFO

Note that monitoring needs to be customized per-machine, but the installed default layouts are read-only.
You’ll need to make a copy of the layouts/g19-eos directory and modify that. And keep backups of your layouts,
preferably outside of the LCDHost installation folder. I’m going to start having the default Eos layout customized for
my own machine simply so I can more easily spot things like that degree symbol bug.

I’m having problems reproducing the data linking failure from the “Extended Function Area/Output” in Eos.
If you can get it to happen, please let me know how. Also, if you used to see that bug and it’s now
gone, let me know that too.

LCDHost Alpha 28

Whats new in LCDHost 0.0.28:

  • Fixed –hidden startup bug
  • Fixed network bandwidth measurements
  • Include LH_DriveStats on Windows
  • Installer tries to clean out old .DLLs
  • Installer includes MS Visual C++ 10 runtimes

Remember to take a backup of your layouts before updating. The Windows installer for A28 tries to remove all old DLL’s and binaries from the LCDHost install directory – hopefully this will help people still stuck on A25.

LCDHost Alpha 27

Whats new in LCDHost 0.0.27:

  • Data linking bug fixed
  • Updated Qt to 5.0.2
  • Windows version now compiled with MSVC
  • Replaced libusb with libusbx
  • Fixed hidapi handle leak on Windows
  • Added standard layouts to google code repository
  • …and lots of bug fixes in general

The autoupdater will get it for you, or download it from the LCDHost homepage.

Qt 5 isn’t binary compatible with Qt 4, so it’s essential that A26 is completely uninstalled.
Take a backup of your layouts directory, uninstall, remove any remaining traces of A26 and install A27.
You will need the Visual C++ 2010 runtime installed (MSVCR100.DLL).
If alpha 27 doesn’t work for you, old versions of LCDHost are still available:

LCDHost Alpha 26

What’s new in LCDHost 0.0.26:

  • First Linux release (Ubuntu 12.10 64-bit, Qt 4.8.3)
  • Update to Qt 4.8.4 on Windows and OS/X
  • Update to openssl-0.9.8x
  • New centralized logger
  • Increase rate limit trigger to help LH_Monitoring
  • Exits on window close if no systray available
  • Distribute HID api as shared library to avoid resource contention
  • Lots of HID testing and workarounds for OS/X Mountain Lion
  • Support G13/G15/G19 output on Linux
  • Removed LH_Lua as it’s broken beyond repair
  • Fix week number formatting
  • Lots of fixes to allow compiling with msvs2010
  • Lots of fixes to be compatible with Qt5

The autoupdater will get it for you, or download it from the LCDHost homepage.

I’ll add a download link for the Linux version to the homepage ASAP. Please read the enclosed README.linux and if you find it confusing, please ask your local Linux guru for help rather than me.

The joys of programming

And six months later down the road, what has all my furious tapping at keyboards got me? I’ll get to that in a sec. First I want to tell you about my unhealthy desire to code things as good as I can – and even worse, re-invent other peoples wheels if I don’t think they’re round enough.

It always starts out reasonably enough. LCDHost needs some kind of repository to maintain metadata about itself, plugins, layouts, et cetera. Which in turns affects the software packaging. Which means I need to address security issues, both in the packaging and repositories. Ok, so far, not so bad. Except every wheel I look at has the wrong kind of spokes, or is too big, or not wide enough.

Then the insanity starts. You see, to have any sort of security, you have to design with it in mind from the start – and not many products are. Also if you want performance – design for it. As opposed to coding for it – that’s called optimization and is nowadays usually a waste of time. And above all else, stability and reliability.

I find plenty of solutions that are good enough. But my ego (he’s the giggling imp on my back, the one with red eyes rolling in random directions) won’t let me use them if I think I can do it substantially better. Which means I…

  • Learn to use Python since awk doesn’t cut it and Perl is not my style.
  • Hack up lbssh to let me launch my local editor to edit server-side docs (no more nano).
  • Got fed up with Pythons argparse and write my own self-documenting CLI package.
  • Write another chroot maintenance tool as I find existing ones lacking.
  • Learn the details of a lot of boring stuff, like upstart and IPv6 and what the blërgh else.
  • Evaluate existing PHP frameworks, contribute some bug fixes to them, and then start on my own. Of course.

I’m quite sure I left out more than half in that list, but it gives you the general idea. These tendencies of mine are good for software quality, but a supermassive black hole to time management. I hope to be recovering from obsessive recursive dependency coding soon.

Thank [this space intentionally left blank] for that.